How to deploy Safe Wallet on a new blockchain

Note: This tutorial is contributed by our colleague shelchin. Thanks for his efforts!

Three weeks ago, just like you, I felt both excited and a bit uneasy about deploying Safe Wallet. After continuous attempts and learning, I have finally mastered the skills of deploying and managing Safe Wallet. I am ready to share this process with you in this tutorial.

I will deploy Safe Wallet on the Endurance mainnet. The Endurance mainnet was successfully launched in January 2023, and it is a new Layer1 blockchain compatible with EVM. It provides a solid foundation for the Web3 AAA game Fusionist. If you are planning to deploy Safe Wallet on this newly launched blockchain like me and want to inherit its accumulated reputation, then you have come to the right place. Additionally, if you are concerned about potential service disruptions with Safe Wallet and wish to quickly set up a backup system, this is also where your needs can be met.

The image source is: https://docs.safe.global/advanced/api-service-architecture

The diagram clearly illustrates the architecture of the Safe Wallet service. However, I believe it still overlooks three key components: first, the RPC service for EVM-compatible chains; second, the corresponding blockchain explorer service; and third, the complete suite of Safe Wallet smart contracts deployed on this chain.

You can access the following two websites to search for and obtain the necessary information about Endurance: https://chainlist.org/?search=endurance and https://github.com/ethereum-lists/chains/blob/master/_data/chains/eip155-648.json.

This tutorial consists of the following two topics:

1. How to deploy the complete Safe Wallet smart contract suite on the Endurance chain.
2. How to deploy the full Safe Wallet service for the Endurance chain.

How to deploy the complete Safe Wallet smart contract suite on the Endurance chain

In order to deploy Safe-related contracts on multiple blockchains, the first step is to deploy safe-singleton-factory, which is a singleton factory specifically designed for this purpose.

In previous discussions, we mentioned the desire to “inherit its accumulated reputation.” From my perspective, the trustworthiness of a contract depends on whether its address is widely used and if its corresponding source code is open-source and has been audited by multiple independent parties. The official Safe contract meets these criteria. On a new blockchain, inheriting the accumulated reputation means wanting the newly deployed contract address to match that of the official Safe contract, thus naturally inheriting its reputation. To achieve this, you need to request Safe’s officials to deploy a singleton factory on this new chain and ensure that when deploying the Safe wallet contract, they use the same version and git commit id.

For specific instructions on how to request the deployment of a singleton factory from officials, please refer to Safe Developer Documentation.

After submitting the deployment request, it usually takes 1-2 weeks to receive official approval. However, Safewallet typically only approves deployment requests for the main network. If you wish to deploy or test on a local network or private network, you will need to deploy the safe-singleton-factory contract yourself. Below is the process I followed when deploying these test contracts:

Compile and deploy safe-singleton-factory.

# Clone the source code repository
git clone https://github.com/safe-global/safe-singleton-factory.git
cd safe-singleton-factory

# Compile contract
yarn
yarn hardhat compile

# Copy .env
cp .env.sample .env 

# Estimated Gas
yarn estimate-compile "https://rpc-endurance.fusionist.io"

# Deploy contract
yarn submit

Successfully deployed contract address: 0x181500A79F8e0dd760Bf6856c84440FC029ed7d4

Compile and deploy safe-smart-account

# Clone the source code repository
git clone https://github.com/safe-global/safe-smart-account
cd safe-smart-account

# Switch to version 1.4.1 of the contract
git switch --detach tags/v1.4.1-build.0

# Compile contract
yarn
yarn build

# Copy .env
cp .env.sample .env 

# Deploy contract
yarn hardhat --network custom deploy

Please note: If you want to deploy the safe-smart-account contract on the mainnet, you need to wait for Safe’s official deployment of safe-singleton-factory on your mainnet.

Due to version 1.3.0 not relying on safe-singleton-factory, you will have a smoother experience.

If you encounter the following error during the deployment of version 1.4.1:

Error: 
        Safe factory not found for network 648. You can request a new deployment at https://github.com/safe-global/safe-singleton-factory.
        For more information, see https://github.com/safe-global/safe-contracts#replay-protection-eip-155

This typically means that the safe-singleton-factory contract address for your specified network is not included in the @gnosis.pm/safe-singleton-factory package. You will need to manually add the contract address to the corresponding directory at node_modules/@gnosis.pm/safe-singleton-factory/artifacts.

The following are detailed operational steps along with their annotations:

# Create a temporary directory to store the modified artifacts.
mkdir /tmp/safe-singleton-factory

