Bitcoin Value Overflow 184 Billion Minting Incident

Notice: This page is a new case study and some aspects have not been fully researched. Some sections may be incomplete or reflect inaccuracies present in initial sources. Please check the References at the bottom for further information and perform your own additional assessment. Please feel free to contribute by adding any missing information or sources you come across. If you are new here, please read General Tutorial on Wikis or Anatomy of a Case Study for help getting started.

Notice: This page contains sources which are not attributed to any text. The unattributed sources follow the initial description. Please assist by visiting each source, reviewing the content, and placing that reference next to any text it can be used to support. Feel free to add any information that you come across which isn't present already. Sources which don't contain any relevant information can be removed. Broken links can be replaced with versions from the Internet Archive. See General Tutorial on Wikis, Anatomy of a Case Study, and/or Citing Your Sources Guide for additional information. Thanks for your help!

Bitcoin Talk Forum

In August 2010, Bitcoin's source code was exploited by an anonymous individual, resulting in the creation of an enormous amount of Bitcoin in block 74,638—specifically 184,467,440,737.09551616 Bitcoin, distributed to two addresses. Bitcoin developer Jeff Garzik noticed this anomaly and termed it an "overflow bug," where the code failed to check transactions if outputs overflowed during summation. This prompt action preserved Bitcoin's value and prevented potential devaluation caused by the exploit. The incident didn't impact Bitcoin's price negatively; in fact, its value increased over 300% from $0.07 to $0.30 between the patch and year-end 2010. Satoshi's quick intervention demonstrated Bitcoin's resilience and bolstered confidence in the concept.

About Bitcoin

Bitcoin (BTC) is a decentralized cryptocurrency created in 2009 by an anonymous entity known as Satoshi Nakamoto. Designed to function as a form of money and payment, Bitcoin eliminates the need for trusted third parties like banks, enabling direct financial transactions. As the most recognized and largest cryptocurrency, Bitcoin has paved the way for the emergence of numerous other cryptocurrencies.

The Reality

An unfortunate overflow vulnerability was present in the original bitcoin software.

What Happened

"In August 2010, Bitcoin’s source code was exploited by someone who to this day remains anonymous. Enter block 74,638, the fateful block that created 184,467,440,737.09551616 Bitcoin, with two addresses receiving just over 92 billion Bitcoin each—92,233,720,368, to be specific."

Key Event Timeline - Bitcoin Value Overflow 184 Billion Minting Incident

Date	Event	Description
August 15th, 2010 11:01:16 AM MDT	Block 74636 Is Mined	Bitcoin block 74,636 is mined, according to popular block explorers BlockStream, Blockchain.com and BtcScan.
August 15th, 2010 11:02:43 AM MDT	Block 74637 Is Mined	Bitcoin block 74,637 is mined, according to popular block explorers Blockchain.com and BtcScan.
August 15th, 2010 11:05:57 AM MDT	Value Overflow Incident	The original bitcoin block 74,638 is mined, according to the blockchain timestamp shared by Jeff Garzik. The value overflow incident occurred at this moment in time with this block being mined.
August 15th, 2010 11:10:33 AM MDT	Pre-Fork Block 74639 Mined	The pre-fork block 74,639 is mined. This adds to the pre-fork chain, which makes it longer. Anyone using the original bitcoin mining algorithm would pick this up as the valid chain.
August 15th, 2010 12:08:49 PM MDT	Jeff Garzik BitcoinTalk Post	Jeff Garzik posts on the BitcoinTalk forums to announce the strange block 74,638, which has a valueout field indicating "92233720368.54277039 BTC"
August 15th, 2010 12:55:34 PM MDT	BitcoinTalk User lfm	Within an hour, BitcoinTalk user lfm has identified the root cause and warns that readers "should probabl[y] shut down whatever you can and by no means make nor accept any transactions".
August 15th, 2010 1:04:11 PM MDT	New Thread By lfm	lfm has started a new thread to discuss the incident, the root cause, and his conclusion that "[w]e need a fix asap".
August 15th, 2010 2:39:42 PM MDT	Gavin Andresen Provides Fix	Gavin Andresen shares the source code for an interim fix, which appears to reject the transaction and continue to allow the bitcoin blockchain to operate starting from block 74,637.
August 15th, 2010 2:59:09 PM MDT	Satoshi Nakamoto Code Change	Satoshi Nakamoto posts an updated version of the bitcoin client CheckTransaction function, which includes checks that the values are positive, within range, and the total is also within range.
August 15th, 2010 3:06:45 PM MDT	It Would Help To Stop Generating	Satoshi Nakamoto asks the community to stop generating blocks. He's "pushing some other misc changes out of the way first, then I'll upload the patch for this".
August 15th, 2010 3:40:19 PM MDT	New Version Released To SVN	Satoshi Nakamoto announces that the new version has been committed to the official SVN repository for the bitcoin project. The recommendation is for the community to download a series of blocks from a user named knightmb.
August 15th, 2010 5:36:10 PM MDT	Satoshi Suggests Remining 7,000 Blocks	Satoshi suggests that clients should start at block 67,000 and remine the blockchain, validating the last 7,000 blocks again, before they start to mine new blocks. He describes this as "perfect".
August 15th, 2010 5:53:59 PM MDT	Replacement Block 74638 Mined	The timestamp of the replacement block 74,638 on popular block explorers Blockchain.com and BTCScan. This suggests that some bitcoin users had already implemented a fix and managed to mine a block at this point in time. As per the bitcoin protocol, this particular block would have been rejected by the main chain, as the forked chain was much shorter.
August 15th, 2010 5:55:55 PM MDT	Replacement Block 74639 Mined	The timestamp of the replacement block 74,639. Whoever has discovered and implemented the fix is profiting considerably, should this chain become the accepted one.
October 2nd, 2023 6:58:00 AM MDT	Crypto News Article Misinformed	An article published by Crypto News incorrectly states that "[b]itcoin experienced a value overflow incident at BTC block 74,638 mined on Aug. 15, 2010, at 7:53:59 a.m". This time appears to potentially represent when the new block was mined which fixed the incident, however in no part of the world was that August 15th at 7:53:59 AM. In Beijing China, it was August 16th, 2010 at 7:53:59 AM. The article speculates that Satoshi may have been the one responsible for implementing the fork, which is attributed to a tweet by Coinbase director Conor Grogan.

