Share article

Bitcoin$62,598.94 didn't "break" this week, it just reminded everyone that mining is getting a little too top-heavy.
Crypto News Summary March 23

Enjoy articles without ads?

Register for free and get unlimited access to all articles.

What happened: a rare 2-block reorg at height 941,881

On Monday (March 23), Bitcoin saw a two-block chain reorganization (reorg) around block height 941,881 after Foundry USA, the network's largest mining pool, briefly mined seven blocks in a row. [1] During that stretch, Foundry's version of the chain ended up with more cumulative proof of work, so nodes did what they are supposed to do: they accepted Foundry's chain as the canonical history. [2]
That process orphaned (discarded) otherwise valid blocks produced by AntPool and ViaBTC. No "rollback" in the social sense occurred, and there was no protocol bug. This is Bitcoin$62,598.94's normal fork-choice rule in action: the chain with the most accumulated work wins.

Reorgs are normal, a two-block reorg is just uncommon

Short reorgs happen when two miners find blocks at nearly the same time, creating a temporary split where different parts of the network see different "tips." Usually the network converges within a block. A two-block reorg is rarer simply because it requires the "losing" side to be extended for an extra block before the "winning" side overtakes it.
Practically, this is why exchanges and high-value merchants still care about confirmation depth. If you are treating 1 confirmation as "final," you are taking on exactly the kind of tail risk a two-block reorg represents. The protocol is doing what it advertised, but your settlement assumptions might be too aggressive.
Bitcoin Holds $70K, Iran US Talks Set Next Move

Why mining concentration is the real headline

The reorg itself is not a security crisis. The uncomfortable part is what made it more likely: hashrate concentration inside a small number of large pools.

When one pool commands a large share of global hashrate, it becomes statistically more likely to mine multiple consecutive blocks, especially during periods of higher variance. That increases the odds of:

  • Longer streaks (like Foundry's seven in a row),
  • Short-lived competing chains when blocks are found close together,
  • More frequent orphaned blocks for smaller pools and solo miners.

None of that automatically implies malicious behavior. It does, however, highlight a structural shift: shrinking margins push miners toward large pools that offer steadier payouts, better fee optimization, and operational tooling. That economic gravity tends to centralize block production even if the underlying miners are geographically distributed.

The timing: difficulty just dropped nearly 8%

The incident also landed only days after a near-8% downward difficulty adjustment, which typically reflects a recent drop in effective hashrate (miners turning off machines, relocating, or otherwise going offline), followed by the network rebalancing. [3]
A lower difficulty environment can amplify variance in block discovery and can change which operators are most competitive on a marginal cost basis. It does not "cause" reorgs, but it can set conditions where streaky outcomes are more visible, especially when a dominant pool is having a lucky run.

Was this selfish mining or an attack?

Some corners of crypto Twitter will inevitably post the "51% attack" meme. This event does not, by itself, prove anything like that. [4]

A two-block reorg can occur from benign causes: propagation delays, near-simultaneous blocks, and normal variance. The key point is that the network resolved it through cumulative proof of work, with no need for coordination or emergency measures.

That said, the broader worry is less about a single spooky reorg and more about how concentrated mining coordination becomes when a handful of pools mediate block templates, transaction selection, and payout routing for a large slice of hashrate. Even if individual miners can switch pools, real-world frictions (fees, tooling, contracts, geography, uptime) mean that "just switch" is not always instant.

What this means for users, traders, and builders

For most users, nothing changes. Bitcoin$62,598.94 kept producing blocks, and finality after several confirmations remained effectively intact.

For businesses that rely on fast settlement, this is a reminder to align confirmation policies with risk:

  • Exchanges and payment processors should sanity-check policies that treat 1 confirmation as final for large transfers.
  • Wallets and infrastructure providers should keep monitoring orphan rates and propagation health, especially during periods of hashrate churn.
  • Miners and pool operators will face renewed scrutiny on pool dominance, censorship-resistance posture, and whether miners retain meaningful control over block construction.
Strategy Seeks $44.1B to Supercharge Bitcoin Buys

What to watch next

If Foundry and a few peers keep gaining share, expect more "rare but normal" events like multi-block reorgs to show up in public dashboards, and more debate about whether pool-level centralization is becoming a real governance risk.

If hashrate disperses (or miners more actively hop pools), the network should see fewer streak-driven quirks, and reorgs should revert to the usual one-block blips most users never notice.

Either way, the tell is simple: watch consecutive-block streaks and pool share. If streaks become routine, the concentration story stops being academic and starts being operational.

Companies Referenced

Foundry logo

Foundry

Bitmain logo

Bitmain

ViaBTC logo

ViaBTC

Tags

#Bitcoin#proof-of-work#Chain reorg#Mining pools#Foundry USA#AntPool#ViaBTC#Confirmations#Mining centralization