The Ethereum Trouble bomb is delayed until mid-September – The Defiant

There are Ethereum developers Delayed The so-called “solid bomb” of the network, in about 100 days, set a rough estimate in September for its long-awaited proof-of-stack transfer.

Ethereum currently uses a power-intensive proof-of-work (PoW) process to verify transactions. The disadvantage is an update built into the bomb protocol that will significantly increase the complexity of the PoW calculation, and therefore, the time required to process the transaction – a kind of self-destruction process that encourages conversion to an environmentally-friendly proof-of-use. -Steak (PoS) model.

That transformation, known as consolidation, has been repeatedly delayed. The difficulty is that suspending the bomb within 100 days – a decision the developers made last month – is a recognition that Merge will have to wait a little longer.

Delay debate

The main developers of Etherium debated at the June 10 meeting the merits of delaying the trouble bomb. At that point, according to EtherScan data, the time required to complete a block has already begun to increase, increasing from about 13 seconds to more than 16 seconds.

Thomas J. Rush, one of the participants in the call, said allowing the trouble bomb to explode according to the original plan in June “certainly has very bad results if you have a 20 or 30-second block by August.”

Still, it was his recommended move, he said.

“I think it’s like hitting the community on the head with a stick,” he said. “The community needs to pay attention to the fact that the original Davis has the power to make this decision. We can use it to say, ‘You have to make the community more involved in this kind of decision.'”

Another participant, Andrew Ashikhmin, called it a “stupid political game.”

‘Responsible Things’

Delaying the bomb “actually sends a good signal – that we’re doing a responsible job, we don’t want to rush into a code that’s not ready,” he said. “Doing nothing would actually be irresponsible because it would damage network throughput.”

If the developers are in favor of the delay, Rush said, they should announce a tough deadline for them to come together, he said. But it also faced opposition from other developers, including Tim Beiko, who led the meeting.

“If we delay the bomb by two months, four months, six months, whatever,” he said, “there are some articles that say it has been delayed until the end of the year. I don’t care.”

Lack of emergency

Developer Ben Easington has spoken of defending a tough timeline, saying there was a lack of urgency to complete the merger.

“There are very real costs involved in not consolidating: 130,000 tons of carbon dioxide per day,” he said. “It’s about a million tons a week. Every week we twist our thumb, it’s one megaton of carbon dioxide that we’re emitting. ”

Beiko objected to the notion that developers do not feel pressured to complete the merger.

“It simply came to our notice then [that] In the last call, and to me personally, client teams mentioned that they were feeling quite stressed and urgent, “he said.” Excessive pressure pushes teams to burn out or make bad decisions, and we don’t want to be in that situation. “

https://ift.tt/bAuSRv2

Baca juga

• Upcoming Drops: October 24-30
• Abbott and Costello have immortalized their legacy as NFTs
• Telegram gears up to launch its on-board Web3 marketplace