{"id":70133,"date":"2026-03-24T14:05:34","date_gmt":"2026-03-24T14:05:34","guid":{"rendered":"https:\/\/crowdfundjunction.com\/blog\/bitcoin-logs-rare-two-block-reorg-as-mining-pools-clash-network-shrugs-it-off-crypto-news-bitcoin-news\/"},"modified":"2026-03-24T14:05:34","modified_gmt":"2026-03-24T14:05:34","slug":"bitcoin-logs-rare-two-block-reorg-as-mining-pools-clash-network-shrugs-it-off-crypto-news-bitcoin-news","status":"publish","type":"post","link":"https:\/\/crowdfundjunction.com\/blog\/bitcoin-logs-rare-two-block-reorg-as-mining-pools-clash-network-shrugs-it-off-crypto-news-bitcoin-news\/","title":{"rendered":"Bitcoin Logs Rare Two-Block Reorg as Mining Pools Clash\u2014Network Shrugs It Off \u2013 Crypto News Bitcoin News"},"content":{"rendered":"

(Originally posted on : Bitcoin News )<\/b>
\n<\/p>\n

\n

Foundry USA Extends Lead in Bitcoin<\/span> Reorg Race<\/h2>\n

The event unfolded around block height 941880<\/a> on March 23, when competing blocks were mined nearly simultaneously, creating a temporary fork between chains led by the mining pool giant Foundry USA<\/a> and a rival branch backed by Antpool and Viabtc.<\/p>\n

Bitcoin<\/span> developer and \u201cobserver\u201d b10c discovered the reorg. \u201cWe just had a rare-ish two block fork\/reorg between Foundry and AntPool+ViaBTC. Foundry mined six blocks in a row,\u201d the developer wrote<\/a>. \u201c*seven, Foundry mined seven blocks in a row,\u201d the X account b10c added<\/a>.<\/p>\n

<\/p>\n

Within seconds, both sides extended their versions of the chain, producing two parallel branches of equal length. For a short window, different nodes<\/span> recognized different chains as valid, a standard outcome when blocks are discovered at nearly the same time. The tie did not last long.<\/p>\n

Foundry USA pulled ahead by mining additional consecutive blocks, ultimately extending its chain beyond the competing branch. Once it established the longer chain, the network followed suit, abandoning the shorter version.<\/p>\n

The rival blocks mined by Antpool and Viabtc were marked as \u201corphaned,\u201d meaning they were removed from Bitcoin<\/span>\u2019s canonical history. Transactions included in those blocks were not lost; they returned to the mempool and were later processed again.<\/p>\n

Analysts and onlookers<\/a>, including Bitcoin<\/span> observer b10c, described the episode as routine behavior under Bitcoin<\/span>\u2019s proof-of-work system. No exploit, double-spend, or malfunction was detected. If anything, the system did exactly what it is designed to do.<\/p>\n

Short reorganizations\u2014especially single-block events\u2014happen from time to time due to network latency and simultaneous discoveries. Two-block reorganizations are less common, but still well within expected parameters. The timing is notable.<\/p>\n

The reorg came shortly after a 7.76% downward difficulty adjustment, one of the largest declines this year. At the same time, global hashrate<\/span> has slipped from prior highs, easing competition just enough to increase the odds of near-simultaneous block discoveries.<\/p>\n

That combination can produce brief forks like this one. Mining concentration also played a role. Foundry USA, which controls a significant share of global hashrate<\/a>, was able to string together multiple blocks and decisively win the race. Larger pools tend to have an edge in these moments, occasionally leaving smaller competitors with orphaned blocks.<\/p>\n

Still, there was no broader disruption. The network converged within minutes, users saw no impact, and Bitcoin<\/a> continued processing transactions as usual. The episode serves as a clean, real-world example of Nakamoto consensus<\/a> resolving conflicts without human intervention.<\/p>\n

In other words, nothing broke\u2014and nothing needed fixing.<\/p>\n

FAQ \ud83d\udd0e<\/h2>\n