In Ethereum, calldata is the input data supplied with a message call or transaction. Solidity also uses calldata as a read-only data location for certain function parameters. It helps a contract understand the requested operation, but it does not prove the request is authorised or the information is true.
Alicia submits a fictional science-kit booking with a kit identifier and date. Tricia’s booking desk receives the request fields. Kai Kai checks the caller’s authority and the current booking state before accepting anything.
This accessible lesson is for children, parents and adult beginners. It teaches blockchain technology, not cryptocurrency investing. All school examples use invented information.
The answer in plain English
In Ethereum, calldata is the input data supplied with a message call or transaction. Solidity also uses calldata as a read-only data location for certain function parameters. It helps a contract understand the requested operation, but it does not prove the request is authorised or the information is true.
A familiar classroom story
Alicia submits a fictional science-kit booking with a kit identifier and date. Tricia’s booking desk receives the request fields. Kai Kai checks the caller’s authority and the current booking state before accepting anything.
1. What goes into a contract call?
A call can carry a function selector and ABI-encoded arguments. The bytes specify a requested function and its inputs, not a guaranteed result.
2. Calldata versus contract storage
Calldata belongs to the call context. Persistent contract storage survives successful state changes between transactions. Reading an input is not the same as writing a lasting record.
3. Why Solidity parameters can use calldata
External function parameters can use calldata for read-only reference-type data. This can avoid unnecessary copying in some cases. The exact allowed locations depend on type, visibility and compiler rules.
4. Public data and privacy
Transaction input data on a public chain may be observable. A private-looking form does not make names, student marks or addresses confidential once placed in publicly accessible calldata.
5. Input validation is essential
A correctly encoded booking date can still be outside the allowed range, or the caller may lack permission. A contract must validate the intended conditions rather than trust the request.
6. Gas and data size
Transaction data consumes network resources and can affect fees. Large documents should not be placed on-chain merely because calldata can carry bytes.
7. A successful call can still be misleading
A transaction can be included and revert, or execute successfully while the physical kit is unavailable. Read the receipt and authoritative state separately from the outside-world outcome.
8. Paper exercise
Give children a request form with Kit, Date and Requester. Ask which fields are inputs, which rules need checking and what new entry should be written only after approval.
What should a parent or learner check?
Ask what data the contract receives, which network and state reference apply, who may act, which result is independently verifiable and what still depends on a human observation. Digital validity does not guarantee real-world truth.
Try a five-minute paper exercise
Use the activity above and introduce one missing permission, stale record or incorrect input. Ask the learner which check detects the mistake and what remains unresolved. Paper exercises illustrate logic, not real cryptographic security.
When an ordinary system is better
A school can often manage these operations with a conventional database, signed records and role-based permissions. Blockchain is justified only where independent shared verification or governance solves a specific requirement.
Frequently asked questions
Does this make the physical-world claim true?
No. Contract rules establish particular digital outcomes. School results, physical deliveries and human decisions still need reliable evidence.
Do children need cryptocurrency?
No. These examples require no wallet, money or real student information.
Does every blockchain use Solidity?
No. Solidity is associated with Ethereum-compatible smart contracts; other networks use different execution environments and languages.
Continue learning
Read the related chapter, the English Master Blockchain Learning Guide, the Chinese guide and the main Master Blockchain hub.
Sources and limitations
Primary technical reference: https://docs.soliditylang.org/en/latest/types.html#data-location. Broader background: NIST Blockchain Technology Overview. Examples are fictional, and network-specific behaviour should be checked against the current implementation.