Safe{Wallet} now lets you deploy Safes with the same address across multiple blockchains (gasless on major L2s) — a long-awaited feature that drastically improves how you can manage your assets on different networks.

• Unified Safe Address: Use a single Safe address on supported chains. No more confusion—just consistency.

• Effortless Multichain Management: Easily manage assets across chains from a single, user-friendly interface.

• Streamlined Workflow: Forget about setting up multiple wallets for different networks. Deploy a Safe Smart Account on any supported chain with just a few clicks—gas-free on major L2s.

When you deploy a Safe on your primary network (e.g., Ethereum), you can later add it to additional networks like Binance Smart Chain or Polygon while keeping the same Safe address. The process is seamless—just connect to the desired network from Safe{Wallet}, and the Safe will deploy on that chain. You can track all your Safes in the unified sidebar, easily switching between networks.

Creating Safes across multiple networks

Now you can create new Safes on multiple networks with the same address simultaneously.

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 & Compatibility

When adding a network to an existing Safe, it will keep the initial owner structure, threshold, and modules, unless modified after deployment. Multichain Safe deployment is compatible with smart contract accounts version 1.3.0 and above. Older master copies cannot be cloned, and Safes created outside Safe{Wallet} may not be compatible.

🚨 zkSync Era Compatibility: zkSync Era is not compatible with this feature, and sending funds to a zkSync Era address used on another chain will result in loss of funds.

Network-Specific Limitations: Safes using EIP-155 deployment on Optimism, Base, and Avalanche cannot be cloned to Polygon, Arbitrum, and other networks.

For more details, check the technical limitations here.

Safe{Wallet} now lets you deploy Safes with the same address across multiple blockchains (gasless on major L2s) — a long-awaited feature that drastically improves how you can manage your assets on different networks.

• Unified Safe Address: Use a single Safe address on supported chains. No more confusion—just consistency.

• Effortless Multichain Management: Easily manage assets across chains from a single, user-friendly interface.

• Streamlined Workflow: Forget about setting up multiple wallets for different networks. Deploy a Safe Smart Account on any supported chain with just a few clicks—gas-free on major L2s.

When you deploy a Safe on your primary network (e.g., Ethereum), you can later add it to additional networks like Binance Smart Chain or Polygon while keeping the same Safe address. The process is seamless—just connect to the desired network from Safe{Wallet}, and the Safe will deploy on that chain. You can track all your Safes in the unified sidebar, easily switching between networks.

Creating Safes across multiple networks

Now you can create new Safes on multiple networks with the same address simultaneously.

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 & Compatibility

When adding a network to an existing Safe, it will keep the initial owner structure, threshold, and modules, unless modified after deployment. Multichain Safe deployment is compatible with smart contract accounts version 1.3.0 and above. Older master copies cannot be cloned, and Safes created outside Safe{Wallet} may not be compatible.

🚨 zkSync Era Compatibility: zkSync Era is not compatible with this feature, and sending funds to a zkSync Era address used on another chain will result in loss of funds.

Network-Specific Limitations: Safes using EIP-155 deployment on Optimism, Base, and Avalanche cannot be cloned to Polygon, Arbitrum, and other networks.

For more details, check the technical limitations here.