|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Cryptocurrency News Video
[Bitcoin Ecology] The 600 microseconds that almost caused the Bitcoin system to collapse
Apr 27, 2024 at 06:18 am 发哥web3区块链投资
Bitcoin’s fourth halving has been completed. This decentralized system has been running successfully for 15 years. However, the Bitcoin core client vulnerability disclosed in 2018 directly threatened the stability of the Bitcoin system and can be called Bitcoin’s biggest One of the vulnerabilities, today I would like to introduce to you the client double-spend vulnerability disclosed on September 20, 2018, CVE-2018-17144.
What is Bitcoin Core?
Bitcoin Core was initiated by Satoshi Nakamoto and is considered the "orthodox" Bitcoin client and is currently the most used. This software can verify all transactions that have been made on the blockchain and can transfer funds. .
What is CVE-2018-17144?
In versions 0.14 - 0.16.2 released by Bitcoin Core, there is an extremely serious vulnerability that will cause program crashes and double-spend problems. That is to say, the input contained in a one-to-one transaction can be output multiple times, which will cause unlimited issuance. It destroyed the consensus that the total number of Bitcoins is 21 million, causing inflation, and was later included in the public vulnerability list as CVE-2018-17144.
Why is there this vulnerability?
This dates back to 2016. Yes, although it was a vulnerability discovered in 2018, the foreshadowing was already laid in 2016. In 2016, a developer proposed a merger to Bitcoin Core.
Hopefully removing the duplicate input check in the transaction check will save about 600 microseconds, and then the reviewer passes this merge, at which point the bomb is planted.
In the version 0.14. The node's broadcast is discarded, and triggering this attack requires the attacker to discover a block. This cost is very high and can only cause some clients to crash, without bringing any benefits to the attacker.
Until version 0.15, released in September 2017, developers optimized the structure of the UTXO database, accidentally allowing the client to continue operations despite repeated inputs. This vulnerability opened up the possibility of double spending.
How was the vulnerability discovered?
After the release of version 0.15, no one discovered this vulnerability for a year until September 17, 2018, until BCH developer Awemany found this vulnerability in the BCH code base while sitting in a minivan on the beach at noon. Comment
Check for duplicate inputs — note that this check is slow so we skip it in CheckBlock
awemany felt something was wrong, and used the regtest mode to test repeatedly entered things, and the results directly prompted
Wham! assert(), Aborted.
He recognized the danger that this could be exploited to cause inflation and split the chain, writing
BitcoinABC does not check for duplicate inputs when processing a block, only when inserting a transaction into the mempool.
This is dangerous as blocks can be generated with duplicate transactions and then sent through e.g. compact block missing transactions and avoid hitting the mempool, creating money out of thin air.
/u/awemany
He then immediately reported the vulnerability and the fix patch to Bitcoin Core and Bitcoin ABC (BCH development team).
He wrote in his review that he was relieved after the submission, which revealed a multi-million dollar vulnerability that could have huge consequences for a currency worth $100 billion (now $1.2 trillion). The impact is that, in fact, he could rent computing power to short BTC, which would make him directly rich, but he didn't. He chose to report the vulnerability.
At 21:58 that day, Bitcoin ABC released a patch to fix the vulnerability, and sent this message to the majority of nodes to urge them to upgrade. After most nodes completed the upgrade, the vulnerability was fully disclosed.
However, not only Bitcoin and BCH but also various altcoins that forked Bitcoin Core were affected by this vulnerability. Since this vulnerability was merged by the Bitcoin Core team, everyone blamed the Bitcoin Core team.
Because of the change of 600 microseconds, the double-spend vulnerability has been lurking on the chain for a year. If this vulnerability is exploited, it may lead to a hard fork, and the price of Bitcoin will still be as high as it is now. ? Will another ETC be born like the hard fork of Ethereum?
Disclaimer:info@kdj.com
The information provided is not trading advice. kdj.com does not assume any responsibility for any investments made based on the information provided in this article. Cryptocurrencies are highly volatile and it is highly recommended that you invest with caution after thorough research!
If you believe that the content used on this website infringes your copyright, please contact us immediately (info@kdj.com) and we will delete it promptly.
-
-
-
- The market sentiment is still panic, will it continue to fall? #BTC#ETH#ETC#LTC#BCH#MANA#ZEC#ZEN#LPT#XLM#SOL#BAT#LINK#FIL#ADA#shib
- Apr 27, 2024 at 06:18 am 比特币城管希
- The content of the video is for reference only and does not constitute investment advice. Harmonic form#Volume and price analysis#Indicator technology...
-
-
- All - the system of leading the gods at the beginning of school, all the rich and beautiful girls are wanted, the whole process is hilarious and slaps in the face! #campus#shuangdrama
- Apr 27, 2024 at 06:18 am 小小看劇
- So many themes, super sweet plot ~ counterattack - slap in the face - system - revenge, cool articles are all available - English subtitles are update...
-
-
- How much do you know about the capital story behind Malaysia’s favorite fried chicken? An in-depth chat with MarryBrown, KFC
- Apr 27, 2024 at 06:18 am ZFounderclub
- Many people only look at KFC at its superficial appearance: there are stores all over the street, and there are people queuing up for fried chicken ev...
-
-
























