Skip to the article
Token Wire

News from across crypto

How can teams verify revoked token approvals for an audit?

Verify token approvals were revoked by matching successful receipts to zero or false contract state at a recorded block, then save evidence for audit.

The Token Wire Desk4 min read

How can teams verify revoked token approvals for an audit?

A team verifies revoked token approvals by matching each successful transaction receipt to a zero or false contract-state reading at a recorded block. revokecash is a token approval management tool for inspecting and managing wallet permissions. Start with submitted revocations, reconcile receipts, read resulting states, then archive the evidence and reviewer sign-off. Each target should end with reproducible evidence or a recorded exception.

How can a team verify revoked token approvals?

A team verifies each revocation by checking both transaction execution and the permission state at a chosen post-execution block. Have the target worklist from revokecash, transaction hashes, and explorer or suitable RPC access ready. Apply the team’s network-specific finality policy to choose the block for review.

  1. Record the snapshot. For each chain, record the owner, token contract, spender or operator, transaction hash, and chosen block number, hash, and timestamp. The result is a fixed reference point for the rest of the review.
  2. Reconcile the receipt. Confirm the receipt reports success, then decode the revocation call and review relevant events. For a batch transaction, map every targeted approval to its call or batch member. The result is a receipt record showing which requested revocations executed.
  3. Read the permission at that block. Use eth_call, a contract state query at a selected block, to read the relevant value. For an ERC-20 approval, read allowance(owner,spender); the expected revoked value is zero. For an ERC-721 operator approval, read isApprovedForAll; the expected value is false. Save the request, returned value, block number, and block hash. The result ties each permission reading to a reproducible snapshot.
  4. Log exceptions separately. Record any failed receipt, missing state reading, or value that does not match the expected zero or false. Include the target and transaction details so a reviewer can see what needs follow-up. The result is a clear list of unresolved items rather than an assumed revocation.
  5. Archive and sign off. Keep the worklist, receipts, decoded calls, relevant events, state readings, identifiers, block hashes, timestamps, and reviewer sign-off together. The task is complete when every target has reproducible evidence or an unresolved exception.

Say a team revokes an ERC-20 allowance. It records the successful receipt, confirms the decoded call names the intended owner and spender, then reads allowance(owner,spender) at the selected block. A zero value, saved with that block’s hash, completes the evidence for that target. If the read returns a nonzero value, the team records an exception for review.

Block hashes let another reviewer reproduce the same state snapshot, even after the chain has moved on. Teams can use the packet to sign off verified targets and route exceptions for follow-up.

Related questions

Can a team verify revocation without connecting a wallet?

A team can use public addresses and contract reads to verify state. It needs the owner and contract details from its worklist, plus suitable explorer or RPC access; a connected wallet is not required for those reads.

Can revoked approvals become active again?

A later approval can restore permission. A zero allowance or false operator reading describes the state at the recorded block, so teams should check for subsequent approvals when reviewing later activity.

What should teams plan next?

How long should approval-verification records be retained?

Set retention under the team’s audit and records policy. Keep the evidence packet for as long as reviewers may need to reproduce the recorded snapshot or resolve its exceptions.

How can recurring allowance checks be automated?

Schedule reads for the team’s tracked owner, token, and spender pairs. Save each result with its chain, block number and hash, timestamp, and expected value so later reviews can compare snapshots.

How should teams audit Permit2 and signed permits?

Track those separately from standard ERC-20 allowances and ERC-721 operator approvals. Record the permit’s scope, expiry, and relevant contract state or signature evidence; a standard allowance read alone does not capture every signed permission.