In a recent blog post, Donald McIntyre, a core member of the Ethereum Classic (ETC) community and a major contributor to the ongoing development and revamping of Ethereum Classic (ETC) network has recently published a blog post which summarised topics which were discussed by the platform’s developers at a recent “call”.
Discussing the Ethereum Classic (ETC) Network Hardfork
McIntyre’s revealed in his blog post that some section of the ETC ecosystem held a call with the main agenda being the to discuss a proposed hard fork (backwards incompatible upgrade), called Atlantis. The details of the hardfork have been outlined in Ethereum Classic Improvement Proposal (ECIP) 1054.
Main Topics Of Discussion at the Core Developers Meetup
According to McIntyre’s blog post, here are some of the key area of discussion covered at the meeting:
“Byzantium EVM precompiled contracts” including those involving “addition and scalar multiplication” for calculating certain ETC-related functions, and other calculation methods involving “modular exponentiation,”
“Spurious Dragon state-trie clearing,”
“Spurious Dragon contract-code size limit,”
Addition of several “Byzantium Ethereum Virtual Machine (EVM) opcodes,”
Changes to how ETC transaction receipts are processed,
Modifying ETC’s difficulty adjustment algorithm to “target mean block time”
A few main topics discussed during the call are as follows:
“ETC core developers have specified the six changes in the Atlantis hard fork” which is now open for discussion to the wider Ethereum Classic community.
Suggestions were made to “perform the hard fork on block 8,750,000” on ETC’s mainnet.
Zac Mitton, an ETC developer, recommended “analyzing the risk/reward ratio that state trie clearing (item 1 above) may represent as it does not affect ETH compatibility, and the benefits in reducing the state size seem to be marginal as compared to some risks when relating those changes to other ECIPs. There [also appears] to be some buggy code risk in the specification of that change.”
A large portion of ETC developers in attendance agreed to have “a quantifiable benefit of the state trie clearing, and to analyze it further.”
Zac Mitton also “offered to run a script to quantify the state size reduction in GB and get back with some results.”
The ETC developers are planning on following up on the “state trie clearing topic” in the “next few weeks to reach some consensus of whether to implement it or not.”
Cody Burns and other ETC developers on the call “agreed that if the state trie clearing were not included in Atlantis, that would have their support as well.”
