Xinjiang power cuts exposed Bitcoin’s mining concentration

Bitcoin’s network entered a conspicuous slowdown on April 17, 2021, after electricity was cut to mining operations in China’s Xinjiang region during coal-industry safety inspections. The interruption did not stop Bitcoin or invalidate its ledger, but it demonstrated how a geographically concentrated loss of computing power could delay the production of new blocks across a nominally global network.

The episode mattered beyond the affected mining companies. Bitcoin depended on miners repeatedly performing proof-of-work calculations, and the network had adjusted its mining difficulty upward on April 15. That setting would remain fixed until the next scheduled adjustment. When a substantial group of machines went offline immediately afterward, the remaining miners had to work at the higher difficulty with less aggregate computing power.

A coal emergency reached the Bitcoin network

The disruption followed serious coal-mine accidents in several Chinese provinces. Xinjiang’s government had reported that flooding struck the Fengyuan mine in Hutubi County at approximately 18:10 local time on April 10, cutting underground power and communications. Eight of the 29 workers underground escaped, while 21 remained trapped as rescue operations began. On April 15, China’s mine-safety regulator publicized the Xinjiang accident alongside incidents in Shanxi and Guizhou and called for broader safety scrutiny.

Contemporaneous cryptocurrency reporting connected the resulting inspections and power interruptions with mining facilities in Xinjiang. CoinDesk reported on April 16 that coal-plant disruptions had removed a material amount of computing capacity from major Bitcoin pools. Its report emphasized that pool hash-rate figures were estimates assembled from operator and pool data, not a direct measurement of miners’ physical locations.

That distinction is essential. Bitcoin records completed blocks, but it does not record the geographic location or electricity source of the machines that attempted to produce them. A decline in observed block frequency can support an inference that effective hash rate fell; it cannot, by itself, prove which province or power station caused the decline. The geographic attribution depended on reports from mining operators and industry participants.

The protocol continued, but more slowly

Bitcoin targets an average interval of roughly ten minutes between blocks and recalibrates difficulty every 2,016 blocks. The target is an average rather than a timetable: individual blocks can arrive seconds apart or require much longer because mining is probabilistic.

Node-derived block-arrival records preserve the slowdown visible on April 17. Those timestamps are stronger evidence of what the network did than short-window hash-rate charts, which estimate computing power from the irregular pace of block discovery. They show continued block propagation rather than a network halt. Transactions could still be confirmed, although reduced block production meant less new block space was becoming available than under the protocol’s target cadence.

The immediate resilience and the concentration risk were therefore two sides of the same event. No central operator was required to restart Bitcoin, and miners elsewhere continued extending the chain. At the same time, the disruption showed that a regional electricity decision could materially affect the network’s global processing rhythm.

What was not established on April 17

The surviving contemporaneous record did not establish that the power cuts caused any particular Bitcoin price movement. Cryptocurrency trades continuously across venues with different liquidity, pricing and time-zone conventions, while the mining interruption coincided with an already volatile market. Treating temporal proximity as proof of market causation would go beyond the evidence available on April 17.

The event also did not prove that one region controlled Bitcoin’s ledger. Hash rate is not equivalent to ownership of coins, software development authority or unilateral control over consensus rules. What the disruption did establish was narrower and still significant: Bitcoin’s mining industry remained exposed to geographic and energy-supply concentration at a moment when the asset was attracting unprecedented institutional attention.

Later context

A subsequently maintained public dataset assembled from Bitcoin Core node logs preserved block-arrival timestamps from the period. It strengthens the record of slower block production but does not independently identify the affected miners or their location.