Should wallets explain the rights behind a token transaction?

Wallets handling tokenized ownership should show the practical rights behind a transaction, not just the contract address, function name, and amount. A delegated operator, rental user, bundled access right, or upgradeable proxy can make a routine approval carry consequences that are invisible in that summary.

For example, `setApprovalForAll(operator, true)` may authorize an operator to manage substantially more than one NFT—potentially the holder’s entire collection under that contract. A plain-language warning should expose the scope, recipient, duration, and relevant upgrade authority where possible.

Simulations and readable explanations could improve consent, but they can be incomplete, hard to standardize, or misleadingly reassuring when metadata, future upgrades, or later transactions matter. Should human-readable permission summaries be a wallet requirement, an optional feature, or something smart-contract standards must provide? Share wallet UX examples or counterarguments.

The dangerous word is “where possible.” A summary that omits proxy upgrade authority or downstream calls may become a security theater badge. I would rather see explicit unknowns than a green “safe” label. The wallet should distinguish decoded facts from inferred consequences.

Users do not need every ABI detail, but they do need the answer to “what can this party do, to what, and until when?” Rental rights are a good test because ownership and use are deliberately separate. That distinction belongs in the primary confirmation surface, not a disclosure drawer.

Standards can expose fields; they cannot guarantee meaning. Contracts will compose permissions in ways a generic wallet cannot fully infer. I’d make structured permission metadata a requirement for contracts that want a clean UX, while keeping a cautious fallback for everything else.

I support summaries as an optional wallet feature today, with careful labeling. The brief itself matters: proposed clear-signing mechanisms are not universal, and simulations are not proofs of future behavior. A mandatory display could create pressure to compress uncertainty into a misleading sentence.

If “approve everything” still looks like a normal green button, we have learned nothing. Show the scope in large type, then let experts expand the details. The standard can help, but wallets still own the moment when someone signs.