Calldata
Pronunciation: KAWL-day-tuh
Also known as: Call Data, Transaction Input Data
Definition
Calldata is the read-only byte payload supplied to a smart-contract call, commonly carried in the data field of an Ethereum transaction. It usually identifies a function and encodes its arguments according to an application binary interface. Calldata can trigger state changes or carry arbitrary bytes, but it is not contract storage and does not by itself prove that the requested execution succeeded.
Overview
Meaning and scope
Calldata is the read-only byte payload supplied to a smart-contract call, commonly carried in the data field of an Ethereum transaction. It usually identifies a function and encodes its arguments according to an application binary interface. Calldata can trigger state changes or carry arbitrary bytes, but it is not contract storage and does not by itself prove that the requested execution succeeded.
Mechanism and operation
In a typical Ethereum function call, the first four bytes select a function and the remaining bytes encode arguments according to the contract interface. A plain native-asset transfer can have empty calldata, while a token transfer normally includes encoded instructions for the token contract. Contract code can inspect the payload and use it to decide which logic to execute, but any lasting result must be written to state or reflected in logs. The payload remains part of transaction data and can be examined after inclusion. The same bytes can be misleading if interpreted with the wrong contract interface, and unverified contracts may expose selectors that resemble familiar functions.
Practical payment example
A contract call carries encoded function arguments in transaction calldata. The recipient must decode and validate them before deciding what operation to perform.
Operational checks
Calldata also affects fees because nonzero and zero bytes have defined gas costs on Ethereum. Layer 2 systems may publish compressed transaction data or state updates through calldata, although newer data mechanisms can use different fee markets. Developers should not assume calldata cost is constant across networks or upgrades.
Distinctions and limits
Calldata is read-only during a call and is distinct from persistent Blockchain State. Wallets should display the destination contract, decoded action, assets, amounts, and approvals rather than showing only raw Hexadecimal.
Related reading
Related definitions: Blockchain State, Hexadecimal.
Example
A contract call carries encoded function arguments in transaction calldata. The recipient must decode and validate them before deciding what operation to perform.
Comparison
Calldata is read-only during a call and is distinct from persistent Blockchain State. Wallets should display the destination contract, decoded action, assets, amounts, and approvals rather than showing only raw Hexadecimal. Layer 2 systems may publish compressed transaction data or state updates through calldata, although newer data mechanisms can use different fee markets.
Key Takeaway
Calldata carries contract instructions and arguments, but the actual result must be confirmed from execution receipts, logs, and resulting state.
Sources
- Ethereum.org Documentation: Transactions — Ethereum.org (2026-08-02)
- Ethereum.org Documentation: JSON-RPC API — Ethereum.org (2026-08-02)
- Ethereum.org Documentation: Scaling — Ethereum.org (2026-08-02)