Start typing to search this publication.
defi news
Open menu

Subscribe to defi news

Get new posts delivered straight to your inbox.

How Does revokecash Find My Approvals? Your Wallet’s Live Grants

defi news
4 min read

revokecash finds your wallet’s approvals by reading Approval and ApprovalForAll events on the selected chain, then checking which permissions are still active on-chain. When you review an unfamiliar spender, use revokecash as a Revoke.cash approval checker for its current permission before deciding whether to revoke it. The events record grants tied to your address; live reads show what remains now.

How revokecash Builds the List From Chain Events

The list starts with event logs that connect your wallet address to a token or NFT operator on one chain. A log is a record a contract writes when a transaction happens. The search filters those records by your address in the indexed owner topic, which is the part of an event that can be searched directly.

  • ERC-20 token approvals: An Approval event records the owner, spender and approved value. It identifies the token contract and the address allowed to spend its tokens.

  • ERC-721 operator approvals: An ApprovalForAll event records the owner, operator and whether that operator was approved. It concerns permission over the owner’s NFTs in that collection.

That gives the checker candidates, not the finished list. It takes each token and spender pair found in the logs and asks the token contract for its current value. It can then attach readable token and spender labels and present the active permission with its address and amount. The contract addresses are the underlying identities; names make them easier to recognize.

The chain is part of the search, too. Base and Polygon keep separate logs and contract state, even when you use the same wallet address on both. An approval granted on Base therefore belongs to the Base list. Looking at Polygon can produce a different list without anything having changed in your Base wallet.

Current On-Chain Reads Decide Which Approvals Stay

Current contract state decides whether a logged approval still belongs in the list. For an ERC-20 token, allowance() returns the amount the spender may still withdraw from the owner. For an ERC-721 collection, isApprovedForAll() says whether the operator still has collection-wide permission. A zero allowance or a false operator approval removes that candidate from the active results.

Say you gave a trading contract an Unlimited token approval, then later changed the allowance to 40 tokens. This is an illustrative case: the wallet, token and spender are the same before and after the change. The old Unlimited grant remains in the event history, but the current allowance is 40, so 40 is the useful amount to show. The list follows the live permission, not the largest value that ever appeared in a log.

If that same allowance later reaches zero through use or revocation, the historical event still exists. A fresh live read finds zero and drops the pair from the active list. An NFT operator follows the same pattern: an earlier ApprovalForAll event may identify the operator, while a current false value means its collection-wide permission is off.

This explains why an entry can disappear without its original transaction disappearing. It also explains why a remembered approval amount may differ from the amount shown today. The log answers which permission should be checked?; the contract answers what permission exists now?

Signed Permits and Separate Chains Explain Missing Entries

A signed permit can be missing because signing and submitting it are different actions. With ERC-2612, a wallet signs a message authorizing an allowance. The signature can be held off-chain until someone submits a valid permit transaction. Signing alone writes no Approval event and changes no on-chain allowance, so the event-and-live-read method has nothing new to list.

Consider an illustrative signed permit for 100 tokens. While the signed message remains unsubmitted, the approval list reflects the token’s existing on-chain allowance, whatever that was before signing. Once someone submits the permit successfully, the token sets the allowance and emits an Approval event. The next live read can then show the new amount, provided the permission is still active. If the signature expires without submission, that proposed grant never becomes an on-chain allowance.

This is the method’s real boundary. An absent entry tells you about recorded, current permissions; it does not tell you whether an unsubmitted signature is still in someone’s hands. For that question, inspect the message you signed, its deadline and nonce, and the rules of the contract that accepts it. Those details determine whether the signature can still be used.

Permit2 adds another distinction. A token allowance granted to the Permit2 contract is an ERC-20 approval that a token read can find. Permit2 also has its own allowance and signature mechanisms; a token’s Approval log alone does not describe every permission inside them. When the concern is a Permit2 signature or internal allowance, examine that specific authorization as well as the token’s allowance to Permit2.

Why is an approval missing from revokecash?

An approval may be absent because its current allowance is zero, its operator permission is false, it belongs to another chain, or the signed permit has not been submitted on-chain. Start with the chain and the exact token and spender addresses. Those details tell you which contract state is relevant.

Can revokecash check any wallet address?

Approval logs and current allowance values are public blockchain data, so this method can inspect an address without that wallet’s private key. Reading a permission and changing it are separate actions: a revocation must be authorized by the wallet that owns the permission.

Where do revokecash spender names come from?

A spender name is a readable label associated with an on-chain address; the Approval event itself contains the address, not a brand name. Labels help with recognition, but use the address when identifying the contract that actually holds permission.

For your next review, choose the chain where you granted access and compare the spender address with the permission’s current value. That gives you the live grant to keep, reduce or revoke—and a clear reason when an old grant no longer appears.

Subscribe to defi news