runtimeverification / runtimeverification/evm-semantics

Automatically detect and warn user on bad branches

Open
#1,752 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
KCL
Stars
591
Forks
156
Avg merge
2h 19m
Merged PRs (30d)
1

Description

Blocked on: #1753

Bad branches can happen in a variety of cases:

  • Branching on gas conditions.
  • Branching factor larger than 2 (all branches should be binary).
  • Branching on #Ceil conditions.
  • Branching on symbolic components of program.
  • Branching on the various checks when we do calls/creates (eg. "account exists? balance exists?, etc...")

Most of these cases are not actually "proper" branches, in the sense that they should not be present. So it would be good to not explore these branches further without confirmation from the user about which branch to take (or all of them).

Contributor guide

No contributing guide indexed for this repository

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 blocking issue #1753 and the branch cases listed here. The work is done when improper branches are detected, the user is warned, and exploration waits for confirmation about which branch or branches to follow.

Written by the indexing model from the issue text.

Assessment

Domain
blockchain
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.