Token Approval UX: What Revoke.cash Gets Right

Using a DeFi app often starts with a token approval.

The problem is that an approval can remain active after the swap, deposit or purchase is finished. A user may think they approved one action, while the contract may still have permission to move their tokens later.

The important question is:

Who can access my assets right now?

What Revoke.cash gets right

Revoke.cash turns these hidden permissions into a list users can inspect and manage.

Users can see the token, approved amount, spender and approval date. They can search, filter and sort the list, then reduce or remove an approval.

This makes permissions feel less permanent and gives users a way to clean up access they no longer need.

What I would test next

I would make the possible loss easier to understand by showing:

1. The app or contract with access

2. The asset it can move

3. The amount it can spend

4. The current value at risk

5. The cost of revoking access

Unlimited approvals should be clearly separated from limited ones. Unknown or recently approved contracts should also receive more attention.

The interface should explain that revoking access requires an on-chain transaction and will not recover funds that have already been taken.

The takeaway

Token approvals should be treated like active permissions, not completed transactions.

Users need a simple place to see who has access and remove it.