Lesson 0004: Miners, Nodes & the Block Race

Part 1: The Moment of Discovery — What Happens When a Block Is Solved

After trillions of nonce attempts, an ASIC finds a double-SHA-256 hash below the difficulty target. The block is valid. Now what?

The Winning Miner's Immediate Actions

1. The ASIC signals the mining node: "I found it — here's the nonce." The mining software (bitcoind or the pool server) assembles the full block: the 80-byte header (with the winning nonce) plus the complete transaction list (which the header's Merkle root already commits to).
2. The miner broadcasts the block: The mining node sends a block message to every connected peer. This is a push — no inv/getdata round-trip needed. Speed matters: every millisecond of delay increases the chance another miner finds a competing block at the same height.
3. The miner immediately starts on the next block: Even before validation propagates, the miner builds a new block template on top of the one they just found and starts hashing. They want to extend their own chain before anyone else can.

What Every Receiving Full Node Does: The Validation Checklist

When a full node receives a block message, it runs a comprehensive validation gauntlet. Here's the checklist, in order:

Part 2: Two Miners, One Block Height — The Stale Block Race

Bitcoin blocks are found roughly every 10 minutes on average, but the timing is random (a Poisson process). Sometimes two miners find valid blocks within seconds — or even milliseconds — of each other.

What Actually Happens

Block 800,000 —————— Block 800,001 (Miner A finds it first, in Texas)
         \
          —— Block 800,001 (Miner B finds it ~3 seconds later, in Kazakhstan)

Both blocks are fully valid. Both pay the correct subsidy. Both contain valid transactions. But they are at the same height — they both point to block 800,000 as their parent. Only one can survive.

The Timeline of a Chain Split

Why Don't Miners Just Keep Mining on Their Own Block?

A miner who stubbornly continues mining on the stale tip (the one that didn't get the next block) is racing against the entire honest network. The winning chain already has a 1-block lead and the combined hashrate of everyone else building on it. For the stubborn miner to overtake, they would need to find two blocks faster than the rest of the network finds one. Unless they control >50% of hashrate, this is a losing bet.

Rational miners immediately switch. The moment a node receives a valid block at the current height (or higher), it builds a new block template on top of it — even if it was previously mining on a different tip. The incentive is to be the one who finds block 800,002, not to defend a block that's already losing.

Part 3: The Miners-and-Nodes Relationship

This is one of the most misunderstood dynamics in Bitcoin. Let's clarify exactly who does what.

The Power Dynamic: Nodes Rule, Miners Serve

It's tempting to think miners "run" Bitcoin because they produce blocks and earn rewards. This gets the power relationship backwards:

Why Run a Full Node If You're Not Mining?

This is a common question. Full nodes earn no block rewards. They cost money to run (disk space, bandwidth, electricity). Why does anyone bother?

1. Self-sovereign verification: If you run your own node, you don't need to trust anyone. You validate every transaction independently. Exchanges, payment processors, and large holders run nodes to protect their assets.
2. Privacy: Light wallets that query third-party servers leak which addresses belong to you. A full node lets you query your own blockchain — nobody learns your balance or transaction history.
3. Network health: Every full node is a relay point that helps transactions and blocks propagate. More nodes = more resilient network. Running a node is a public good.
4. Economic weight: If a contentious protocol change were proposed, the side that economic nodes (exchanges, custodians, payment processors) choose is the side that retains value. Miners follow the economic majority — they mine where the fees are.

The Full Picture: How It All Fits Together

Let's trace the entire loop — from block discovery through propagation through miner response — in one sequence:

  1. Miner A finds valid nonce
         │
  2. Miner A broadcasts BLOCK to peers
         │
  3. Peers validate (8-step checklist)
         │
  4. Peers relay BLOCK to their peers  ←── Network floods the block
         │
  5. Miner B receives BLOCK
         │
  6. Miner B validates, accepts it as new tip
         │
  7. Miner B abandons current work, builds new template on BLOCK
         │
  8. Miner B starts hashing for block N+1
         │
  9. ~10 min later, someone finds block N+1 → repeat from step 1
      

Common Misconceptions

Key Takeaways

1. Block validation is a gauntlet. Full nodes run an 8-step checklist on every block — header PoW, previous hash, timestamp, Merkle root, size/weight, every transaction's signatures and scripts, coinbase subsidy, and UTXO set consistency. Any failure rejects the entire block.
2. Stale blocks are normal. When two miners find blocks at nearly the same time, the network temporarily splits. The next block breaks the tie — the chain with more accumulated PoW wins, the other is discarded. Transactions in stale blocks return to the mempool.
3. Miners switch instantly. The moment a miner receives a valid new block, they abandon current work and start mining on top of it. Mining on a losing chain is throwing money away — the rest of the network is advancing the winning chain.
4. Nodes are the sovereigns; miners are the servants. Miners expend energy to propose blocks. Nodes independently enforce the rules. If miners produce invalid blocks, nodes reject them regardless of hashrate. Economic value follows the node network, not the miners.
5. The cycle is self-sustaining. Block found → flood the network → validate → relay → miners reset → repeat. No coordinator, no downtime, no single point of failure. Over 880,000 times and counting.

Navigate