Thursday, October 22, 2026 Plain-English guides to how blockchain and crypto actually work AboutContact
Security

What Is a 51% Attack? How Blockchains Get Rewritten and Why Big Chains Resist It

What is a 51% attack? Learn how attackers rewrite blockchain history, what they can and cannot do, real examples, and why large networks are so hard to attack.

What Is a 51% Attack? How Blockchains Get Rewritten and Why Big Chains Resist It

A 51% attack is one of the most talked-about threats in crypto, and also one of the most misunderstood. It is the scenario where a single person or group controls the majority of a blockchain’s block-producing power and uses it to rewrite recent history. On small networks it has happened many times. On the largest networks it remains theoretical, and the reasons why tell you a lot about how blockchain security really works.

What “51%” Actually Refers To

On a proof-of-work chain, the percentage refers to hashrate, the total computing power spent on mining. On a proof-of-stake chain the equivalent is a majority of staked coins. In both cases, nodes follow a simple rule: the valid chain is the one with the most accumulated work, or the most stake-weighted support. Whoever controls the majority of that resource can, in principle, produce a longer or heavier chain than everyone else combined.

The number 51% is a rule of thumb. An attacker with less can still get lucky over a short period, and an attacker with much more succeeds faster and more reliably.

How the Attack Works, Step by Step

  • 1. Public payment: the attacker sends coins to an exchange, where they are visible on the public chain.
  • 2. Secret mining: at the same time, the attacker mines a private version of the chain in which that payment never happened, or the coins went back to themselves.
  • 3. Cash out: after the exchange credits the deposit, the attacker trades the coins and withdraws something else.
  • 4. Release: the attacker publishes the private chain. Because it is longer, nodes switch to it, and the original deposit disappears from history.

The result is a double spend: the attacker keeps the coins and also walks away with whatever they withdrew. The exchange is left with a loss.

What an Attacker Can and Cannot Do

Can doCannot do
Reverse their own recent transactionsSteal coins from other people’s addresses
Exclude or delay chosen transactionsCreate coins beyond the protocol’s rules
Stop other miners’ blocks from being acceptedChange old history cheaply; cost rises with every block
Damage confidence and the coin’s priceForge signatures or spend without private keys

This matters because a 51% attack does not give anyone access to your private keys. The damage is mostly to recipients who accepted a payment that later vanished, and to the network’s reputation.

Real Examples

Smaller proof-of-work coins have been hit repeatedly. Ethereum Classic suffered several reorganisations in 2019 and 2020, with attackers double-spending large amounts at exchanges. Bitcoin Gold was attacked in 2018 and again in 2020. In these cases the coins shared mining algorithms with larger networks, so attackers could rent enough hashpower for a few hours to overwhelm them.

That is the key weakness. If a small coin uses the same algorithm as a much bigger one, a fraction of the bigger network’s hardware can outmatch the small coin completely.

Why Bitcoin and Ethereum Are Hard to Attack

For Bitcoin, an attacker would need more hashpower than the entire existing global mining industry. That hardware is not available to rent in that quantity, building it would take years and enormous capital, and the electricity bill alone would be huge. Even if successful, the attack would likely crash the price of the very coin the attacker was trying to profit from.

For Ethereum, an attacker would need to acquire a massive share of all staked ETH. Buying that much would push the price up sharply, and if they used it to attack, the protocol can slash their stake and the community can coordinate to reject the attacking chain. The attacker would be burning their own capital.

How Exchanges and Users Protect Themselves

  • Confirmation requirements: exchanges wait for more blocks on smaller or recently attacked chains before crediting deposits.
  • Monitoring: services watch for unusual reorganisations and sudden hashrate spikes.
  • Checkpoints and finality: some networks finalise blocks so they cannot be reverted after a certain point.
  • For you: when receiving a large payment on a small chain, wait for many confirmations before treating it as settled.

Key Takeaways

  • A 51% attack lets someone rewrite recent history, mainly to double-spend their own coins.
  • It does not let an attacker take coins from your wallet.
  • Small chains, especially ones sharing an algorithm with bigger networks, are the realistic targets.
  • Large networks resist it because the cost is enormous and the attack would damage the attacker’s own holdings.

Frequently Asked Questions

Has Bitcoin ever suffered a 51% attack?

No successful majority attack has ever been carried out against Bitcoin. Concerns have been raised at times when a single mining pool approached a very large share of hashrate, and miners have moved away from pools to reduce that risk.

How many confirmations are safe?

It depends on the network and the amount. On Bitcoin, six confirmations is a common standard for large payments. On smaller chains exchanges often require many more.

Can a 51% attack happen on proof of stake?

In principle yes, with a majority of stake, but the attacker risks having that stake slashed and the community can coordinate to reject the attack, making it very costly.

This article is for educational purposes only and is not financial advice. Crypto assets are volatile; do your own research before making decisions.

Blockchain Pulse Editorial

Our team writes original, plain-English explainers on blockchain technology and crypto, checked against primary sources. Read our editorial standards.