Why Do Bitcoin Miners Sometimes Mine Empty Blocks? The Mechanics of Header-First Validation
Empty blocks occur when mining pools begin hashing a new block header before fully validating the previous block's transactions, a strategy to maximize hardware efficiency during brief data transmission delays.
Key points
- Miners sometimes mine empty blocks containing only the network reward because they have not yet received the full data of the preceding block.
- Using header-first validation allows miners to start working on the next block immediately, preventing hardware from sitting idle.
- Including user transactions without verifying the previous block risks creating an invalid block that the network would reject.
- The introduction of compact block relay (BIP 152) significantly reduced the time needed to transmit blocks, lowering the frequency of empty blocks.
Bitcoin miners occasionally produce blocks containing zero user transactions because they begin calculating the next block before they have finished receiving the transaction data from the previous one. This phenomenon is a deliberate strategy to prevent computing power from sitting idle during the seconds it takes for a new block to propagate across the network. By mining an empty block—containing only the network-mandated reward transaction—miners avoid accidentally including a transaction that was already processed in the preceding block, which would invalidate their new block entirely.
The Continuous Competition for Blocks
The Bitcoin network regulates the issuance of new $BTC through a proof-of-work consensus mechanism, designed to produce one block approximately every 10 minutes. Miners compete to solve a cryptographic puzzle, and the first to find a valid solution earns the right to append their block to the blockchain, claiming the block subsidy and associated transaction fees. For a deeper understanding of this process, see How Bitcoin Mining Works: Hashing, Difficulty, and Block Rewards.
When a miner discovers a valid block, they immediately broadcast it to the peer-to-peer network. Other miners must then verify the block's validity, update their local ledger, and begin working on the subsequent block. However, information does not travel instantaneously. Network latency, bandwidth limits, and verification times introduce a delay between the moment a block is found and the moment competing miners have fully processed it. During this gap, competing miners face a choice: pause their machines and wait for the full data, or immediately start mining the next block blindly.
Header-First Validation and Network Latency
A Bitcoin block consists of two main components: the block header and the transaction data. The header is a tiny data structure (80 bytes) containing the essential metadata of the block, including a reference to the previous block, the timestamp, and a cryptographic commitment to the transactions included. The transaction data, however, can be up to several megabytes in size.
Because the header is so small, it propagates across the network much faster than the full block. When a mining node receives a new valid header, it knows that a competing miner has found a block. The node can immediately perform header-first validation, verifying the proof-of-work without needing the full transaction list 1. At this exact moment, the miner has the mathematical foundation needed to start building the next block, but lacks the specific transaction details of the block that was just found.
The Empty Block Strategy
If a miner waits for the full block to download and validate before resuming their hashing operations, their hardware sits idle. In an industry with razor-thin margins where profitability depends on continuous operation, turning off machines for even one or two seconds per block represents a significant financial loss.
To bridge this gap, miners employ a technique known as SPV (Simplified Payment Verification) mining. As soon as a mining pool receives a valid block header, it constructs a new template for its miners. Because the pool does not yet know which transactions were included in the previous block, it cannot safely include any transactions from its own mempool (the waiting area for unconfirmed transactions). If the pool were to guess and include a transaction that the previous miner already confirmed, the pool's new block would be rejected by the network for attempting a double-spend or including an already-mined transaction 2.
The only safe transaction to include during this blind window is the coinbase transaction—the special transaction that creates new coins and pays the miner their block subsidy. Therefore, the pool instructs its hardware to mine a block containing only the coinbase transaction. If the pool solves the cryptographic puzzle during this brief window (typically lasting a few seconds), the result is an empty block. Once the full transaction data from the previous block arrives and is validated, the pool quickly switches its miners to a normal, full block template containing user transactions.
Compact Block Relay Optimizations
Historically, the delay in block propagation caused a higher frequency of empty blocks. To address this, Bitcoin developers introduced BIP 152, known as compact block relay, in 2016 3.
Before compact blocks, a node receiving a new block had to download all the transactions within it, even if that node already had most of those same transactions sitting in its local mempool. Compact blocks optimized this process by broadcasting only the block header, short transaction identifiers, and a few missing transactions. Since nodes generally have synchronized mempools, the receiving node can reconstruct the full block using the transactions it already has on hand, requesting only the specific data it lacks.
This optimization reduced the time required to transmit a block from seconds to milliseconds, drastically shrinking the window during which miners must rely on empty block templates. Consequently, the percentage of empty blocks on the network has declined steadily since the implementation of compact block relay, though they still occur occasionally when miners get lucky in the milliseconds immediately following a new block discovery.
The Mathematical Cost of Waiting
To illustrate why miners mine empty blocks, consider the mathematics of network hash rate—the total computational power securing the network.
Assume a large mining pool controls 10% of the global network hash rate, which for this example we will set at 500 exahashes per second (EH/s). The pool is contributing 50 EH/s.
If it takes 2 seconds for a full block to propagate and validate, and the pool chooses to pause its machines during this time rather than mine an empty block, the pool loses 2 seconds of hashing time.
- 50 EH/s × 2 seconds = 100 exahashes of wasted computation.
Since the network aims to find a block every 600 seconds (10 minutes), a 2-second delay represents 0.33% of the total time window for a single block. Over the course of a year (52,560 blocks), pausing for 2 seconds per block means the pool would sit idle for approximately 29 hours. By mining empty blocks during those 2-second intervals, the pool maintains its statistical probability of capturing the block subsidy, avoiding significant revenue leakage over time. For more on the probabilities of block discovery, see Solo Bitcoin Mining vs Pool Mining: The Lottery Math Explained.
Common Misconceptions
- Empty blocks are an attack on the network. Empty blocks are a rational economic response to the physics of data propagation, not a malicious action. They secure the network by adding computational weight to the blockchain, even if they do not clear pending user transactions.
- Miners choose empty blocks to avoid processing large transactions. Processing user transactions generates fee revenue for the miner. Miners always prefer to mine full blocks to collect these fees. Empty blocks are only mined as a temporary fallback when the pool lacks the data required to safely build a full block.
- Empty blocks delay transaction processing significantly. Because an empty block requires the network to find another block to clear transactions, it technically delays confirmation. However, because empty blocks are usually found mere seconds after the previous block, the actual real-world delay to users is negligible.
How This Connects to the Market
The frequency of empty blocks serves as an indirect indicator of Bitcoin's network health and the efficiency of its data propagation. When network upgrades like compact block relay are implemented successfully, the reduction in empty blocks demonstrates improved scalability and latency at the protocol level.
For investors and network participants, understanding empty blocks highlights the critical balance between the block subsidy and transaction fees. As the block subsidy continues to halve every four years, miners will become increasingly reliant on transaction fees for revenue. In a future where the subsidy is negligible, the economic incentive to mine an empty block diminishes entirely, because an empty block would yield almost zero reward. Network engineers and mining pool operators continuously optimize their infrastructure to ensure that full block templates are generated as fast as the laws of physics allow, securing maximum fee revenue for their operations.
Questions this story raises
- Do miners get paid for mining an empty block?
- Yes. Miners who successfully mine an empty block receive the standard network block subsidy, but they do not receive any user transaction fees.
- Are empty blocks bad for the Bitcoin network?
- No. While they do not process user transactions, empty blocks still contribute proof-of-work to the blockchain, enhancing its overall security and immutability.
- Why don't miners just wait for the full block data?
- Waiting for full block data forces mining hardware to sit idle. In a highly competitive industry with tight margins, every second of unused computation represents lost potential revenue.
- Will empty blocks eventually disappear?
- As the block subsidy continues to decrease due to halvings, transaction fees will become a larger share of miner revenue. This will likely reduce the economic incentive to mine empty blocks.
References
- [1] Bitcoin Developer Reference: Block Chain — Bitcoin.org
- [2] BIP 152: Compact Block Relay — Bitcoin Core Developers
Evergreen explainer written by Basis Desk's system and checked by an independent model pass for factual errors and advice language. Figures, fees and rules change — the references above are where to verify current specifics. Market figures marked "at the time of writing" come from live exchange data. Report an error: corrections@basisdesk.news · corrections policy.
The Daily Brief, in your inbox at 07:00 ET
Five stories, the numbers that moved, what to watch. Three minutes. No hype, no advice, unsubscribe in one click.
Get the big crypto stories first
A few alerts a day at most: major breaking news and the morning brief. Switch off anytime.
Not financial advice. Basis Desk publishes information, not recommendations. Crypto assets are volatile and you can lose what you invest.