Value overflow incident: Difference between revisions
No edit summary |
Fix transaction template (there is no such thing as a from address) |
||
| Line 1: | Line 1: | ||
{{Transaction | {{Transaction | ||
|hash=1d5e512a9723cbef373b970eb52f1e9598ad67e7408077a82fdac194b65333c9 | |hash=1d5e512a9723cbef373b970eb52f1e9598ad67e7408077a82fdac194b65333c9 | ||
|in1= | |in1=237fe8348fc77ace11049931058abb034c99698c7fe99b1cc022b1365a705d39-000 | ||
|val1=0.5 | |val1=0.5 | ||
|out1=1Hk51V49a58fC2r471hScXopEQpioDEuqx | |out1=1Hk51V49a58fC2r471hScXopEQpioDEuqx | ||
Revision as of 03:04, 23 September 2014
|
237fe8348fc77ace11049931058abb034c99698c7fe99b1cc022b1365a705d39-000 0.5 BTC |  |
92,233,720,368.54275808 BTC 1Hk51V49a58fC2r471hScXopEQpioDEuqx 92,233,720,368.54275808 BTC 12vRJXnnA21YAaLacWXpNshy7MBAwrigtQ 0.51 BTC Miner's fee |
On August 15 2010, it was discovered that block 74638 contained a transaction that created 184,467,440,737.09551616 bitcoins for three different addresses.[1] Two addresses got 92.2 billion bitcoins, and whoever solved the block got an extra 0.01 BTC that did not exist prior to the transaction. This was possible because the code used for checking transactions before including them in a block didn't account for the case of outputs so large that they overflowed when summed.[2] A new version of the client was published within five hours of the discovery. The block chain had to be forked. Although many unpatched nodes continued to build on the "bad" block chain, the "good" block chain overtook it at a block height of 74691. The bad transaction no longer exists for people using the longest chain. Therefore, the bitcoins created by it do not exist either. While the transaction does not exist anymore, the 0.5 BTC that was used in it does. It appears to have come from a faucet and has not been spent since.