Foundry Flexes Hashpower: A Two-Block Reorg Proves Bitcoin's Consensus Isn't Just Decentralized Theater

The Bitcoin blockchain just experienced a 'rare-ish' two-block reorganization. Before the "banksters won" brigade starts drafting their tweets, this wasn't an attack or a bug—it's Nakamoto Consensus doing its day job with the ruthless efficiency of a well-coded mercenary.

A spicy multi-block fork briefly emerged in a heavyweight hashing bout between mining pool Foundry and the tag-team duo of AntPool and ViaBTC. Data from researcher b10c shows Foundry USA ultimately clinched victory in this proof-of-work arms race, proving once again that in Bitcoin, hash talks and everything else walks.

The digital drama kicked off at block height 941,880. The network, in a moment of beautiful indecision, split into two perfectly valid chains. On one path, AntPool mined block 941,881, only for ViaBTC to quickly follow up and mine block 941,882, like a well-rehearsed but ultimately doomed relay team.

Not to be outdone, Foundry USA mined its own competing version of block 941,881. It then proceeded to find the very next block, creating its own, superior-in-the-eyes-of-the-network version of block 941,882, essentially telling the other chain, "I'm you, but stronger."

This left the network staring at two chains of equal length, a cryptographic stalemate. The tie was decisively broken when Foundry went full degen mode, mining blocks 941,883, 941,884, and 941,885 in a row, a display of raw hashpower that would make any other pool blush.

The blocks from AntPool and ViaBTC were unceremoniously discarded, becoming 'stale' or 'orphaned'—the blockchain equivalent of getting your lunch money taken. In total, Foundry mined seven consecutive blocks from 941,879 to 941,885, a flex so powerful it probably caused a minor power surge in their data centers.

While single-block reorgs happen periodically—bitcoin's version of a network burp—a two-block reorg is a much rarer spectacle. It simply means the temporary tie between chains lasted for an entire extra block cycle, a slightly longer argument before Nakamoto's code shrugged and picked a winner. The protocol handled it all without breaking a sweat, which is more than can be said for most centralized databases on a Tuesday.