Skip to content

Instantly share code, notes, and snippets.

@meowsbits

meowsbits/ETC-re-ECIP1088-Phoenix.md Secret

Last active February 24, 2020 13:53
Show Gist options
  • Save meowsbits/d19911027454027a5409fe0deac2154f to your computer and use it in GitHub Desktop.
Save meowsbits/d19911027454027a5409fe0deac2154f to your computer and use it in GitHub Desktop.
Download ZIP
Raw
ETC-re-ECIP1088-Phoenix.md

ETC Aztlan+PhoenixFix Rejection, and a Replacement Proposal

With a bedrock goal of maintaining and building for stability and security on the ETC network, it is the opinion of ETC Labs (with advisement of development groups ETC Core and Chainsafe), 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 "Aztlan + 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 ETH network, two ECIPs (1088, 1089) have been drafted for the subsequent consideration of the community, which intend to summarize and simplify next potential paths forward.

  1. ECIP1088: Phoenix EVM Upgrade (Vanilla Option) proposes a fork specification equivalent to the Ethereum Foundation's Istanbul fork1.
  2. ECIP1089: Phoenix EVM Upgrade (Classic Option) proposes a unified version of the rejected Aztlan + PhoenixFix specification(s)2.

A community meeting has been scheduled for Wednesday, April 26, 13:00 UTC, to review these concerns and discuss forward steps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment