fix(fuzz): preserve stateless transactions#15814
Open
stevencartavia wants to merge 2 commits into
Open
Conversation
stevencartavia
requested review from
0xrusowsky,
DaniPopes,
figtracer,
grandizzy,
mablr and
mattsse
as code owners
July 18, 2026 05:52
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stateless fuzzing generates complete transactions but previously discarded everything except calldata. This meant values such as
msg.valuewere not preserved consistently across execution, corpus storage, counterexamples, and replay.This PR carries a complete
BasicTxDetailsthrough the stateless fuzzing path. It also keeps existing failure artifacts replayable.This is PR 1 because a shared transaction representation is the foundation for unifying stateless and invariant fuzzing around sequences. Follow-up PRs will unify transaction generation and dictionaries, sequence generation and mutation, and finally the execution campaign. Those architectural changes are intentionally out of scope here.
Part of OSS-252