Skip to content

Add Safe v1.5.0 canonical addresses - #2

Closed
techdigger wants to merge 2 commits into
mainfrom
pr/v150-addresses
Closed

techdigger wants to merge 2 commits into
mainfrom
pr/v150-addresses

Conversation

@techdigger

@techdigger techdigger commented Nov 12, 2026 •

Copy link
Copy Markdown

Replaced by #8: the same code as one commit on a clean branch.

safe_addresses.py lists contracts up to v1.4.1, so on a chain where only
v1.5.0 is deployed the interactive mode fails to find a Safe singleton,
fallback handler, proxy factory, MultiSend or SignMessageLib. Add the
v1.5.0 canonical addresses (safe-deployments v1.5.0) first in each list.
Listing v1.5.0 first made it the default on every network that has it:
safe-creator would create v1.5.0 Safes, update would move old Safes
straight to v1.5.0, and v1.4.1 Safes would be reported as not updated.
List it last instead, so networks with an earlier version behave as
before and networks with only v1.5.0 work.

Add a test for both cases, for all seven lists.
@techdigger techdigger closed this Nov 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant