fix: add multisig_address_book source to v2 calldata local address resolution#273
Merged
fix: add multisig_address_book source to v2 calldata local address resolution#273
Conversation
…solution Mirrors the v0.6.0 backport (1db4a24) for the v2 calldata path: when a "local" trusted name source is specified, also include MULTISIG_ADDRESS_BOOK alongside LOCAL_ADDRESS_BOOK. Made-with: Cursor
fsamier
approved these changes
Mar 16, 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
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.
Summary
"local"trusted name source is specified, also includeMULTISIG_ADDRESS_BOOKalongsideLOCAL_ADDRESS_BOOK.convert/calldata/v1/field.pybut was missing from the v2 path inconvert/calldata/convert_erc7730_v2_input_to_calldata.py.Test plan
"local"trusted name source now includesmultisig_address_bookMade with Cursor