A full node downloads and independently validates the entire blockchain: every block's proof of work, every transaction's signatures, and every rule such as the supply schedule, the block size limit and the ban on spending the same output twice. This first download and validation is called Initial Block Download (IBD) and can take from hours to days depending on hardware and bandwidth.
After IBD, a node stays synchronised by validating new blocks and transactions as they arrive, and it relays only what passes its own checks to its peers. Crucially, a node does not trust its peers' claims, it re-derives every conclusion from the raw data and the rules it was compiled with.
This is what makes Bitcoin's rules enforceable without a central authority: miners propose blocks, but nodes decide whether to accept them. A block that breaks a consensus rule is rejected by every properly configured node, no matter how much computing power was spent creating it.
Explain more simply
A node is a computer running Bitcoin software that keeps a copy of the entire transaction history and checks that every new block plays by the rules.
You do not have to trust anyone else's word for what happened: if you run a full node, your own computer verifies everything from scratch and tells you if something is wrong.
Real-world analogy
A node is like an accountant who refuses to accept any invoice unless they personally check the maths, no matter who submitted it or how confidently.
Key facts
- A full node independently validates every block and transaction against the consensus rules.
- Initial Block Download (IBD) is the one-time process of verifying the entire history from genesis.
- Nodes, not miners, ultimately decide which blocks are valid by choosing what to accept and relay.
Common misconception
“Miners control what counts as a valid Bitcoin transaction.”
Miners can choose which valid transactions to include and in what order, but they cannot force acceptance of an invalid block or transaction: every node checks the rules independently and rejects anything that fails, regardless of how much hashing power backed it.[2]
Go deeper
'Running a node' and 'mining' are separate activities that are often confused. Mining proposes new blocks and requires enormous computing power; validating blocks requires only commodity hardware and bandwidth, and it is validation, not hashing power, that ultimately enforces the rules, because miners cannot force nodes to accept invalid blocks.
This separation is why the 2017 block-size debate resolved the way it did: node operators, not miners, held the deciding leverage, since miners produce blocks that are worthless if the economically active nodes on the network refuse to relay or build on them.
Quick check
Answer every question correctly (100%) to complete this lesson.
1.What is Initial Block Download (IBD)?
2.Who ultimately enforces Bitcoin's consensus rules?
Counts towards your streak in this browser.
Extra exam questions
Every question here counts towards your accuracy, XP and rank. No guessing: every answer is explained.
Quick check
Answer every question correctly (100%) to complete this lesson.
1.What is the primary job of a Bitcoin full node?
2.Does running a full node require mining hardware?
3.What happens if a miner produces a block that breaks a consensus rule?
4.Why are full nodes described as giving users 'their own truth'?
5.What data does a full node typically store to validate the entire chain?
6.What is a 'lightweight' or SPV node?
7.Why does a large, distributed set of full nodes strengthen Bitcoin?
8.Do nodes and miners perform the same role in Bitcoin?
Counts towards your streak in this browser.
Sources
- Bitcoin Core documentation, Bitcoin Core project
Reference implementation documentation, including validation and release notes.
- Bitcoin developer documentation, bitcoin.org / Bitcoin Optech glossary