Bitcoin VerityOpen comparator ↗

Bonus · Financial history and Bitcoin curiosities

The bug that created 184 billion BTC

How an integer overflow bypassed a value check in 2010, how the network removed it and what the event says about immutability.

Article
B08
Reading time
10 minutes
Reviewed
26 September 2026

In a nutshell

In August 2010 a crafted transaction exploited an integer overflow. Two enormous outputs passed a faulty check and created about 184.47 billion BTC. Developers fixed the bug, and nodes and miners adopted a valid chain without that transaction. Supply limits depend on rules and correct implementation.

A child-friendly recap

In very simple terms

In August 2010 a crafted transaction exploited an integer overflow. Two enormous outputs passed a faulty check and created about 184.47 billion BTC. Developers fixed the bug, and nodes and miners adopted a valid chain without that transaction. Supply limits depend on rules and correct implementation.

01

When a number wraps around

Computers store integers within fixed ranges. If a calculation exceeds the maximum and software fails to check it, the result can wrap into a small or negative value. This is integer overflow.

In block 74,638, two outputs of roughly 92.2 billion BTC each pushed the sum outside the old numeric range. The flawed check failed to see the giant total and the old software accepted the block.

02

Fixing the rule and the chain

Users spotted the strange transaction on 15 August 2010. Satoshi and other developers prepared stricter range checks and released version 0.3.11. Nodes had to run the code and miners had to build on the branch without the exploit.

The repaired chain replaced the short invalid history. This was not a valid payment erased under unchanged rules; it was a correction to code that had failed to enforce the intended monetary rule.

03

What immutability means

A blockchain is not a file that can never change. Nodes choose a valid chain with the most accumulated proof of work, and short reorganisations are part of the design. More confirmations make replacement increasingly costly.

Open code and human review still matter. Bitcoin reduces reliance on one administrator but does not eliminate software bugs. Developers may propose code; independent node operators decide what to run.

Bonus · Financial history and Bitcoin curiosities

Terms to know

Integer overflow
A bug in which a result exceeds a numeric type's range and is processed incorrectly.
Reorganisation
Replacement of a recent blockchain branch by another valid branch with more accumulated proof of work.
Implementation
A concrete software program that executes protocol rules.

Common misconception

The incident proved that Bitcoin's 21 million limit never existed.

A more accurate explanation

The intended rule existed, but faulty code failed on an extreme transaction. Corrected nodes rejected that history; the event exposed implementation risk rather than permanently changing issuance.

A more accurate explanation

If developers issued a fix, do they control Bitcoin?

They can write and recommend software but cannot remotely force independent nodes to run it. Coordination was easier in the tiny 2010 network; broad disagreement today could produce separate networks.

B08

Key takeaways

  1. 01The 2010 transaction created about 184.47 billion BTC.
  2. 02An overflow in output-sum validation caused the failure.
  3. 03Corrected nodes and miners built a chain without the transaction.
  4. 04Immutability is economic and consensual, not an absolute ban on every reorganisation.

Reviewed: 26 September 2026

Sources and further reading

Sources support particular facts and definitions; listing one does not mean the editors endorse every view of its author.

01
Original report of strange block 74,638BitcoinTalk
bitcointalk.org ↗
02
NVD: CVE-2010-5139U.S. National Vulnerability Database
nvd.nist.gov ↗
03
Bitcoin Core's current transaction-value checksBitcoin Core source code
github.com ↗

Educational material, not an investment recommendation.