Definition
Stale Block is a validly mined Bitcoin block that arrives too late to become part of the chain that the network accepts, because another miner already found a block at the same height and that competing block propagated to the majority of nodes first.
Also known as: stale, orphan block (loosely), detached block.
How a block goes stale
Bitcoin is a race. Thousands of miners hash against the same block height at once, and only one winner can extend the longest chain. When two miners solve valid blocks at nearly the same moment, the network temporarily splits: some nodes see one block first, some see the other. As the next block is found, one branch becomes the longest chain and the other is abandoned. The discarded block — fully valid proof-of-work, just on the losing side — is stale.
The decisive factor is propagation delay: how quickly your solved block reaches the rest of the network. A block that takes longer to relay has more chance of being out-raced by a competitor’s block discovered seconds later. This is also why payouts are not final the instant a block is found; pools and exchanges wait for confirmations before treating coins as spendable, precisely because the chain can briefly fork and re-settle.
Stale block vs. orphan block vs. stale share
These three terms get tangled together, so it is worth separating them. A stale block lost the chain-extension race but its parent is known and accepted. An orphan block is technically a block whose parent the node has not yet seen, though in everyday mining talk people often use “orphan” and “stale” interchangeably for any block that did not make the canonical chain. A share is a different animal entirely: it is the unit of work a mining pool counts toward your payout, and a stale share is a share submitted for a job that the pool has already retired.
The economics are simple: pools do not pay out for stale (orphaned) blocks at all, and even a winning block’s reward only matures after roughly a hundred-and-twenty confirmations before it can be spent. A single stale block is the rare, dramatic version of a problem your rig faces constantly in miniature: stale shares.
Why an ASIC or home miner cares
If you run an ASIC at home, you will almost never personally mine a full block that goes stale — but the same mechanics quietly tax you through stale shares. A stale share happens when your chips find a valid nonce for a job the pool has already cleared because a new block arrived and a fresh block template was pushed. That work doesn’t count: depending on timing it is either discarded locally before submission or returned by the pool as a stale reject — not because the share was invalid, but because it arrived too late.
The defense is speed in the work pipeline. Pools that detect new blocks in well under a second (via block-notify hooks or ZMQ) and push fresh work every thirty seconds keep the stale-share window tiny. On the miner side, a good Stratum protocol implementation caches several jobs and interrupts current work the instant a new block notification lands, switching the hashboards onto the new template fast. Firmware quality genuinely matters here: faster job-switching and tight Stratum handling shave the stale rate, and an open tuning stack lets you watch discarded-versus-rejected counts directly. You can compare how different stacks handle this on our firmware comparison page.
For solo mining and lottery rigs like a Bitaxe, the stakes are different but real: if you ever do win the lottery and find a block, a slow internet link or a laggy pool can let a competitor’s block out-propagate yours, turning your once-in-a-lifetime block reward stale. Low-latency connectivity and a fast node are cheap insurance. As mining decentralizes — more sovereign miners, more independent templates, one more layer away from a handful of large pools — keeping propagation fast keeps everyone’s odds honest. Explore home and open-source rigs in our Bitaxe hub.
Related terms: Orphan Block, Longest Chain Rule, Propagation Delay, Share, Confirmations, Block Template
In Simple Terms
A valid block not included in the main chain because a competing block was accepted first.
Stale Block is a validly mined Bitcoin block that arrives too late to become part of the chain that the network accepts, because another miner already found a block at the same height and that competing block propagated to the majority of nodes first.
Also known as: stale, orphan block (loosely), detached block.
How a block goes stale
Bitcoin is a race. Thousands of miners hash against the same block height at once, and only one winner can extend the longest chain. When two miners solve valid blocks at nearly the same moment, the network temporarily splits: some nodes see one block first, some see the other. As the next block is found, one branch becomes the longest chain and the other is abandoned. The discarded block — fully valid proof-of-work, just on the losing side — is stale.
The decisive factor is propagation delay: how quickly your solved block reaches the rest of the network. A block that takes longer to relay has more chance of being out-raced by a competitor's block discovered seconds later. This is also why payouts are not final the instant a block is found; pools and exchanges wait for confirmations before treating coins as spendable, precisely because the chain can briefly fork and re-settle.
Stale block vs. orphan block vs. stale share
These three terms get tangled together, so it is worth separating them. A stale block lost the chain-extension race but its parent is known and accepted. An orphan block is technically a block whose parent the node has not yet seen, though in everyday mining talk people often use "orphan" and "stale" interchangeably for any block that did not make the canonical chain. A share is a different animal entirely: it is the unit of work a mining pool counts toward your payout, and a stale share is a share submitted for a job that the pool has already retired.
The economics are simple: pools do not pay out for stale (orphaned) blocks at all, and even a winning block's reward only matures after roughly a hundred-and-twenty confirmations before it can be spent. A single stale block is the rare, dramatic version of a problem your rig faces constantly in miniature: stale shares.
Why an ASIC or home miner cares
If you run an ASIC at home, you will almost never personally mine a full block that goes stale — but the same mechanics quietly tax you through stale shares. A stale share happens when your chips find a valid nonce for a job the pool has already cleared because a new block arrived and a fresh block template was pushed. That work doesn't count: depending on timing it is either discarded locally before submission or returned by the pool as a stale reject — not because the share was invalid, but because it arrived too late.
The defense is speed in the work pipeline. Pools that detect new blocks in well under a second (via block-notify hooks or ZMQ) and push fresh work every thirty seconds keep the stale-share window tiny. On the miner side, a good Stratum protocol implementation caches several jobs and interrupts current work the instant a new block notification lands, switching the hashboards onto the new template fast. Firmware quality genuinely matters here: faster job-switching and tight Stratum handling shave the stale rate, and an open tuning stack lets you watch discarded-versus-rejected counts directly. You can compare how different stacks handle this on our firmware comparison page.
For solo mining and lottery rigs like a Bitaxe, the stakes are different but real: if you ever do win the lottery and find a block, a slow internet link or a laggy pool can let a competitor's block out-propagate yours, turning your once-in-a-lifetime block reward stale. Low-latency connectivity and a fast node are cheap insurance. As mining decentralizes — more sovereign miners, more independent templates, one more layer away from a handful of large pools — keeping propagation fast keeps everyone's odds honest. Explore home and open-source rigs in our Bitaxe hub.
Related terms: Orphan Block, Longest Chain Rule, Propagation Delay, Share, Confirmations, Block Template