One more thing: it would be good to support "self-destruct" for plugins. That is, if plugin can authorise removal of itself from the user's wallet. This would permit other parties to terminate their access to the wallet without user's involvement.

[MxNsTrixXx777]

One more thing: it would be good to support "self-destruct" for plugins. That is, if plugin can authorise removal of itself from the user's wallet. This would permit other parties to terminate their access to the wallet without user's involvement.

Examples:

1. "One-shot delegate". If a plugin is setup with an escrow to permit access to some funds once, it would be a nice UX if the user authorized this once, and then the counterparty would unlock the funds and cleanup the setup in one step.
2. Safety. Let's say a subscription service got their keys leaked and does not want the attacker to collect funds from their subscribers. It would be much safer for the users if the service could unilaterally terminate subscriptions without having to send out emails with warnings that no one reads.

Originally posted by @oleganza in ton-blockchain/TIPs#38 (comment)