runtimeverification / runtimeverification/kontrol
Move Solidity-specific files to Kontrol repo
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 122
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Several files in KEVM are really solidity specific, which means they belong in Kontrol, for example:
abi.mdhttps://github.com/runtimeverification/evm-semantics/blob/master/kevm-pyk/src/kevm_pyk/kproj/evm-semantics/abi.mdhashed-locations.mdhttps://github.com/runtimeverification/evm-semantics/blob/master/kevm-pyk/src/kevm_pyk/kproj/evm-semantics/hashed-locations.md
I suspect that these files aren't really needed in KEVM anymore, and so can be moved to Kontrol, and this would avoid issues where those files are updated, a bug is introduced, and not discovered until the merge into Kontrol (for example https://github.com/runtimeverification/evm-semantics/pull/2174).
Contributor guide
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 reviewing abi.md and hashed-locations.md in the linked KEVM path, then check whether they are still referenced by KEVM or needed by Kontrol. Compare the corresponding Kontrol usage and move the Solidity-specific files only when their dependencies are understood; done means they live in Kontrol and no longer create update or merge issues in KEVM.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- solidity
- Domain
- blockchain
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100