Snapshot fuzzing
- Dominant language
- Haskell
- Stars
- 3.2k
- Forks
- 432
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 5
Description
- [ ] Maintain a corpus of interesting EVM state snapshots and singleton transactions, rather than storing only complete transaction sequences.
- [ ] Compress, deduplicate and garbage-collect snapshots, and reconstruct and shrink an executable transaction sequence for every reported failure.
Optional:
- [ ] Investigate storage-data-flow, comparison, state-novelty and property-progress waypoints.
References:
* https://github.com/fuzzland/ityfuzz
Contributor guide
Research direction
No files, tests, or entry points are named. Start by reading the snapshot-fuzzing requirements and the linked ityfuzz project, then define how EVM state snapshots and singleton transactions will be stored, compressed, deduplicated, garbage-collected, and used to reconstruct and shrink executable failure sequences.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell, solidity
- Domain
- security, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100