Try   HackMD

Deploying a Safe on Multiple Networks

Safe contract addresses are determined by the initializer function and a nonce. In order to deploy a Safe to the same address on multiple networks it is important to ensure the following conditions are met:

  • Same factory address is used on both networks
  • Same singleton address used on both networks
  • Same nonce used on both networks
  • The same initializer payload is used on both networks

This guide includes addresses for the latest v1.4.1 release of Safe. If the Safe you are trying to replicate is an earlier version you must find the old singleton address. This can be found in your original Safe creation transaction (see below)

Factory

The latest Safe factory is deployed to 0x4e1dcf7ad4e460cfd30791ccc4f9c8a4f820ec67 on most networks

Singleton Address

The v1.4.1 template Safe contract is deployed to 0x41675C099F32341bf84BFc5382aF534df5C7461a on most networks

Initializer

The initializer sets up the Safe settings like owners and thresholds. You must copy the initializer used on the first network to the second. However this means that the new Safe will match the original settings of the first Safe. If after setup you have changed signers, thresholds, modules, etc, you will have to make these changes on the new Safe as well

Example - Deploying to the same address on Sepolia and Scroll

Sepolia Deployment

This example uses a v1.4.1 Safe deployed on Sepolia first then Scroll second.

Sepolia Deployment Tx: https://sepolia.etherscan.io/tx/0xdce9314dea0d3080d26e347d0828918be17dbb6e290ac0cd5711a066d1728df1

Image Not Showing Possible Reasons
  • The image was uploaded to a note which you don't have access to
  • The note which the image was originally uploaded to has been deleted
Learn More →

  • Singleton: 0x41675C099F32341bf84BFc5382aF534df5C7461a
  • Initializer (REMEMBER to change this to your initializer): 0xb63e800d00000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000bd89a1ce4dde368ffab0ec35506eece0b1ffdc540000000000000000000000000000000000000000000000000000000000000140000000000000000000000000fd0732dc9e303f09fcef3a7388ad10a83459ec99000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000005afe7a11e7000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000100000000000000000000000001b2f8877f3e8f366ef4d4f482309491237338970000000000000000000000000000000000000000000000000000000000000024fe51f64300000000000000000000000029fcb43b46531bca003ddc8fcb67ffe91900c76200000000000000000000000000000000000000000000000000000000
  • Nonce: 1

Scroll Deployment

Scroll Deployment Tx: https://scrollscan.com/tx/0xdb2e69796a1ff5ba22392fceabd437b88e6c3c08cdd53788f8932571a827d4ab

  • Singleton: 0x41675C099F32341bf84BFc5382aF534df5C7461a
  • Initializer (REMEMBER to change this to your initializer): 0xb63e800d00000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000bd89a1ce4dde368ffab0ec35506eece0b1ffdc540000000000000000000000000000000000000000000000000000000000000140000000000000000000000000fd0732dc9e303f09fcef3a7388ad10a83459ec99000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000005afe7a11e7000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000100000000000000000000000001b2f8877f3e8f366ef4d4f482309491237338970000000000000000000000000000000000000000000000000000000000000024fe51f64300000000000000000000000029fcb43b46531bca003ddc8fcb67ffe91900c76200000000000000000000000000000000000000000000000000000000
  • Nonce: 1

Instructions

  1. Find the deployment transaction for the Safe you want to copy

Note the version of the previous Safe. I think if it's v1.3.x or v1.4.1 it will work

Image Not Showing Possible Reasons
  • The image was uploaded to a note which you don't have access to
  • The note which the image was originally uploaded to has been deleted
Learn More →

  1. Go to the Safe Proxy Factory contract on the new chain

https://scrollscan.com/address/0x4e1dcf7ad4e460cfd30791ccc4f9c8a4f820ec67#writeContract

  1. Enter the matching date on the createProxyWithNonce function and send the transaction

Image Not Showing Possible Reasons
  • The image was uploaded to a note which you don't have access to
  • The note which the image was originally uploaded to has been deleted
Learn More →

  1. Check transaction logs for the Safe address

This should match the original Safe address

Image Not Showing Possible Reasons
  • The image was uploaded to a note which you don't have access to
  • The note which the image was originally uploaded to has been deleted
Learn More →

  1. Visit the Safe on the UI

Enter your address in this link

https://app.safe.global/home?safe=scr:0x164730037ae0ccffb55dbd43df9cd6e040bf73e7

Image Not Showing Possible Reasons
  • The image was uploaded to a note which you don't have access to
  • The note which the image was originally uploaded to has been deleted
Learn More →

Last changed by 
 
Shield3
0
56

Read more

Verifying Multisig Transactions with Ledger

Context

Jun 6, 2025
SEAL Battlenet Initiative Proposal

Concept OverviewSEAL Battlenet is a live adversarial environment where teams can deploy and test new protocol versions with realistic network behavior prior to deploying on public main networks. Battlenet allows for rapid iteration to improve web3 security by creating a feedback loop between protocols, attackers, and security professionals in a controlled environment.What does success look like?We stop seeing the same types of exploits and vulnerabilities make their way into production because they are caught at an earlier stage, preventing harm to users and protocols. Alternatively, more unique bugs, exploits, and failure conditions means that Battlenet is working.What does failure look like?We continue to see the same issues exploited on Battlenet over and over, and continue to see them on mainnet chains as well. This would indicate that the feedback loop is not working, protocol teams are not improving, and we have not improved the safety of crypto.Why do we need a Battlenet?For ProtocolsBefore deploying new protocol versions, teams currently perform internal testing, deploy to testnets, work with external auditors, and set up bug bounties for security disclosures. Many teams also configure some sort of monitoring, paging, and incident response processes but the approach varies widely.

Sep 25, 2024
Onchain Summer Buildathon

Use Shield3 in your app

Jun 5, 2024
Cybersecurity Internship Opportunities in Web3

CMU has this program https://www.heinz.cmu.edu/programs/itlab/ where they set up students with projects to get some real life experience alongside their classes. It's not a guarantee and they need a short (1-2 paragraph write up) by mid-next week, but if you have something and would want to work with a group of students, lmk!

Jun 5, 2024
Read more from Shield3
Published on HackMD