Running a Node and How the Network Stays Honest

The Concept

It's tempting to think whoever controls the most mining power controls Bitcoin. This is one of the most common misconceptions about how the network actually works — and understanding why it's wrong is key to understanding Bitcoin's decentralization.

Bitcoin has two distinct roles that are often confused: miners and full nodes. Miners compete to propose the next block, as covered in the previous two lessons. But proposing a block isn't the same as having it accepted. Full nodes — software run by individuals, businesses, and exchanges on ordinary computers all over the world — independently verify every single rule of every block they receive: Is the total subsidy correct for this block height? Are all signatures valid? Does any transaction try to spend a coin twice? Does the block follow the current difficulty target?

If a miner proposes a block that breaks any rule — even a miner with the overwhelming majority of global hash power — every honest full node simply rejects it. The miner wastes all the electricity spent finding that block and earns nothing, because the rest of the network won't build on top of an invalid block. This is the separation of power that keeps Bitcoin decentralized: miners propose, but nodes dispose. Running a full node costs very little (a modest computer and an internet connection) compared to competitive mining, which is why thousands of individuals worldwide can meaningfully participate in enforcing the rules even though only specialized hardware can meaningfully compete to mine.

What a Full Node Actually Does for You

If you run a full node yourself (free software like Bitcoin Core), you download and independently verify the entire transaction history — you don't trust anyone else's summary of the ledger. This matters practically: when your wallet shows a balance, a full node lets you confirm that balance against rules you verified yourself, rather than trusting a company's server to tell you the truth. Most everyday users don't run a full node — they use "light" or custodial wallets that trust someone else's node for this information, a tradeoff covered in Module 3. But the fact that anyone can run one, for the cost of a cheap computer, is what keeps the verification process genuinely decentralized rather than concentrated among a handful of large companies. The more independent nodes exist worldwide, the harder it is for any coalition — governments, large miners, or large companies — to quietly change the rules without the broader network noticing and rejecting the change.

Worked Example

In 2017, a real dispute broke out in the Bitcoin community over whether to increase the "block size" (a technical parameter affecting how many transactions fit in each block). A coalition that included some of the largest mining pools and bitcoin-related companies at the time backed a plan to change this rule. By pure hash-power math, they controlled enough mining share that many expected the change to simply take effect.

It didn't — at least not on the original network. Full node operators, including many individuals running Bitcoin Core software on home computers, did not update their software to accept the new rules. When miners began producing blocks under the new rules, nodes that hadn't adopted the change rejected those blocks as invalid under the rules they were still enforcing. The result was a split: the chain following the old rules continued as Bitcoin, while the new-rules chain became a separate asset. The case demonstrated concretely that hash power alone cannot force a rule change onto a network of nodes that refuse to accept it — enforcement power sits with the people running verification software, not with whoever mines the most blocks. Years later, this episode is still the standard reference case cited whenever someone asks "but what if a few big miners just agreed to change the rules?"

Exercise

Answer this scenario in your own words: A miner with 60% of global hash power creates a block that pays itself 100 BTC instead of the correct, scheduled subsidy. What happens next, and why? Your answer should reference both (a) what honest full nodes do when they receive this block, and (b) why the miner's hash-power advantage doesn't change the outcome. (Expected answer: every honest node checks the subsidy against the rule for that block height, sees it's wrong, and rejects the block regardless of how much hash power produced it — the miner forfeits the block reward and wastes the electricity spent finding it.) Then write one more sentence: if you wanted to personally verify your own Bitcoin balance without trusting any company's server, what would you need to run, based on this lesson?

Recap

• Miners propose blocks; full nodes independently verify and can reject them — this separation is what prevents hash power alone from controlling the network.
• The 2017 block size dispute is a real-world case where node operators, not the largest miners, determined which rules actually took effect.
• Consensus emerges from thousands of independently-verifying nodes agreeing on the same rules, not from trusting any single company, miner, or coalition — the decentralization property that distinguishes Bitcoin from permissioned systems, and the foundation for the self-custody skills covered starting in Module 3.