runtimeverification / runtimeverification/evm-semantics
Figure out how many special cases in semantics are actually needed for previous hard forks
Nobody has claimed this yet.
- Dominant language
- KCL
- Stars
- 591
- Forks
- 156
- Avg merge
- 2h 19m
- Merged PRs (30d)
- 1
Description
This can be done by syncing Mantis on the main-chain using KEVM as a backend, and disabling the various rules which depend on previous hard forks.
Similarly, we may be able to find alternate (simpler) descriptions of the EVM which still conform to the existing blockchain by changing KEVM and trying to sync.
One concrete example is the dependence on FRONTIER, https://github.com/kframework/evm-semantics/blob/master/evm.md#account-creationdeletion during account creation.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading evm.md at the account creation/deletion section and reviewing how Mantis is synced on the main chain with KEVM as its backend. Disable or simplify one prior-hard-fork-dependent rule, then check whether synchronization still conforms to the existing blockchain. Done means the required special cases and any valid simpler EVM descriptions are identified and documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- blockchain, compilers
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100