In this track: The network behind the screen
intermediate · 5 MIN READ

Nodes and the shared state

Computers that check the rules instead of trusting someone else’s copy.

LET’S PICTURE IT

If everyone in a game can check the score themselves, a referee cannot quietly award a million extra points.

SEE IT FOR YOURSELF
Receive, check and share across independent nodesStep 1 / 4
Receive, check and share across independent nodesIncoming dataCandidate instructionNot yet trustedNode AReceives the messageApplies local checksEach participant has a local view of incoming informationNode A checksAuthorizationProtocol validityValid candidateEligible for next stepsNot a finality promiseApplication safety is a different claim from protocol validityNode AShares checked dataNode BChecks for itselfNode CChecks for itselfNode ARules checked✓Node BRules checked✓Node CRules checked✓Agreement on history adds the consensus mechanism

A node receives a proposed transaction or block-related message. Receipt is not the same as accepting its claims.

Animated local teaching model. No wallet, RPC or live blockchain data. Some labels and hashes are abbreviated for readability.

What a node does

A node runs Ethereum client software. It receives blocks, checks transactions and maintains information about the chain. Running your own node lets you verify answers instead of fully trusting a hosted service. Different node types retain different amounts of historical data.

Execution and consensus

An Ethereum node normally uses an execution client and a consensus client. The execution side checks transactions and the EVM. The consensus side follows proof of stake and the choice of chain. A validator also needs validator software and the appropriate stake.

Reading is different from writing

A wallet can ask a node for a balance or simulate a call through JSON-RPC. This does not itself make a new onchain transaction. Writing persistent changes requires a transaction that the network accepts. A hosted RPC can have limits or costs even when a read does not consume onchain gas.

Why this site works offline

Our tools calculate from the inputs in your browser. They do not query balances, resolve ENS names or broadcast transactions. That makes experiments repeatable without API keys. A valid result in a local decoder describes those bytes, not the current state of a real contract.

QUICK CHECK · NO PRESSURE

Must a node also be a validator?

Your progress stays in this browser.
Keep exploring the original referenceethereum.org ↗

Original explanations by EtherTools. Examples are educational and source-linked; this site is independent of the Ethereum Foundation. Our approach.