Bitcoin Value Overflow 184 Billion Minting Incident

Notice: This page is a freshly imported case study from the original repository. The original content was in a different format, and may not have relevant information for all sections. Please help restructure the content by moving information from the 'About' section to other sections, and add any missing information or sources you can find. 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.

This is a global/international case not involving a specific country.

About Bitcoin

"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."

"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."

"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."

"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. The update, Bitcoin patch 0.3.10, was implemented by Bitcoin’s pseudonymous creator, Satoshi Nakamoto himself (or herself, or themselves)."

"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."

"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."

"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."

This is a global/international case not involving a specific country.

The background of the exchange platform, service, or individuals involved, as it would have been seen or understood at the time of the events.

Include:

• Known history of when and how the service was started.
• What problems does the company or service claim to solve?
• What marketing materials were used by the firm or business?
• Audits performed, and excerpts that may have been included.
• Business registration documents shown (fake or legitimate).
• How were people recruited to participate?
• Public warnings and announcements prior to the event.

Don't Include:

• Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed.
• Anything that wasn't reasonably knowable at the time of the event.

There could be more than one section here. If the same platform is involved with multiple incidents, then it can be linked to a main article page.

The Reality

This sections is included if a case involved deception or information that was unknown at the time. Examples include:

• When the service was actually started (if different than the "official story").
• Who actually ran a service and their own personal history.
• How the service was structured behind the scenes. (For example, there was no "trading bot".)
• Details of what audits reported and how vulnerabilities were missed during auditing.

What Happened

The specific events of the loss and how it came about. What actually happened to cause the loss and some of the events leading up to it.

Key Event Timeline - Bitcoin Value Overflow 184 Billion Minting Incident

Date	Event	Description
August 15th, 2010	Value Overflow Exploit	Describe the event.

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

How did the various parties involved (firm, platform, management, and/or affected individual(s)) deal with the events? Were services shut down? Were announcements made? Were groups formed?

Ultimate Outcome

What was the end result? Was any investigation done? Were any individuals prosecuted? Was there a lawsuit? Was any tracing done?

Total Amount Recovered

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

What funds were recovered? What funds were reimbursed for those affected users?

Ongoing Developments

What parts of this case are still remaining to be concluded?

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.