Glossary
Blockchain node (full, light and archive)
A blockchain node is a computer running the network's software that stores, checks and passes on blocks; full, light and archive nodes keep different amounts of data.
A blockchain node is a computer running a network's client software. It downloads blocks, checks them against the rules and passes valid ones on to its peers. The nodes together are the blockchain: no central server holds the ledger, so every copy that checks the rules for itself makes the record harder to rewrite.
Three kinds of node
- Full node. Downloads and verifies every block from the first one and enforces every rule. It rejects an invalid block even if a majority of miners or validators produced it. To save disk space it may prune old data once checked. Ethereum full nodes typically keep detailed state only for the last 128 blocks.
- Light node. Downloads only block headers and asks full nodes for the rest, checking each answer against the headers. The Bitcoin white paper (2008) called this simplified payment verification. It is cheap enough for a phone but relies on honest full nodes being reachable.
- Archive node. A full node that keeps every past state, so it can answer questions like "what was this address's balance at block 15,000,000?". On Ethereum this runs to terabytes; one client, Erigon, cites under 3 TB. Block explorers and data services run them.
Nodes are not validators
Running a node verifies the chain; it does not produce blocks. On proof-of-stake Ethereum, a validator is extra software attached to a node, and each validator needs at least 32 ETH staked. On Bitcoin, miners produce blocks, and most of them rely on full nodes. Many people run a node with no stake and no mining, to check their own transactions without trusting anyone else's copy of the ledger.
