Validators propose and vote; nodes check that the rules hold.
LET’S PICTURE IT
A proposer suggests a new notebook page. Other participants check it and sign votes, with something valuable at stake.
SEE IT FOR YOURSELF
Receive, check and share across independent nodesStep 1 / 4
A node receives a proposed transaction or block-related message. Receipt is not the same as accepting its claims.
A node receives a proposed transaction or block-related message. Receipt is not the same as accepting its claims.The node checks the relevant authorization and protocol rules. Popularity does not make an invalid state transition valid.Valid candidate data can propagate to peers. Connections and timing differ, so there is no perfect simultaneous worldwide view.Peers validate under the same protocol rules. This illustration is about verification and propagation, not a complete proof-of-stake consensus algorithm.
Animated local teaching model. No wallet, RPC or live blockchain data. Some labels and hashes are abbreviated for readability.
Proposals and attestations
Ethereum uses proof of stake. Validators lock ETH as collateral and take part in proposing blocks and making attestations, which are votes about the chain. A node still checks whether each block follows the protocol. A popular invalid block does not become valid just because many votes mention it.
Why put value at stake?
Validators earn rewards for correct participation and can face penalties for missed duties. Certain provable conflicting actions can cause slashing, a more severe penalty. These incentives help make attacks costly, while independent verification enforces the execution rules.
Inclusion is not finality
A transaction can appear in a block before the chain finalizes it. The head can change in a reorganization. Finality comes from checkpoint agreement with enough stake participating. Network disruption or attacks can delay it, so do not treat a fixed countdown as a guarantee.
What the picture leaves out
The network illustration is a simplified view. Real Ethereum has slots, epochs, fork-choice rules and checkpoint votes, not three computers taking turns in perfect harmony. Once you understand the basic relationship, read the primary documentation for the actual protocol.
QUICK CHECK · NO PRESSURE
Does validator agreement make an invalid state transition valid?
Consensus chooses among valid histories. Nodes independently enforce validity rules.