runtimeverification / runtimeverification/kontrol

Kontrol Cheatcodes library next steps

Open
#98 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement investigation
Dominant language
Python
Stars
122
Forks
16
PR merge metrics
No merged PRs in 30d

Description

Libray's ready here. We may want to do some of the following:

  • Make KontrolCheatcodes inherit Test, so that users only have to import one library
  • Make sure we have some CI to check that the current version of the Cheatcodes library doesn't break anything
  • At some point, replace kevm with kontrol to do kontrol.cheatcode() in favour of kevm.cheatcode()

We can open an issue for each bullet that makes sense and close this one.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the Kontrol Cheatcodes library in the linked repository. Separate the three proposals—inheritance, CI coverage, and replacing kevm with kontrol—into focused issues with their own scope and completion criteria; this umbrella issue is done when those follow-up issues exist and it can be closed.

Written by the indexing model from the issue text.

Assessment

Tech stack
solidity
Domain
blockchain, testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.