refactor(tempo): derive broadcast fee token - #16222
Merged
Merged
Conversation
Use the active typed transaction environment as the source of fee-token data when cheatcodes capture broadcast calls and creates. This removes duplicate Tempo state from CheatsConfig while preserving explicit fee-token propagation for simulation and broadcast.
mablr
requested review from
0xrusowsky,
DaniPopes,
figtracer,
grandizzy,
mattsse and
stevencartavia
as code owners
August 17, 2026 15:32
Contributor
✅ Changelog foundThe deterministic check will validate the changed entry. |
figtracer
enabled auto-merge (squash)
August 18, 2026 14:28
figtracer
approved these changes
Aug 18, 2026
stevencartavia
approved these changes
Aug 18, 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.
Description
This simplification was found while preparing #16217.
This removes duplicate Tempo fee-token state from
CheatsConfigand instead derives the token from the active typed transaction environment when broadcast calls and contract creations are captured. This keeps the transaction environment as the single source of truth while preserving explicit--tempo.fee-tokenselections through simulation and broadcast. The regression coverage verifies that bothCREATEandCALLentries persist the selected token in the broadcast artifact.This change was developed and reviewed with AI assistance.