# Copy the artifacts from the current node_modules to a temporary directory.
cp -r ./node_modules/@gnosis.pm/safe-singleton-factory/artifacts /tmp/safe-singleton-factory/artifacts

# Rename the current 'artifacts' directory to 'backup' for archival purposes.
mv ./node_modules/@gnosis.pm/safe-singleton-factory/artifacts ./node_modules/@gnosis.pm/safe-singleton-factory/artifacts-bak

# Create a symbolic link to point the "artifacts" folder in the "node_modules" directory to a temporary directory.
ln -s /tmp/safe-singleton-factory/artifacts ./node_modules/@gnosis.pm/safe-singleton-factory

# Verify if the symbolic link has been successfully created.
ls -l ./node_modules/@gnosis.pm/safe-singleton-factory/

# Create a directory for network ID 648.
mkdir /tmp/safe-singleton-factory/artifacts/648

# If the safe-global/safe-singleton-factory repository already contains your chain information.
wget -O /tmp/safe-singleton-factory/artifacts/648/deployment.json https://raw.githubusercontent.com/safe-global/safe-singleton-factory/main/artifacts/648/deployment.json

# If the safe-global/safe-singleton-factory repository does not have your chain information.
# You need to create a deployment.json file in the directory /tmp/safe-singleton-factory/artifacts/648 and fill it with the following content.
echo '{
	"gasPrice": "your tx gas price",   
	"gasLimit": "your tx gas limit",  
	"signerAddress": "your signer address",  
	"transaction": "your signed tx",   
	"address": "0x181500A79F8e0dd760Bf6856c84440FC029ed7d4"  # Your safe-singleton-factory contract address
}' > /tmp/safe-singleton-factory/artifacts/648/deployment.json

Please replace the following parameters with the specific details of your transaction: your tx gas price, your tx gas limit, your signer address, and your signed tx. You can obtain this information by visiting the following link: 0xa450888b56f3306861c64619cba67a8f54dbbe65bcb2ef0f1568cf81eba2139d.

Obtain your signed tx

curl -X POST -H "Content-Type: application/json" --data '{
  "jsonrpc": "2.0",
  "method": "eth_getRawTransactionByHash",
  "params": ["0xa450888b56f3306861c64619cba67a8f54dbbe65bcb2ef0f1568cf81eba2139d"],
  "id": 1
}' https://rpc-endurance.fusionist.io

The value after my replacement is:

echo '{
	"gasPrice": "1500000007",  
	"gasLimit": "96586", 
	"signerAddress": "0x36C8403082Fc6dF260FCa47C5a0F2141D6840039",  
	"transaction": "0xf8a6808459682f078301794a8080b853604580600e600039806000f350fe7fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffe03601600081602082378035828234f58015156039578182fd5b8082525050506014600cf3820533a07941a82aae53b4ed2a63be73c72e221dac750305c5270cd69ad48cab0bfb10d6a04657e52a6fd68effa9f6c97a4533333644e86eac9fe30871b948b094b1e21b7a",   
	"address": "0x181500A79F8e0dd760Bf6856c84440FC029ed7d4"  
}' > /tmp/safe-singleton-factory/artifacts/648/deployment.json

After successful deployment, you will receive a series of contract addresses:

How to deploy the full Safe Wallet service for the Endurance chain

# Clone the source code repository
git clone https://github.com/OpenFusionist/how-to-self-host-safe-wallet.git
cd how-to-self-host-safe-wallet/safewallet

# Copy .env
cp .env.sample .env

# Start 
docker network create safe_shared_network
docker compose -f docker-compose.core.yml -f docker-compose.tx.yml up -d

Add the Endurance chain in the safe-config-service.

Introduction: https://docs.safe.global/advanced/api-service-architecture

URL: http://localhost:8008/cfg/admin/chains/chain/add/

Refer to the following table:

Add a Safe App in the safe-config-service.

URL: http://localhost:8008/cfg/admin/safe_apps/safeapp/add/

Refer to the following table:

Add a proxy factory to the safe-transaction-service.

Introduction：https://docs.safe.global/advanced/api-service-architecture

URL: http://localhost:8008/txs/admin/history/proxyfactory/

Refer to the following table:

Add the master copy to the safe transaction service.

URL: http://localhost:8008/txs/admin/history/safemastercopy/

Refer to the following table:

🎉 Congratulations! The Safe Wallet service is now fully launched and you can access the Safe Web App through http://localhost:8008.

If you need to deploy Safe Wallet on another chain, simply follow the steps above: first deploy the smart contract suite, then start the full Safe Wallet service. This way, you can easily expand to a new blockchain network!