Hard Forking Capability for EOS EVM

[stephenpdeos]

Hard Forking Capability for EOS EVM

Problem

Opportunity: What are the needs of our target user groups?

The EOS EVM lacks a robust mechanism for implementing hard forks, which are essential for introducing significant updates, protocol improvements, and possibly addressing critical vulnerabilities. This capability is crucial for the platform's adaptability, security, and evolution, meeting the needs of developers and users for a dynamic, up-to-date, and secure blockchain environment.

Strategic alignment: How does this problem align with our core strategic pillars?

Introducing hard forking capability aligns with our strategic pillars of "Relevance and Compatibility" and "Security and Trust". It ensures the EOS EVM can evolve in response to technological advancements and community needs while maintaining a secure and reliable platform.

Context

Competitors: Who are our top competitors and why? How do they solve this problem today?

Competitors like Ethereum have established mechanisms for hard forking, allowing them to introduce significant updates such as EIP-1559 and transition towards Ethereum 2.0.

Product differentiation: What would make our solution different?

The EOS EVM's approach to hard forking would has been designed to minimize disruption and ensure a seamless transition.

Solution

Solution name: Hard Forking Capability for EOS EVM

Purpose: Define the product’s purpose briefly

To establish a comprehensive framework within EOS EVM that allows for the smooth execution of hard forks, enabling the platform to introduce significant updates, enhance functionality, and address vulnerabilities effectively.

Success definition: What are the top metrics for the product to define success?

1. Successful implementation of a test hard fork demonstrating the framework's effectiveness.
2. Seamless execution of hard forks with minimal disruption to the EOS EVM ecosystem.

Assumptions

• The reused fields utilized in the current design will not be utilized by future Ethereum updates

Risks: What risks should be considered?

• TBD

Business Objectives/Functionality

1. Implement technical tools and protocols within EOS EVM to support hard forking, ensuring minimal disruption and maximum security.

User stories

• As a user, I want assurance that the platform can evolve and improve over time through hard forks without compromising my assets' security or usability.

Open questions

• TBD

Tasks

Preview Give feedback

1. Design spike: proposal general hard fork solution compatible with silkworm eos-evm-contract#626
   👍 lgtm +1
   
2. Support for upgrading EOS EVM version and emit evmtx action for each EVM transaction eos-evm-contract#671
   👍 lgtm +1
   
3. Listen to evmtx actions and ensure EVM block header nonce captures EOS EVM version eos-evm-node#97
   👍 lgtm +1
   
4. Ensure EVM block header nonce captures EOS EVM version eos-evm-node#98
   👍 lgtm +1
5. Upgrade EOS EVM version eos-evm-contract#672
   👍 lgtm +1
6. Use nonce as EOSEVM version and map to EVMC revision silkworm#82
   👍 lgtm +1
   
7. Use nonce as EOSEVM version and map to EVMC revision eos-evm-node#96
   👍 lgtm +1
   
8. Map EOS EVM version to EVMC revision eos-evm-contract#673
   👍 lgtm +1
   
9. Document EOS EVM version conventions for node operations eos-evm-node#133
   +0
   

Possible future tasks

• Develop educational materials for the community on the hard fork process and status.

[stephenpdeos]

Reopening until released alongside Gas Fee Algorithm