Three regions, three cost profiles. This lesson sits inside Module I — Architecture — of The EVM, the course that anchors the Ethereum program. It is not a survey; it is the specific, working understanding of "Memory vs. storage vs. calldata" that the rest of the course assumes you carry forward.
- 01Define Memory vs. storage vs. calldata in the precise sense used across The EVM.
- 02Recognize when Memory vs. storage vs. calldata is the correct lens for the situation in front of you, and when it is not.
- 03Apply Memory vs. storage vs. calldata to a concrete case drawn from Architecture, and defend the result in plain language.
- 04Connect Memory vs. storage vs. calldata to the adjacent lessons in this module without collapsing the distinctions between them.
The idea, stated plainly
Three regions, three cost profiles. That single sentence is the whole lesson in compressed form. The rest of the reading unfolds it — what it means when the terms are taken seriously, where it comes from, and what work it does inside The EVM. Read the sentence, then read it again after the sections below; it should carry more weight the second time.
Why it belongs in Architecture
Module I exists because stack, memory, storage. "Memory vs. storage vs. calldata" is one of the pillars of that module: without it, the later lessons either become memorization or lose their bite. Notice which earlier lessons this one leans on, and which later lessons will lean on it — the shape of the module is easier to see once you place this piece.
How the School of Blockchain faculty use it
In practice, working school of blockchain professionals reach for this idea before they reach for a formula or a tool. It is a way of framing the problem so that the right question comes first. The mark of understanding is not that you can recite Memory vs. storage vs. calldata; it is that you catch yourself using it, unprompted, when the situation calls for it.
Common misreadings
The most frequent error is to treat Memory vs. storage vs. calldata as a slogan and skip the mechanics. The second most frequent is the opposite — treating the mechanics as the point, when the mechanics are only there to make the idea usable. Both errors collapse the same distinction, and both are correctable by returning to the one-line summary and asking what it actually claims.
- Memory vs. storage vs. calldata is a working tool, not a slogan.
- Its meaning is set by the module it lives in: Architecture.
- Understanding is demonstrated by unprompted use in the correct situation.
- The adjacent lessons in this module are its natural context; read them together.
- 303 — The EVM, Module I: Architecture — The parent module for this lesson. Re-read the module blurb after finishing the lesson.
- The Anabasis Academy — School of Blockchain, Ethereum — The wider program this lesson serves; the Certificate in Ethereum (Practitioner tier). credential ultimately certifies mastery of ideas like this one.