Bitcoin’s blockchain underwent an unusual two-block reorganization on March 23, as competing mining pools clashed over block production near height 941880. The episode, quickly resolved by the network’s longest-chain rule, left user funds and transaction data entirely unharmed.
How the Reorg Unfolded
Bitcoin developer and observer b10c first flagged the event. “We just had a rare-ish two block fork/reorg between Foundry and AntPool+ViaBTC. Foundry mined six blocks in a row,” he wrote on X, later correcting to “seven, Foundry mined seven blocks in a row.” The rival branch, backed by Antpool and ViaBTC, managed to extend its own chain simultaneously, creating two parallel chains of equal length for a brief window. Different nodes temporarily recognized different chains as valid — a standard outcome when blocks are discovered at nearly the same time.
The tie did not last. Foundry USA leveraged its significant hashrate share to mine consecutive blocks, quickly building a longer chain. Once Foundry’s chain surpassed the competing branch, the entire network converged on it, abandoning the shorter version. The blocks mined by Antpool and Viabtc were orphaned — removed from Bitcoin’s canonical history. However, all transactions included in those blocks returned to the mempool and were later confirmed on the winning chain. No funds were lost or double-spent.
Why It Happened
The timing of the reorg is notable. Shortly before the event, Bitcoin underwent a 7.76% downward difficulty adjustment, one of the largest this year. Simultaneously, global hashrate had slipped from earlier highs, reducing the competitive pressure slightly and raising the odds of near-simultaneous block discoveries. This combination can produce brief forks like the one seen on March 23. Mining concentration also played a role: Foundry USA controls a large share of global hashrate, giving it a decisive advantage in tight races. Larger pools can chain together blocks faster, leaving smaller competitors with orphaned blocks.
Nakamoto Consensus in Action
Short reorganizations — especially single-block ones — happen periodically due to network latency and simultaneous discoveries. Two-block reorganizations are less common but remain well within expected parameters. The event serves as a clean, real-world example of Nakamoto consensus resolving conflicts without human intervention. No exploit, bug, or malfunction was detected. The network simply did what it was designed to do: converge on the chain with the most cumulative proof-of-work. Within minutes, all nodes agreed, and Bitcoin continued processing transactions as usual. In other words, nothing broke — and nothing needed fixing.