header-langage
简体中文
繁體中文
English
Tiếng Việt
Scan to Download the APP
Partnered With:

Ethereum's pre-dawn bomb failed to detonate

Read this article in 5 Minutes
The darkest hour is that before the dawn. The dawn of ethereum may be coming.

Block beat BlockBeats 0x28


The darkest hour is that before the dawn. The dawn of ethereum may be coming.


On January 21, PeckShield released a message saying that ethereum's "Difficulty Bomb" had not exploded and had little effect on the block timing at this time. This effectively refutes the previous "ethereum difficulty bomb has exploded, will enter the ice age" mantra.


Two days ago at the eaeum developers' conference, the height of the hard-forked block in Constantinpole was reset to 7280000. According to this estimate, the hard bifurcating of Constantinople in ethereum will be delayed by more than a month from the original date, which is expected to be around February 27.


Expectations for ethereum's split were high, and enough eyeglasses were drawn. But the delays have caused a lot of grumbling among followers, and worse, the timing of the split, the decisive factor, is slowing down. Triggered another round of bad news for the market.


Plus, on January 15, Ethhub founder Eric Conner tweeted that ethereum's "difficulty bomb" had "exploded," as evidenced by the fact that ethereum's block time is increasing, "from 14 seconds to 15.5 seconds on average, and will continue to increase ethereum's block time."


As the news continued to grow with the warning, the ethereum difficulty bomb exploded and the sound of ethereum entering an ice age grew louder. PeckShield's statement at the time was more of a reassurance to ethereum's supporters.

"Difficulty bomb"Don't bang

In the early hours of January 16, it was revealed that ethereum had a "reentrant" bug in its code just before the scheduled fork in Constantinople. Since then, there seems to be a steady stream of bad news about ethereum.


According to PeckShield's research, the recent increase in average mining time, from 14 seconds to 15.5 seconds, had nothing to do with the eaeum difficulty bomb claimed by many media outlets to have exploded. The researchers say the difficulty bomb code already existed in October 2017, when the Byzantine hard bifurcated in ethereum. Therefore, the push back of Constantinople did not result in a new difficulty bomb.


In fact, difficulty bombs are not as easy to activate as you might think. First, the difficulty value generated by the "difficulty bomb" algorithm is part of the ethereum block difficulty value, along with related factors such as the block difficulty and time of the previous block.


Even if all of these elements are met, the difficulty value generated by the current difficulty bomb accounts for less than one part in 10,000 of the total difficulty and has little or no effect on the block time. In other words, it's very difficult to actually cause a bomb to go off on a difficulty that actually affects the safety of the piece.


But a very low probability doesn't mean it's impossible. Ethereum's rule is that the difficulty of ethereum blocks doubles for every 100,000 blocks that are added. In this case, if the block difficulty is not adjusted, the block difficulty becomes higher and higher, which gradually becomes the determinant of ethereum's block time.


In the worst case scenario, the ethereum ice age arrives as the ethereum block lasts indefinitely, making it less attractive to miners. PeckShield revealed that the Constantinople hard fork, which was delayed until February 27, would reduce the difficulty by 2 to the 20th power, or about a millionth of the present value, delaying the "difficulty bomb" by a year.

w1.2210.jpg      

As of press time, ethereum's browser showed a block-out speed of 17 seconds, compared with 14 seconds on Monday morning. BlockBeats found that before entering the predetermined bifurcation period, the block exit speed would also float, so this situation is more like the normal float of calculation force.


Miners still stand to lose most from fixing the leak


PeckShield revealed a hard bifurcation "reentrant" vulnerability in ethereum, disrupting the bifurcation plan. A "reentrant" vulnerability can attack the relevant contracts, and user balances or other key variables can be modified. The first storage operation before the fork requires at least 5000gas, which becomes 2300gas. Therefore, this loophole directly caused the delay of Constantinople in ethereum.


The ethereum developer conference opens on January 18. The meeting focused on updating difficulty bombs, when to reintroduce hard bifurcations, road maps after Constantinople, and "reentry" vulnerabilities that delayed upgrades.


In light of the bug, the developers decided to remove the SSTORE net gas measurement ethereum improvement proposal (EIP) from the upgrade and instead place it in ethereum's "Istanbul" fork in October.


In other words, the main contents of Constantinople's upgrade plan were: 5 eips (Ethereum Improvement Proposal). Except for EIP1283, EIP145, EIP1014, EIP1052 and EIP1234 are still continuing in the bifurcations as originally planned.


As a result, block rewards were reduced from 3 ETH to 2 ETH unchanged, difficulty bombs were deferred for 12 months, and other minor protocol improvements were made.


Notably, EIP1234 corresponds to block rewards, which are miners' interests. Ethereum has been continuously reducing the benefits of miners, which has also become the resistance of ethereum system upgrade.


Now, by reducing the existing block rewards from 3 ETH to 2 ETH, the miner rewards are reduced by more than 33%. Based on the current average ETH price of $790, miners will receive $790 less for each ethereum they dig out. In the current market, the severity of the situation can be imagined.



Welcome to join the official BlockBeats community:

Telegram Subscription Group: https://t.me/theblockbeats

Telegram Discussion Group: https://t.me/BlockBeats_App

Official Twitter Account: https://twitter.com/BlockBeatsAsia

Choose Library
Add Library
Cancel
Finish
Add Library
Visible to myself only
Public
Save
Correction/Report
Submit