The issue of unlimited contract authorization is basically like giving the delivery person your house key and casually saying "Feel free to come in anytime"... It saves trouble now, but if something really goes wrong later, you won't even know where the leak came from. Revoking permissions is just as important as sleeping: you can sleep without locking the door or closing the windows, but you won't sleep soundly. Recently, before and after the upgrade of that mainstream public chain, everyone has been guessing whether the project will migrate. I think, regardless of whether they move or not, the old keys should be revoked first. By the way: I treat complexity as an enemy, so if there's a one-click revoke option, I won't bother memorizing a bunch of addresses. Anyway, I'm used to revoking permissions after use to avoid waking up in the middle of the night to security group messages and a racing heart.