A technical primer on how these systems work — not on any coin, market or product, none of which appear here. One idea explains most of the rest: a blockchain is a public database that many independent machines keep identical copies of, and nearly every surprising property is the price of removing the operator you would otherwise trust to hold it. That single trade produces the publicness, the permanence, the cost per operation and the finality rules. Read it as engineering and it stops looking like magic: it is a set of expensive trade-offs, most of which an ordinary database wins.
Each chapter opens with the short version. Tap one to read the detail.
A database with no owner, and the bill for that
~2 min
A blockchain is a public database shared across many computers and appended to rather than edited. It buys agreement without an operator anyone must trust, and charges privacy, speed, and the ability to fix a mistake.
Why tampering shows, and what "immutable" really claims
~2 min
Hashing is not encryption: there is nothing to decrypt and no key. It is a one-way fingerprint, and linking each block to its parent's fingerprint is the whole tamper-evidence mechanism. It makes an edit detectable, never impossible.
Possession of a key is the entire security model
~2 min
No account, no password, no reset: an address is computed from a key you generated and registered with nobody. A lost key is final, a copied key total, and a wallet stores the key rather than the assets.
Two ways to record who owns what
~2 min
Ownership is not stored the same way everywhere. One family tracks discrete unspent outputs consumed whole; the other stores a balance per account plus a counter that keeps order. The difference explains change outputs, stuck transactions and irreversibility.
Consensus buys ordering, not validity
~2 min
Consensus does not decide whether a transaction is valid — every node checks that alone. It decides which of several valid histories everyone keeps, and that ordering is paid for with electricity or with destructible capital. The two offer different guarantees.
Who actually enforces the rules
~2 min
No foundation and no vote of holders enforces anything. The rules are whatever independently run software accepts, which makes verification something you either do yourself or delegate, and rule changes something client teams coordinate rather than announce.
A machine every node re-runs, metered by the step
~2 min
Contract code runs on every verifying node and must give identical results everywhere, so no clock, no randomness and no network call exists inside it. Since nobody can know in advance whether a program halts, it is charged per step.
Contracts: what code can see, and why it cannot be patched
~2 min
Deployed bytecode cannot be edited at its address, so every upgrade is indirection rather than a patch. And visibility keywords say who may call a function, never who may read data — the ledger is public whatever you mark private.
Every caller is adversarial, and every bug is permanent
~2 min
Contract code sits where anyone can call it, in any order, from another contract you did not write. Combine that with immutability and a bug's consequences change in kind: no patch, no rollback, and the attacker never touches your interface.
Moving execution elsewhere, and where the trust goes
~2 min
A rollup executes transactions off the main chain and posts the data plus a state commitment back, which is what keeps it checkable. Bridging is different in kind: nothing crosses. Something is locked here and a claim is minted there.
The chain cannot see out, and cannot hide the queue
~2 min
Determinism forbids a contract from fetching anything: outside facts arrive only as transactions someone sends, so a contract fed by one reporter trusts it completely. Publicness runs the other way — whoever orders a block reads your pending transaction first.
Written by Keentune. We are not affiliated with or endorsed by the organizations whose documentation informs this guide, and any linked sources belong to their respective owners.
All exam, test, and product names and trademarks are the property of their respective owners and are used here for identification and reference only. Keentune is independent study practice — not affiliated with, authorized, or endorsed by any of these organizations.