Bitcoin recently went through a rare two-block chain reorganization, a short-lived event that briefly split the network between competing mining pools before consensus was restored automatically. The incident took place around block height 941880 on March 23, when nearly simultaneous block discoveries created two parallel branches of the blockchain.
A brief fork between major mining pools
According to the source material, the temporary split formed between a chain led by Foundry USA and a rival branch backed by Antpool and ViaBTC. Bitcoin developer and observer b10c flagged the event, noting that Foundry then mined a streak of additional blocks that allowed its branch to pull ahead. The report states that Foundry mined six to seven blocks in a row, enough to decisively win the race for the canonical chain.
For a short period, nodes across the network did not all agree on the same chain tip. That outcome is normal in Bitcoin’s proof-of-work system when blocks are found at nearly the same time and propagation delays cause different nodes to see different valid blocks first. In such moments, the network effectively waits for one branch to gain a lead. Once that happens, consensus converges on the chain with the greater accumulated proof-of-work.
Why the reorganization happened
Short reorganizations are not unknown in Bitcoin. Single-block reorgs can occur from time to time because of network latency or tight mining races. A two-block reorg is less common, but it still falls within expected behavior under Bitcoin’s design. In this case, the event appears to have been driven by ordinary mining competition rather than any protocol failure or malicious action.
The report also points to broader network conditions that may have increased the odds of a close race. Shortly before the incident, Bitcoin underwent a 7.76% downward difficulty adjustment, described as one of the larger declines of the year. At the same time, global hashrate had retreated from earlier highs. That combination can slightly increase the chances of near-simultaneous block discoveries, which in turn makes temporary forks more likely.
Mining concentration may also have influenced the outcome. Foundry USA controls a meaningful share of Bitcoin’s global hashrate, and larger mining pools often have an advantage once a fork begins. If a large pool can quickly mine successive blocks, it can turn a tie into a clear lead, forcing the rival branch out of the main chain.
No funds lost, no exploit detected
Although the word “reorg” can sound alarming, the source makes clear that the event did not lead to broader disruption. There was no exploit, no double-spend, and no system malfunction. Once Foundry’s branch became longer, the network accepted it as the valid chain and discarded the competing version.
The blocks mined on the losing branch by Antpool and ViaBTC were classified as orphaned blocks. That does not mean user transactions disappeared. Instead, transactions included in those blocks were returned to the mempool and later processed again in subsequent valid blocks. In practical terms, users did not lose funds, and the network continued operating as intended.
The source emphasizes that convergence happened within minutes and that users saw no meaningful service interruption. Bitcoin continued processing transactions normally, making the episode a real-world demonstration of Nakamoto consensus working exactly as designed: when two valid histories compete, the network eventually settles on the one with more cumulative work, without requiring human intervention.
What the incident says about Bitcoin’s design
Rather than exposing a weakness, the reorganization appears to highlight the resilience of Bitcoin’s consensus model. Temporary forks are a built-in possibility in any proof-of-work system where geographically distributed participants discover blocks independently. The protocol does not attempt to prevent every short-lived disagreement instantly. Instead, it resolves those disagreements by allowing miners to extend competing branches until one becomes dominant.
That process can occasionally produce orphaned blocks, especially when major pools are closely matched in timing. But as this event showed, the existence of a short fork does not automatically imply danger to user funds or chain integrity. The key question is whether the network can resolve the conflict cleanly. In this case, it did.
The incident also illustrates the influence of large mining pools in moments of uncertainty. Because Foundry USA was able to mine a sequence of additional blocks, it transformed a temporary split into a settled outcome quickly. That dynamic is important for observers watching mining centralization, even if nothing abnormal occurred in this specific case.
In the end, the takeaway is straightforward: Bitcoin experienced a rare but expected two-block reorganization, the network resolved it on its own, and users were unaffected. Far from signaling a crisis, the event served as a reminder that Bitcoin’s consensus rules are designed to handle exactly this type of brief conflict.