What is a 51% attack? What majority hash power can and cannot do, the economics that make attacking Bitcoin irrational, and why reserves rely on it.
A 51% attack is the scenario where a single entity controls a majority of Bitcoin's mining hash rate, gaining the ability to reorder recent transactions, censor new ones, and double-spend its own coins by rewriting the latest blocks. It is the canonical theoretical attack on proof-of-work systems โ and, at Bitcoin's scale, one of the most expensive attacks ever conceived.
Control of majority hash power lets an attacker mine a private chain faster than the honest network and then publish it, replacing recent history (a "reorg") and reversing their own recent transactions โ the double spend. They can also refuse to include specific transactions while they maintain the majority. What they cannot do is more important: they cannot steal coins from addresses they don't control, cannot create bitcoin beyond the schedule, cannot change the 21-million cap, and cannot rewrite deep history โ every block they replace must be re-mined at full cost, so transactions with many confirmations become geometrically harder to reverse. The nodes enforce the rules; miners only order the queue.
Attacking Bitcoin means out-computing the entire global network continuously. That requires millions of latest-generation ASICs (years of total global production), gigawatts of contracted power, and industrial facilities โ a multibillion-dollar buildup that would be visible in hash-rate data long before launch. And the payoff is self-defeating: a successful attack collapses confidence in the asset the attacker just spent billions to accumulate infrastructure around. Smaller proof-of-work coins have been 51%-attacked repeatedly; Bitcoin never has, because its security budget โ renewed every ten minutes via the block reward โ dwarfs any rational attack budget.
The 51% question is the first one every treasury committee and defense analyst asks: can someone just rewrite the ledger? Understanding why the answer is "not economically" is prerequisite to holding bitcoin at sovereign scale โ the finality of the US reserve's 328,372 BTC or El Salvador's stack rests on this security model. It's also why nation-state mining concentration (a majority of hash rate sits in identifiable jurisdictions) features in policy debates: the attack is irrational for profit, but state actors optimize for different things. So far, seventeen years of history side with the economics.
The 51% attack is Bitcoin's known theoretical ceiling โ real in small proof-of-work networks, prohibitively irrational at Bitcoin's scale. The ledger's safety isn't an assumption; it's a continuously funded economic fact.
Ballpark the price tag: matching today's network requires on the order of millions of latest-generation ASICs โ several years of global chip production โ plus multi-gigawatt power contracts and facilities, before a single hostile block is mined. Sustaining the attack burns comparable operating costs indefinitely, while the target asset's price (and the attacker's own hardware value) collapses on discovery. Academic estimates put even brief reorg campaigns in the billions of dollars for minutes of disruption, with zero coins stolen from third parties. Compare that to simply buying bitcoin with the same budget, and the market's revealed preference โ accumulation over aggression, visible across our tracker โ looks less like restraint and more like arithmetic.
This attack targets Proof-of-Work, so read that entry first, then Blockchain for what's being defended. Mining explains the industry whose scale makes the attack irrational, and our reserve guide covers why finality matters to governments.
BitcoinReserveTracker Team has verified the information and data provided on this page. Our research team is dedicated to tracking Bitcoin reserves, cryptocurrency regulation, and mining policy across the globe. We verify information using government records, official announcements, and other primary sources to ensure the data remains accurate and regularly updated. Learn how we verify data โ