The basic idea
Nodes independently check Bitcoin
Bitcoin does not rely on one central server to maintain its transaction history.
Instead, independently operated computers run Bitcoin software and communicate with one another.
Each full node downloads and verifies blockchain data according to the rules encoded in the software it runs.
A node does not accept a transaction or block simply because another participant claims it is valid.
Simple definition
A Bitcoin node is a computer that checks Bitcoin's rules for itself and shares valid network information with other nodes.
Node responsibilities
What does a Bitcoin node do?
Full nodes perform several roles that help Bitcoin operate without a central authority.
Verify transactions
Nodes check that transactions follow Bitcoin's rules before accepting and relaying them.
Verify blocks
Nodes inspect every proposed block and reject it if it breaks any consensus rule.
Maintain blockchain data
Full nodes store enough blockchain information to independently verify Bitcoin's transaction history.
Relay information
Nodes share valid transactions and blocks with other connected participants.
Enforce consensus rules
Each node independently decides which transactions and blocks it considers valid.
Support wallets
Wallets can connect to a personal node instead of relying on a third-party server.
Verification process
How a node handles a transaction
Nodes verify information before accepting and sharing it.
A transaction reaches the node
The transaction may arrive from a wallet or another connected Bitcoin node.
The node checks the rules
It verifies signatures, inputs, output values and other transaction requirements.
Valid transactions enter the mempool
The node temporarily stores valid unconfirmed transactions in its own mempool.
The transaction is relayed
The node may share the valid transaction with other connected nodes.
A miner includes it in a block
A miner may select the transaction and include it in a proposed block.
The node verifies the block
The node checks the block independently before adding it to its accepted blockchain.
Consensus enforcement
Nodes decide what they will accept
Each Bitcoin node independently applies the consensus rules contained in its software.
It does not need permission from miners, developers, exchanges or other node operators.
A node rejects any transaction or block that violates the rules it enforces.
This is how Bitcoin can maintain shared rules without one central organisation controlling verification.
Validation rules
What rules does a node check?
Transactions provide valid authorisation for the bitcoin being spent.
Inputs exist and have not already been spent.
Transactions do not create bitcoin from nothing.
Blocks include valid proof-of-work.
Blocks remain within permitted size and weight limits.
Miner rewards do not exceed the amount allowed by the protocol.
Transactions and blocks follow the required script and consensus rules.
Important distinction
Nodes and miners are different
Miners propose blocks. Nodes determine whether those blocks follow the rules.
Main role
Node
Checks transactions and blocks against Bitcoin's rules.
Miner
Builds candidate blocks and performs proof-of-work.
Creates blocks
Node
No. A normal node does not compete to create blocks.
Miner
Yes. Miners compete to propose the next block.
Enforces rules
Node
Yes. Each node independently rejects invalid data.
Miner
Miners must follow the rules if they want nodes to accept their blocks.
Requires specialised hardware
Node
No. A normal computer with sufficient storage can run a node.
Miner
Competitive mining normally requires specialised ASIC equipment.
Earns block rewards
Node
No. Running a normal node does not earn bitcoin automatically.
Miner
A successful miner may earn the block subsidy and transaction fees.
Invalid blocks
What happens if a miner breaks the rules?
A miner could attempt to broadcast a block that creates too much bitcoin or includes an invalid transaction.
Bitcoin nodes independently inspect the block before accepting it.
Nodes running the normal rules reject the block, regardless of how much computing power the miner used.
The miner would have spent electricity producing a block that valid nodes refuse to recognise.
Node configurations
Different ways to run a full node
Archival full node
Stores the complete blockchain history and independently verifies all blocks and transactions.
Pruned full node
Fully verifies the blockchain but removes older block data to reduce storage requirements.
Listening node
Accepts incoming connections from other Bitcoin nodes and helps distribute network data.
Non-listening node
Connects outward to other nodes but does not accept unsolicited incoming connections.
Reduced storage
What is a pruned node?
A pruned node downloads and verifies the blockchain from the beginning during its initial sync.
After older blocks have been verified, the node removes much of their stored data to save disk space.
It still independently validates new transactions and blocks.
The trade-off is that it cannot provide the complete historical block archive to other participants.
Peer-to-peer network
How nodes communicate
Bitcoin nodes establish connections with other nodes called peers.
They exchange valid transactions, blocks and information about the current state of the blockchain.
Information spreads from peer to peer rather than through one central server.
A node can disconnect from one peer and continue operating through its other connections.
Initial synchronisation
What happens during the initial block download?
A new full node downloads historical Bitcoin blocks from other nodes.
It verifies the blockchain from the earliest blocks through to the current chain tip.
This process can take considerable time because the node is checking years of transaction and block data.
After synchronisation, the node only needs to process new blocks and transactions as they arrive.
Running a node
What does a node require?
Computer
A desktop, laptop, mini PC or dedicated device capable of running compatible Bitcoin software.
Storage
Enough disk space for blockchain data, or a smaller amount when using pruning.
Internet connection
A reliable connection for downloading and sharing blockchain and transaction data.
Initial sync time
The node must download and verify Bitcoin's historical blockchain before becoming fully current.
Wallet connection
Why connect a wallet to your own node?
Many Bitcoin wallets use external servers to learn about balances, transactions and blockchain activity.
This requires trusting the server's information and may reveal which addresses the wallet is interested in.
Connecting a wallet to your own node allows the wallet to obtain information from infrastructure you control.
The node verifies blockchain data independently before the wallet relies on it.
“Don’t trust, verify” does not mean distrusting everyone. It means important claims—such as your balance, a payment or the supply rules—can be checked by software you choose to run.
Why run one?
Benefits of operating a Bitcoin node
Independent verification
You do not need to trust an exchange, block explorer or wallet server to tell you which transactions are valid. This is the practical meaning of ‘don’t trust, verify.’
Improved privacy
A wallet connected to your own node does not need to reveal its addresses and transaction interests to an external server.
Rule enforcement
Your node personally rejects blocks and transactions that violate the Bitcoin rules you choose to run.
Network resilience
More independently operated nodes make Bitcoin's transaction and block data available through more participants.
Better understanding
Running a node helps users understand how Bitcoin verification and networking work in practice.
Wallet sovereignty
Your wallet can obtain blockchain information from infrastructure you control.
Decentralisation
Why independent nodes matter
Bitcoin is stronger when verification is distributed across independently operated nodes.
Independent operators can choose their own hardware, software version and network connections.
This makes it more difficult for one organisation to control transaction verification or unilaterally redefine the network's rules.
The value comes from independence, not simply from having a large number of identical nodes controlled by one operator.
Common misunderstandings
Node concepts to remember
A node is not the same as a miner
Nodes verify rules. Miners compete to create blocks using proof-of-work.
Running a node does not earn bitcoin
Normal full nodes do not receive block rewards or transaction fees.
Nodes do not vote by majority
Each node independently accepts or rejects data according to the software rules it runs.
A node does not need your wallet
Bitcoin Core can operate as a validating node without storing or connecting to your personal wallet.
Closing the software stops the node
The node only participates in the network while its software is running and connected.
A pruned node still fully verifies
Pruning removes older block files after verification; it does not skip validation.
Knowledge check
Before continuing
What is the main purpose of a Bitcoin full node?
Why does a node independently verify transactions and blocks?
What is the difference between a Bitcoin node and a miner?
What happens when a miner produces an invalid block?
What is the difference between an archival node and a pruned node?
What occurs during the initial block download?
Why might someone connect their wallet to their own node?
Does running a normal node earn bitcoin?
Why are independently operated nodes important for decentralisation?
Full-node validation
Do not trust a blockâ€â€verify every rule
Follow incoming network data through independent proof-of-work, transaction and state validation.
Receive
Peers are sources of data, not authorities. A full node begins by treating incoming data as untrusted.
Visual recap
What a full node does
A node receives network data, checks it against Bitcoin's rules and shares only information it accepts.
Receive
Validate
Store
Relay
References
Further reading
From the 21Relay Library
Recommended reading for this lesson
Optional books selected to reinforce this topic or provide a useful second perspective.
Recommended nextInventing BitcoinYan PritzkerBeginner · Short · EssentialA first technical book about Bitcoin
Another perspectiveMastering BitcoinAndreas M. Antonopoulos, David A. HardingAdvanced · Long · EssentialDevelopers, node operators and serious technical studyLesson summary
Key takeaways
A Bitcoin node independently verifies transactions and blocks.
Nodes enforce the Bitcoin consensus rules contained in the software they run.
Miners propose blocks, while nodes determine whether those blocks are valid.
Invalid blocks are rejected even when they contain valid proof-of-work.
Full nodes communicate through a peer-to-peer network.
Archival nodes retain complete block data, while pruned nodes reduce storage after verification.
A new node must download and verify historical blockchain data during its initial sync.
Connecting a wallet to a personal node can improve verification and privacy.
Running a normal node does not automatically earn bitcoin.
Independent node operators help preserve Bitcoin's decentralisation.