What Does the Approval Event Mean? Read Your ERC-20 Log
What does the Approval event in your ERC-20 contract mean? It records an owner’s allowance for a spender, in base units, so you can decode the permission.
By Crypto Readout Editorial3 min read#913fe9

An ERC-20 Approval log in your contract means an owner set an allowance for a spender: a limit on how many tokens that spender can move on the owner’s behalf. The event records that permission change in the token’s base units. It is not a token transfer.
How to read an ERC-20 Approval log
An ERC-20 Approval log contains an owner address, a spender address and a value. The token contract emits it whenever an approve call succeeds, as the ERC-20 standard specifies.
Decode the log with the ABI for the token contract that emitted it. The ABI tells your log decoder which fields are indexed and how to interpret the log’s topics and data. For ERC-20, owner and spender are indexed, so they appear in the topics; value is unindexed, so it is encoded in the log data. The event identifies whose tokens are covered, which address may spend them, and the allowance amount.
Say you see a value of 1000000. With a token that has six decimals, that means one token: the stored integer is divided by 106 for display. The event’s value is not automatically a whole-token amount. Read the token’s decimals before converting it, and keep the raw integer for calculations.
A value of zero records that the owner set this allowance to zero, removing the spender’s remaining permission under that allowance. A later successful approve can replace it with another value. ERC-20 approve sets the allowance for an owner–spender pair; it does not add the new value to the old one.
Why the event is not the current allowance
An Approval log records an allowance update at a particular point in the contract’s history; allowance(owner, spender) returns the remaining spending permission now. A spender can use transferFrom to spend against an allowance, so the latest Approval log may not tell you the current amount.
There is another decoding trap: ERC-20 and ERC-721 both call an event Approval, and the event signature uses the same argument types. But their third arguments have different meanings and indexing. ERC-20’s third argument is an unindexed allowance value. ERC-721’s is an indexed tokenId, identifying the individual NFT approved for an address, as set out in the ERC-721 standard. The shared signature does not make the log layouts interchangeable: use the ABI for the emitting contract and the token standard it implements.
Current implementations can also change an allowance without emitting a new Approval log. In OpenZeppelin Contracts 5.x, spending through transferFrom can reduce the allowance without emitting that event. This is allowed by ERC-20, so a log indexer that simply replays Approval events can drift from the contract’s current state. For an accurate current value, query allowance(owner, spender) from the contract; OpenZeppelin documents this behavior in its ERC20 API reference.
For an integration, decode Approval logs to track the permission changes the contract reports, then query allowance when you need the live amount. That same distinction helps when reviewing wallet permissions in revokecash: the event is a record of a change, while the current allowance tells you what a spender can still use. Check both, and you can explain what happened without mistaking an old log for today’s permission.