Bitcoin mining pool SpiderPool mined an empty block at block height 954,352 this past Saturday, June 20, 2026. The block contained zero transactions — just the coinbase reward. It's a move that reignites a familiar debate about whether mining pools are prioritizing their own efficiency over the network's health.
What an empty block actually is
An empty Bitcoin block isn't a bug. It's a deliberate choice by a miner to skip the mempool and produce a block with no transactions. When SpiderPool mined block 954,352, it collected the standard block subsidy (currently 3.125 BTC) but left every pending transaction untouched. That means users waiting for confirmations had to wait at least one more block — roughly ten minutes — before their transactions had a chance to clear.
Why a pool would do this
Empty blocks are a known strategy in mining. The theory goes that by skipping transaction validation, a pool can get a block out faster and reduce the odds of another pool finding a competing block in the same interval. The trade-off is clear: speed for the pool vs. service for users. SpiderPool hasn't commented on this specific block, but the tactic isn't new. It's happened before, and it will happen again. The question is how often, and whether the cumulative effect on the mempool is something the community should address.
One empty block doesn't crash the network. But when multiple pools do it repeatedly, transaction backlogs grow. For a system that markets itself as reliable and permissionless, every empty block is a small failure of inclusion. The incident at height 954,352 isn't a crisis — it's a reminder that miner incentives don't always align with what users expect. SpiderPool's move is legal under Bitcoin's consensus rules, but it fuels calls for better incentive design, whether through fee markets, policy changes, or software tweaks.
No regulatory action is on the table here. This is an internal Bitcoin debate. But it's one that won't go away as long as pools can profit by leaving transactions behind.
