Distinguish identity, amounts, permissions and event layouts.
LET’S PICTURE IT
A good inventory clerk checks which register, which item, which unit and which permission before updating a record.
SEE IT FOR YOURSELF
Build a transfer call from typed fieldsStep 1 / 4
The standard transfer interface takes an address and a raw integer amount. This diagram uses address one and amount one hundred.
The standard transfer interface takes an address and a raw integer amount. This diagram uses address one and amount one hundred.Keccak-256 of the canonical signature supplies the first four bytes. The transfer selector is a9059cbb.An address is twenty bytes. Standard ABI encoding adds twelve zero bytes on the left to fill one thirty-two-byte word.The integer one hundred is hex 64, left-padded in word one. Selector plus two words produces sixty-eight bytes of standard calldata.
Animated local teaching model. No wallet, RPC or live blockchain data. Some labels and hashes are abbreviated for readability.
Exercise: interpret a quantity
A token with six decimals reports 3250000 raw units. The display quantity is 3.25 tokens. The number does not establish a dollar price or make the asset native ETH.
Exercise: identify the permission
approve(spender, 100) asks to set a spending allowance under the token’s rules. transfer(recipient, 100) requests movement instead. Compare their selectors in the ABI encoder.
Exercise: distinguish an NFT
Token ID 12 in one collection differs from token ID 12 in another. Network, contract and ID supply the identity context. An image that looks the same does not collapse those records into one item.
Exercise: read a log with limits
A decoded Transfer amount is a raw integer under a chosen schema. It is not proof of the emitter’s safety or the recipient’s final human-readable balance. Keep metadata and implementation assumptions explicit.