Technical Details

This section includes specific detailed technical analysis of any security breaches which happened. What specific software vulnerabilities contributed to the problem and how were they exploited?

Total Amount Lost

No funds were lost.

How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie?

Immediate Reactions

"The anomaly was quickly spotted on the Bitcoin Talk forum by Jeff Garzik, a Bitcoin developer who today is the CEO of Bloq. The issue was termed an “overflow bug”; the code for checking Bitcoin transactions didn't work if outputs were large enough that they overflowed when summed."

BitcoinTalk user lfm realized the seriousness and the root cause within an hour:

"The sum of the two outputs overflows to a negative. Its a bug in the transaction checks which did not reject it, then someone noticed and exploited it. Presumably a new version will be able to reject it and start a new valid fork. meanwhile should probablt shut down whatever you can and by no means make nor accept any transactions."

"The bug that caused the "value overflow incident" was corrected very quickly. It took just five hours before a “soft fork” was rolled out, which reset the Bitcoin blockchain to before the bugged block and included code to reject output value overflow transactions."

"The update, Bitcoin patch 0.3.10, was implemented by Bitcoin’s pseudonymous creator, Satoshi Nakamoto himself (or herself, or themselves)."

"The exploit and subsequent soft fork didn’t dent the price of Bitcoin. Indeed, Bitcoin actually experienced a surge over 2010; its price increased by over 300% between the day of the patch and the end of the year (from $0.07 to $0.30). That Satoshi himself intervened, and did so so quickly, showed that Bitcoin was not as easily hackable as some might have assumed and built confidence in a concept which up to that point remained untested."

Ultimate Outcome

Satoshi Nakamoto requesting the community to stop generating new blocks.

"It would help if people stop generating.  We will probably need to re-do a branch around the current one, and the less you generate the faster that will be. A first patch will be in SVN rev 132.  It's not uploaded yet.  I'm pushing some other misc changes out of the way first, then I'll upload the patch for this."

"A soft fork is a blockchain update. Since the Bitcoin community forked the state of the blockchain before the 184 billion Bitcoin was mined, that means that some blocks that were previously valid were turned into invalid blocks, removing them from the blockchain and restoring it to an earlier state."

"The fork erased all transactions and mining that had been recorded on blocks that were produced after the bugged block. It also disposed of the 184 billion bugged Bitcoin."

Total Amount Recovered

There do not appear to have been any funds recovered in this case.

Ongoing Developments

"The rapid implementation of the patch was vital in keeping Bitcoin a viable cryptocurrency. 184 billion Bitcoin would have devalued the currency completely, leaving it at the mercy of the person holding the newly-minted Bitcoin. Even if the breach happened today, the amount of bugged Bitcoin would completely dwarf the current supply of the cryptocurrency, making any Bitcoin worthless."

"Bitcoin also benefited from this exploit being patched close to its inception, since taking the Bitcoin network offline could be done without significant consequences."

"To this day, the person behind the exploit remains unknown, and due to the anonymous nature of the blockchain there is no way to trace them. Despite their anonymity, they are still a significant individual in the history of blockchain—quite possibly the first ever blockchain hacker."

Individual Prevention Policies

No specific policies for individual prevention have yet been identified in this case.

For the full list of how to protect your funds as an individual, check our Prevention Policies for Individuals guide.

Platform Prevention Policies

Policies for platforms to take to prevent this situation have not yet been selected in this case.

For the full list of how to protect your funds as a financial service, check our Prevention Policies for Platforms guide.

Regulatory Prevention Policies

No specific regulatory policies have yet been identified in this case.

For the full list of regulatory policies that can prevent loss, check our Prevention Policies for Regulators guide.