A proposal’s bytes and execution conditions matter alongside its description.
LET’S PICTURE IT
A committee’s summary of a motion and the exact instruction it authorizes should describe the same action.
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.
Separate text from executable content
A governance proposal can include a human explanation and one or more encoded contract actions. A reassuring title does not prove that the calldata performs the described change.
Voting has eligibility and timing rules
A system can use snapshots, delegation, quorum and different thresholds. The relevant configuration determines which votes count and when the result is established.
Passing may precede execution
A successful vote can require a time delay or additional execution step. Emergency controls or cancellation rules can also matter. A vote badge is not always the completed state change.
Inspect the action locally
A supplied ABI can decode the proposed function arguments. Our decoder can help with those bytes without signing or voting. Implementation and governance context still determine the effect.