Full Node
node · blockchain
Software that independently validates blocks and transactions against a network's consensus rules.
A full node independently checks blocks and transactions rather than accepting another service's view of validity. It verifies proof of work, transaction inputs, scripts, value conservation, issuance, and the other consensus rules for its network.
"Full" describes validation, not permanent storage of every historical block. An archival node retains complete block data, while a pruned full node can discard older block files after validation and keep the state needed to validate new activity.
Full-node software may also relay blocks and unconfirmed transactions, maintain a mempool, serve peers, expose local APIs, and support wallets. These roles can be configured separately, and running a full node does not necessarily mean mining, indexing every address, or holding private keys.
Using a local node can reduce dependence on explorers or wallet servers and avoid sending them every queried address. The operator still relies on the chosen software, build, hardware, configuration, peers, and their own interpretation of which network rules to follow.
Related terms
Node
→Software that participates in a peer-to-peer network by validating, serving, relaying, or requesting blockchain data.
network · blockchain
Block
→A batch of valid transactions added to a blockchain, linked to the previous block by a cryptographic hash.
mining · blockchain · security
Transaction
→A serialized state transition that a blockchain can validate, relay, and include in a block.
blockchain · technical
Simplified Payment Verification (SPV)
→A lightweight verification method that checks block headers and Merkle proofs without downloading full blocks.
security · scaling