The Ethereum community has been anticipating several developments in its ecosystem including its transition to Ethereum 2.0 as well as the Istanbul hard fork. Recently, Vitalik Buterin, the co-founder of Ethereum pointed out the latest change in Sharding protocol. Along with which, Tim Beiko, the Product Manager at PegaSys Protocol Engineering revealed an update pertaining to the Istanbul hard fork. Beiko took to Twitter and elaborated on the same in an array of tweets which read,
“There is some back and forth, but it seems like there is rough consensus on having Dec 4th be the hardfork date, and using Jan 8th as a backstop date in case anything goes wrong (*cough* Petersburg! *cough*)!
So Istanbul is coming early December !”
Furthermore, Beiko pointed out that the network’s development would be centered on rolling out the EIP-2124 which is a fork identifier. The EIP-2124 checks chain compatibility and is also an alternative for discovery protocol. Additionally, Beiko revealed that the development was,
“@peter_szilagyi‘s idea of having clients talk to each other based on their entire fork history rather than just their genesis block.”
However, the risk of losing an easy identifier for the network would still survive considering the synchronous hashing of all the fork blocks. Beiko further said,
“A proposal would be to have both the genesis and EIP-2124 handshakes running in parallel to start, and then if we realize that that genesis blocks aren’t useful, we can drop them eventually.”
Ethereum Classic’s Agharta proposal moves closer to finalization
Ethereum Classic’s successful execution of Atlantis hard fork, led the way to Agharta, the second half of the Atlantis hard fork. Atlantis contributed to enhancing ETH compatibility; however, Agharta will host aspects of Constantinople protocol to make it fully compatible with Ethereum. ETC announced that the core developers will sit down to discuss the ECIP-1056 Agharta Finalization.
The agenda of the meeting has been divided into three parts- Quick client teams check-in, Agharta [ECIP-1056] is in “last call” state, and discussing the timeline for the protocol upgrade. The finalization will reveal the status of ECIP 1056, which still awaits acceptance and will also provide the block number for mainnet. The tweet read:
“The focus of the #Agharta (ECIP-1054) core development call will be to:
• Evaluate network testing
• Discuss upgrade timeline
• Agree on mainnet block number
• Move ECIP to “Accepted””
The Modern testnet has been scheduled for 13 November at block number 5_000_381, and it will be followed by the Mordor testnet on 20 November at block 5_000_381. The Kotti testnet has been scheduled for 11 December at block number 1_705_549, following which on 12 December the team will decide the block number for mainnet.
According to a blog post shared by the core of ETC, Agharta would consist of EIP 145-Bitwise Shifting Instruction, EIP 1014- Skinny Create2 opcode, and the final feature EIP 1052- EXTCODEHASH opcode. The rationale behind enabling the Constantinople and Petersburg network protocol was to upgrade the ETC network and to obtain maximum compatibility across these networks. The hard-fork has received support from Multi-Geth, Parity, and Geth Classic client teams and will go live on 15 January 2020.