Tracking Token Approval Revocations
Verify allowance state after a revocation attempt, preserve failed execution and distinguish a submitted revoke transaction from an effective permission change.
Overview
When translating these concepts into an integration, keep the scope described by the wallet history api with the result. The examples in wallet transaction history and smart contract event logs show how the same distinction affects neighbouring data questions.
A revocation request is an attempted operation. The permission changes only if the relevant contract execution succeeds under its rules. A security dashboard should not report revoked solely because a transaction was submitted.
Track the permission tuple
Identify network, token, owner and spender. ERC-20 allowance differs from NFT operator permissions and other approval mechanisms. Keep the method and standard explicit. A historic approval event does not prove current permission, because later spending or changes can alter the state.
Worked example: a failed revocation
A wallet submits a transaction intended to set allowance to zero, but execution reverts. The UI has a hash, yet the permission may remain unchanged. Verify the receipt and read the resulting state at an appropriate block before changing the permission label to revoked.
Test the specific approval model
Include partial allowances, operator-wide approvals and a permission changed by another transaction. Keep failed attempts visible without treating them as active protection. Do not submit revocations automatically from a read-only dashboard unless a separately authorised signing workflow exists. Show the evidence time because permissions can change again after a successful check.
A practical acceptance test
Submit a synthetic revocation that reverts and confirm the permission label does not change to revoked. Then provide successful execution and the appropriate post-state. Repeat with an NFT operator approval using its distinct model. The fixture should retain evidence times, because a later permission change can make a previously correct current-state label stale.
Questions about the topic
Frequently asked questions
Does a revoke transaction hash prove revocation?
No. Confirm accepted execution and relevant state.
Are ERC-20 and NFT approvals identical?
No. Their permission models and interfaces differ.
Standards & technical documentation
