Connect with us

Ethereum

Ethereum [ETH] Constantinople hard fork deferred; DoS attack vector blamed

Anvita M V

Published

on

Ethereum [ETH] Constantinople hard fork deferred; DoS attack vector blamed
Source: Unsplash

On October 5th, the core developer of Ethereum, Péter Szilágyi announced that the plan to launch the upcoming hard fork, Constantinople on the Ropsten Testnet has been delayed.

Péter Szilágyi explained that the decision comes collectively from the Ethereum community. The core developer stated that the main reason behind the delay was an encountered Ethereum Virtual machine [EVM] Denial of Service [DoS] attack vector. Szilágyi stated that the delay will allow clients to implement, test and release an update on the CREATE2 Ethereum Improvement Protocol [EIP], to counter the DoS attack vector.

Earlier, on 15th September, another member of the Ethereum community, Eric Conner announced that the Constantinople hard fork will hit the Ropsten Testnet on October 9th. Conner also stated that once the hard fork hits the Testnet, it will be implemented on the main chain soon after the Ethereum Devcon 4 event, held from 30th October to November 2nd.

According to Szilágyi’s recent tweet, the Testnet launch has been pushed by 1 epoch to block  #4230000, resulting in a delay of 5 days. The developers, however, have not commented on whether the delay in launching Constantinople on the Ropsten Testnet will push the dates for the main launch of the Ethereum hard fork.

The Constantinople hard fork was first announced in July this year, during a developer and stakeholder meeting that addressed the issues in the blockchain and cryptocurrency space with a focus on further upgrades.

The development team stated that the hard fork was being created to signal a new era of blockchain network usage. The community also claimed that Constantinople will see a cost-effective Mainnet and will be more efficient to use.

Cryptohulk, a Twitterati and cryptocurrency enthusiast said:

“Delay means problems $ETH

Responding to the Twitterati’s comment, the core developer Szilágyi assured that they were taking time because they did not want to “break the Testnet.”



Afri Schoedon, another Twitterati and blockchain minimalist commented:

“Perfect. 4230000 was my favourite block choice anyways.”

The Constantinople will be the second in the series of upgrades, the first being the Byzantine hard fork that took off in October last year. It went live at block #4,370000 and includes nine Ethereum Improvement Protocols.





Subscribe to AMBCrypto’s Newsletter




Follow us on Telegram | Twitter | Facebook



Anvita Mysore Vadiraj is a full-time content writer at AMBCrypto. Her passion lies in writing and delivering apt information to users. Currently, she does not hold any form of cryptocurrencies.

Ethereum

Ethereum [ETH]: ProgPow audit may not be completed before Istanbul

Priya

Published

on

By

Ethereum [ETH]: ProgPow audit may not be completed before Istanbul
Source: Unsplash

Programmatic Proof-of-Work [ProgPow] has undoubtedly been one of the most controversial upgrades of Ethereum. The algorithm that promises to ward off ASIC mining would probably not make it till after the Istanbul hardfork. A blog post titled ‘ProgPow Audit Delay Issue’ published by Hudson Jameson, a member of EF, stated that they encountered problems with ProgPow audit.

Hudson Jameson explained the situation,

“We had a hardware partner who specialized in ASICs who was going to work with Least Authority to perform the hardware parts of the audit. They are no longer participating in the audit so we are looking for other auditors for the hardware portion.”

Further, Jameson stated that there were “some good candidates” to fill in the position, however, it would “effectively delay” the start of the audit even further than what they had anticipated. This was the sole reason the team was uncertain whether the audit would be ready before the Istanbul hardfork.

Along with this, the member also spoke about the funding pertaining to ProgPow miner, where he remarked,

“On top of that I am not sure if anyone has sorted the funding situation in order to build an open source ProgPoW miner.”

Due to these problems, Hudson presented two options, first, delay “ProgPoW until the hardfork after Istanbul”, and second, let ProgPow have its own hardfork once the audit was completed. Hudson further stated that “this was not an ideal situation at all, but despite our best efforts, it is what we have before us”.



McDogger, a Redditor said,

“I personally would prefer a third option (stop with the audits, drop progpow and spend time/ money on Eth 1.x finality) but if I had to chose than it’s certainly option 1. Progpow […] doesn’t deserve it’s own – contentious, because it’s just one change and not many other improvements – hardfork.”

The initial announcement was made on Ethereum Cat Herders Update #9, where Pooja Ranjan, a EF member, stated that “logistical issues” were the reason for the delay of ProgPow audit, adding that the timeline for the start and end of the audit were not even decided yet.





Subscribe to AMBCrypto’s Newsletter


Continue Reading

Trending