fix(anvil): use latest active Tempo hardfork#15706
Merged
Merged
Conversation
mattsse
requested review from
0xrusowsky,
DaniPopes,
figtracer,
grandizzy,
mablr and
stevencartavia
as code owners
mablr
previously approved these changes
Jul 13, 2026
figtracer
previously approved these changes
Jul 13, 2026
Defaulting local Tempo chains to T7 exposed test gas caps and T0-specific assertions. Give current-fork transactions sufficient headroom, pin historical cases explicitly, and avoid zero-address AMM seeding where current forks reject it.
mablr
approved these changes
Jul 13, 2026
grandizzy
approved these changes
Jul 13, 2026
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
4 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.
Summary
Context
anvil --network tempouses local chain ID 31337, which is not present in Tempo's chain-aware activation schedules. The unresolved schedule previously fell back toTempoHardfork::default(), or T0, even though the currently active fork is T7. This disabled hardfork-gated precompile selectors, including the T2+ TIP-403 authorization methods used by ZonePortal deposits.Tempo CI always supplied
--hardfork T7, which masked the default local path. The fallback now reuses Foundry's existinglatest_active_tempo_hardfork()resolver, and CI omits the override unlessTEMPO_HARDFORKis explicitly set. Future Tempo activations therefore flow through the shared schedule without another Anvil-specific default update.Impact
Developers can run
anvil --network tempowithout an additional hardfork flag and get the latest valid Tempo behavior. Explicit hardfork selection remains available for historical compatibility testing.