Ten years ago, the code killed 184467 million bitcoins!
Recently, the two biggest things in the blockchain field are the Ethernet Constantinople hard fork and the private coin grin project. As a media focusing on blockchain technology, the battalion commander naturally pays more attention to the former. This time, the untimely Ethereum is untimely again. But the battalion commander doesn't think we need to pay too much attention to it.
On January 20, just after the Constantinople hard fork was postponed again, Afri schoedon, a core development member of Ethereum, said that the overall progress of Ethereum 2.0 related projects such as serenity, proof of rights and interests (POS) and sharding had nothing to do with the upgrade of Ethereum 1.0's on chain protocol. The delay of Constantinople's hard fork will not affect Ethereum 2.0.
Later, God V tweeted and commented that Constantinople's rigid bifurcations would not affect the stable and sustainable development of Casper / sharding / Serenity at all.
When it comes to bifurcations, the battalion commander went to check the bifurcations of bitcoin and Ethereum. The Dao event of Ethereum is more famous. The direct result is that the two heroes of Eth and etc compete for hegemony (a little exaggeration, in fact, etc is not good enough, and it's hard to protect themselves). However, compared with the bifurcations event that the battalion commander will say next, the Dao is really trivial. Great.
This is the "value spillover event" that almost destroys bitcoin and kills decentralized belief.
On August 25, 2010, an unknown hacker nearly destroyed bitcoin. The hacker generated 184467 million bitcoins (what? It's just 21 million. Nakamoto realized the seriousness of the matter, and soon split the bitcoin blockchain, erasing 184467 million bitcoins, which was the only way to save bitcoin at that time.
So how did it happen? And back to the code. In essence, when running code, if the output is too large to overflow when summing, the code that checks the bitcoin transaction will be invalid. Hackers realize this and take advantage of it. Hackers created 8784 times more bitcoin in a single transaction than ever before.
If Nakamoto didn't correct the mistake in time, bitcoin would probably have died and the whole blockchain world would not exist. Because once users realize that they can create any number of bitcoin at will, the price of bitcoin will immediately drop to zero, bitcoin will lose trust, and Nakamoto's decentralized vision will be impossible to talk about.
Within three hours of the incident, Nakamoto posted on bitcointalk that he and Gavin Andresen, an early bitcoin developer, had quickly created a code repair program.
Within five hours after the incident, Nakamoto released bitcoin version 0.3.10, which prevented the bug of generating bitcoin through overflow vulnerability and erased 184467 million bitcoins generated by hackers.
This is a hard fork, so there will still be two different versions of bitcoin within hours of the 0.3.10 release. Nakamoto closely monitors the other chain and urges miners not to mine the bad blockchain, because it will take longer to make the new chain the main chain.
Finally, 19 hours after the incident, the new blockchain surpassed the original chain in the 74691 high block and became the main bitcoin chain. Since then, the bitcoin blockchain generated by version 0.3.10 has become the one we use today.
I have to say that it's amazing to cry for ghosts and gods. It's not too much to say that it's the biggest hacker incident in history.
Then, similar to the remedy of the Dao event, this event also made a fast hard fork. Is this against the decentralized vision? Is it imperative? What do you think of this? Please leave a message at the end to tell the battalion commander.
On January 20, just after the Constantinople hard fork was postponed again, Afri schoedon, a core development member of Ethereum, said that the overall progress of Ethereum 2.0 related projects such as serenity, proof of rights and interests (POS) and sharding had nothing to do with the upgrade of Ethereum 1.0's on chain protocol. The delay of Constantinople's hard fork will not affect Ethereum 2.0.
Later, God V tweeted and commented that Constantinople's rigid bifurcations would not affect the stable and sustainable development of Casper / sharding / Serenity at all.
When it comes to bifurcations, the battalion commander went to check the bifurcations of bitcoin and Ethereum. The Dao event of Ethereum is more famous. The direct result is that the two heroes of Eth and etc compete for hegemony (a little exaggeration, in fact, etc is not good enough, and it's hard to protect themselves). However, compared with the bifurcations event that the battalion commander will say next, the Dao is really trivial. Great.
This is the "value spillover event" that almost destroys bitcoin and kills decentralized belief.
How serious is it?
On August 25, 2010, an unknown hacker nearly destroyed bitcoin. The hacker generated 184467 million bitcoins (what? It's just 21 million. Nakamoto realized the seriousness of the matter, and soon split the bitcoin blockchain, erasing 184467 million bitcoins, which was the only way to save bitcoin at that time.
So how did it happen? And back to the code. In essence, when running code, if the output is too large to overflow when summing, the code that checks the bitcoin transaction will be invalid. Hackers realize this and take advantage of it. Hackers created 8784 times more bitcoin in a single transaction than ever before.
If Nakamoto didn't correct the mistake in time, bitcoin would probably have died and the whole blockchain world would not exist. Because once users realize that they can create any number of bitcoin at will, the price of bitcoin will immediately drop to zero, bitcoin will lose trust, and Nakamoto's decentralized vision will be impossible to talk about.
What did Nakamoto do?
Within three hours of the incident, Nakamoto posted on bitcointalk that he and Gavin Andresen, an early bitcoin developer, had quickly created a code repair program.
Within five hours after the incident, Nakamoto released bitcoin version 0.3.10, which prevented the bug of generating bitcoin through overflow vulnerability and erased 184467 million bitcoins generated by hackers.
This is a hard fork, so there will still be two different versions of bitcoin within hours of the 0.3.10 release. Nakamoto closely monitors the other chain and urges miners not to mine the bad blockchain, because it will take longer to make the new chain the main chain.
Finally, 19 hours after the incident, the new blockchain surpassed the original chain in the 74691 high block and became the main bitcoin chain. Since then, the bitcoin blockchain generated by version 0.3.10 has become the one we use today.
I have to say that it's amazing to cry for ghosts and gods. It's not too much to say that it's the biggest hacker incident in history.
Then, similar to the remedy of the Dao event, this event also made a fast hard fork. Is this against the decentralized vision? Is it imperative? What do you think of this? Please leave a message at the end to tell the battalion commander.
评论
发表评论