With a bedrock goal of maintaining and building for stability and security on the Ethereum Classic network (ETC), it is the opinion of ETC Labs - with advisement of development groups ETC Core, ChainSafe, and Byzantine Fault -, that given lessons learned and flags raised during the testing and evaluation phase of this proposed fork, it is in the interest of the network and its investors to officially reject the current specification for the network's next planned hardfork bundle of ECIP-1061 "Aztlan" and ECIP-1078 "PhoenixFix" on the basis of red-flag security concerns both known and potential.
These concerns arise from implementation complexity, gray areas, and unforeseens in technical specifications, and a desire to manage and minimize the overall risk exposure of the network.
In order to resolve these concerns and avoid significant delay to the network's original intention of achieving interoperational parity with the Ethereum Foundation network (ETH), the two ECIPs 1088 and 1089 have been drafted for the subsequent consideration of the community, which intend to summarize and simplify next potential paths forward.
- ECIP-1088: Phoenix EVM Upgrade (Vanilla Option) proposes a fork specification equivalent to the Ethereum Foundation's Istanbul fork1.
- ECIP-1089: Phoenix EVM Upgrade (Classic Option) proposes a unified version of the rejected Aztlan + PhoenixFix specifications2.
A community meeting has been scheduled for Wednesday, April 26, 13:00 UTC, to review these concerns and discuss forward steps.
- 1: Istanbul specs: https://eips.ethereum.org/EIPS/eip-1679
- 2: Aztlan + PhoenixFix specs, patches, and related content: https://ecips.ethereumclassic.org/ECIPs/ecip-1061, https://ecips.ethereumclassic.org/ECIPs/ecip-1072, https://ecips.ethereumclassic.org/ECIPs/ecip-1078, https://ecips.ethereumclassic.org/ECIPs/ecip-1086, https://ecips.ethereumclassic.org/ECIPs/ecip-1080, ethereumclassic/ECIPs#295