runtimeverification / runtimeverification/evm-semantics
Bound env variables (`NUMBER`, `TIMESTAMP`) by reasonable values
Nobody has claimed this yet.
- Dominant language
- KCL
- Stars
- 591
- Forks
- 156
- Avg merge
- 2h 19m
- Merged PRs (30d)
- 1
Description
Currently, environmental variables such as block.number and block.timestamp are symbolic and are only bounded by the type range constraints. We can further restrict their values by adding some reasonable bounds, e.g., #rangeUInt(32, NUMBER) for block.number, which is ~3 orders of magnitude larger that current block number, as suggested by @ehildenb.
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 locating where the symbolic block.number and block.timestamp environment variables are defined and where #rangeUInt constraints are applied. Add the proposed reasonable bounds, then verify that the EVM semantics checks accept current values while constraining these variables beyond their type ranges.
Written by the indexing model from the issue text.
Assessment
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100