A record can keep its fields while leaving off the usual type label.
SEE IT FOR YOURSELF
From an emitted Transfer event to a receipt logStep 1 / 4
A token implementation may update balances and emit its standard Transfer event. State and the emitted record are related but distinct.
A token implementation may update balances and emit its standard Transfer event. State and the emitted record are related but distinct.A non-anonymous Transfer event uses the full thirty-two-byte Keccak-256 signature digest as topic zero, not a four-byte function selector.In the common ERC-20 shape, from and to occupy topics one and two. The raw value is a thirty-two-byte data word. Other standards can index fields differently.An application can decode receipt logs under the correct ABI. A matching signature does not establish that an unknown emitter is an honest token.
Animated local teaching model. No wallet, RPC or live blockchain data. Some labels and hashes are abbreviated for readability.
Notice the anonymous declaration
An event declared anonymous does not automatically place a signature digest in topic zero. Its first topic, if present, belongs to an indexed parameter.
Count the available topics
The EVM permits up to four topics per log. Omitting the usual signature topic allows an anonymous event to have up to four indexed arguments.
Require external schema context
Without a signature topic, a generic decoder has less help choosing a declaration. The emitting code and trusted ABI become especially important.
Do not reuse the usual positions
A decoder assuming topic zero is always a signature can misread every field. Check anonymity before assigning topic numbers to arguments.