refactor(traces): unify decoder hardfork state - #16417
Open
stevencartavia wants to merge 2 commits into
Open
Conversation
stevencartavia
requested review from
0xrusowsky,
DaniPopes,
figtracer,
grandizzy,
mablr and
mattsse
as code owners
August 27, 2026 20:31
Contributor
✅ Changelog foundThe deterministic check will validate the changed entry. |
figtracer
approved these changes
Aug 29, 2026
figtracer
enabled auto-merge (squash)
August 29, 2026 14:04
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
3 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.
CallTraceDecodercurrently stores network-specific hardforks separately even though execution resolves a singleFoundryHardfork. This requires callers to decompose that value when configuring and updating the decoder.Store the resolved
FoundryHardforkdirectly and let network-specific metadata extract its relevant variant internally. This simplifies decoder configuration, precompile detection, and runtime refreshes. It also lets Base use the same builder, state, and update APIs instead of adding a parallel Base upgrade field and feature-gated call-site plumbing.