What full nodes verify, what they do not do and why running one changes your trust model. The explanation names what wallets, nodes, and miners each do so their roles do not blur together.
- Full nodes independently validate the entire ruleset.
- Mining power cannot make an invalid block valid to a node.
- A node improves sovereignty but is not maintenance-free.
What a node checks
A full node downloads blocks and independently validates proof of work, issuance, scripts and transaction rules. It can answer a wallet's questions without relying entirely on someone else's server.
Nodes are not miners
Mining proposes the ordering of valid transactions and competes for block rewards. Nodes decide whether proposed blocks follow the rules they run. One operator may run both, but the functions are distinct.
Name the layer and the actor. Wallets create transactions, nodes check rules, miners propose blocks, and Lightning peers manage channels.
Privacy and operations
A personal node can reduce information leaked to public wallet servers, especially when paired with thoughtful network configuration. It still requires disk, bandwidth, updates and secure administration.
What your node does that a wallet cannot
A full node downloads every block since 2009 and checks every transaction against every rule: signatures, no double spends, subsidy amounts, block size, script validity. Once synced, it keeps doing that for every new block. A wallet that connects to someone else's node trusts that node's answer about your balance and about which chain is real.
A wallet connected to your own node trusts nothing but the rules. That difference is invisible on a normal day and decisive on the day a server lies, is hacked, or follows a fork you did not choose.
Setting one up without surprises
Bitcoin Core is the reference implementation; download it only from bitcoincore.org and verify the signatures, which the release notes explain. On first run it will sync the whole chain — several hundred gigabytes over hours to days depending on disk speed and bandwidth. Set the database cache high during sync and lower it afterwards.
Choose pruned mode if disk is scarce: it validates everything and keeps a few gigabytes. Connect your wallet to it over the local network or through Tor. The node planner on this site turns those choices into disk, memory and bandwidth figures for the hardware you have.
Nodes, miners and who decides the rules
Miners produce blocks; nodes decide whether to accept them. A block that breaks a consensus rule is discarded by every node no matter how much work it carries, so miners cannot change the rules unilaterally. Neither can developers, who can only publish software; a change takes effect when node operators choose to run it.
This is why Bitcoin's upgrades are slow and conservative, why a broadly run node network matters for the system's independence, and why running one is described as participating in governance even though it earns nothing.
Trace the rule through the network
Follow one transaction from wallet signing to node validation, mempool relay, block inclusion, and confirmations. That sequence shows which facts come from consensus and which depend on local policy.
Common questions
Do I need to run a node to use Bitcoin?
No. Wallets can rely on someone else's node. Running your own means you verify every rule yourself instead of trusting a server, and your wallet's addresses are not revealed to a third party. It is a privacy and verification choice rather than a requirement.
What hardware does a full node need?
A modest computer with an SSD of several hundred gigabytes, a few gigabytes of memory and an unmetered internet connection. Initial sync downloads and checks the entire history and can take from hours to days depending on the machine; pruned mode reduces storage to a few gigabytes.
Do nodes earn bitcoin?
No. Only miners receive the block subsidy and fees. Nodes are run for verification, privacy and the ability to broadcast one's own transactions directly; the incentive is control, not income.
Sources and further reading
Primary documents this guide draws on. Links open the original publisher.
- Running a full node bitcoin.org
- Full node Bitcoin Wiki
- Bitcoin Core releases bitcoincore.org
- BIP 157: Client-side block filtering Bitcoin Improvement Proposals