Part I · Start from everyday life

Nodes and trust boundaries

By KangPublished: Chain snapshot: , block 12117419

“Hard for one party to tamper with” does not mean “always true, always safe, never changeable”.

What a node is

A node is a computer running blockchain software that stores or validates on-chain data. With an ordinary web request you usually have to trust whatever the server returns; with a blockchain, different nodes can each check that transactions follow the same rules. Nodes differ in their roles and in how much data they keep: some keep the full history (archive nodes), others only recent state.

The labs in this book used a free public RPC node:

https://ethereum-sepolia-rpc.publicnode.com

It needs no API key. The trade-offs are limited speed and reliability and no archive data: asking for the state at an old block may fail. That is why the P0 review rebuilt the upgrade path locally instead of paying for an archive node (see Chapter 15).

Everyday analogy: a shared mall checkout

Suppose three shops share a points ledger that no single shop can rewrite. Shop A claims it added 10 points for a customer; the other shops can check by the rules whether that change is valid.

But that does not prove the customer really bought anything. Facts that happen offline still have to be entered by a trusted person, device or institution.

Four things a blockchain does not solve on its own

  1. Real-world truth (the oracle problem): a false report made before data goes on-chain is still recorded faithfully.
  2. Privacy: addresses and interactions on a public chain can usually be traced by anyone.
  3. Lost keys: losing a private key is not like forgetting a website password. There is no “reset password” button.
  4. Buggy contracts: code can be executed in public, and it can also execute the wrong logic in public.

Where this shows up in the labs

  • Chapter 9: 1,000 MBox were sent to an address that has no private key, so they can never be moved: an extreme case of a lost key.
  • Chapters 14–15: the P0 review still found a Medium-severity issue. Putting code on-chain does not make design flaws disappear.