Introduction
Safe now offers counterfactual deployments across multiple chains directly from the user interface. This feature allows you to reserve and deploy your Safe address across multiple networks simultaneously.
Key Features
Create your Safes with the same address across networks
Flexible deployment options (multi-chain at once or add networks later)
New Sidebar interface for managing multiple accounts
Deployment Process
Creating Safes across multiple networks
Now you can create new Safes on multiple networks with the same address simultaneously;
Creating a Safe is free but to activate them the asset for the respective chains will need to be present in the Wallet in order to pay the fees i.e. $BASE, $POL.
We also take advantage of Gelato 1balance technology to provide sponsored transactions (five per day) on several L2 chains.
If you already have an existing Safe account you want to add a network to this now takes no longer than a few seconds using the reworked network selector.
Technical Information
These multi-chain accounts will be created using the same transaction data to create the first one.
When adding a network to an existing Safe, it will be created with the initial owner structure, threshold and modules.
These will vary if you modified the Safe after deployment.
Compatibility
Compatible with smart contract accounts version 1.3.0 and above.
Safes created from master copies (versions 1.1.1, 1.2.0, 1.0.0) cannot be cloned even if they were upgraded to newer versions.
Some Safes that were created outside of Safe{Wallet} might also not be compatible with adding new networks.
🚨 zkSync Era is not compatible with this feature.
It is not possible to create Safes on zkSyncEra with the same address as on other networks.
This is important to note as if you do send funds via ZkSyncEra to a Safe address already in use they will be lost.
Network-Specific Limitations
In some cases when creating Safe’s, they will be migrated from their older versions on creation, you will see the following screens when doing so.
The same warning displayed when adding signers to the account;
For Safes created via our user interface:
Optimism, Base and Avalanche 1.3.0 L2 Safes using the EIP155 deployment cannot be cloned to: Polygon, Arbitrum, Scroll, Blast, Worldchain, Gnosis Chiado.
🗒️ These limitations primarily affect Safes created through our UI. Other interfaces may be different.
Best Practices
1. Plan your deployment across networks before initiating.
2. Ensure compatibility and sufficient assets on each network for fees.
3. Start with smaller transactions to familiarise yourself with each network's characteristics.
Multi-chain Safe deployment offers unprecedented flexibility in asset management. While powerful, users should be aware of compatibility considerations. For questions or support, please contact our team.