fix(cast,script): resolve transaction networks more consistently - #16790
Open
mablr wants to merge 1 commit into
Open
fix(cast,script): resolve transaction networks more consistently#16790mablr wants to merge 1 commit into
mablr wants to merge 1 commit into
Conversation
mablr
requested review from
0xrusowsky,
DaniPopes,
figtracer,
grandizzy and
mattsse
as code owners
September 10, 2026 17:39
Contributor
✅ Changelog foundThe deterministic check will validate the changed entry. |
mablr
enabled auto-merge (squash)
September 10, 2026 19:55
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.
Transaction commands previously resolved network-specific behavior at different stages and from different sources. This could produce inconsistent handling of explicit network flags, configured chains, RPC-discovered chains, and Tempo sessions, including selecting the wrong signing account or applying incompatible fee settings.
Centralize Cast network resolution with explicit configuration taking precedence over the configured chain and RPC discovery. Reject conflicting Tempo, Ethereum, and Celo selections; resolve Tempo session senders safely; and preserve legacy transaction and named-chain curl behavior.
Apply the same network conflict validation to Forge scripts so transaction execution follows consistent rules across both tools.
This change was developed with AI assistance.