Add New Networks
Safe's vision is to make every web3 account a smart account. Therefore, we prioritize teams and chains building with smart accounts, especially if they push account abstraction (for example, ERC-4337/EIP-1271 adoption) with Safe (learn more here (opens in a new tab)).
Safe's security is based on the contracts deployed in EVM-compatible networks. For the time being, we are not looking to extend beyond EVM.
To have the full Safe stack running on your chain network, you need to consider the following steps:
Deploy Safe canonical contracts
Process
- Follow the steps in the safe-contracts (opens in a new tab) GitHub repository.
- Create a GitHub issue using the Add new chain (opens in a new tab) template in the safe-deployments (opens in a new tab) repository.
- Create a Pull Request with the new Safe contract addresses in the safe-deployments (opens in a new tab) repository.
Cost
The contracts are fully open source, but gas is needed in the native currency of the new chain for contract deployment.
Timeline
Pull Requests on Safe's GitHub are reviewed roughly on a two-week cadence.
Deploy and maintain Safe{Wallet} and Safe{Core} infrastructure
Process
- Two possible options are available:
- Native integration in Safe{Wallet} (opens in a new tab): The Safe team runs all the infrastructure.
- Fill out this form (opens in a new tab) with your request.
- The Safe team evaluates the chains that need Safe{Wallet} or Safe{Core} support every quarter based on a priority matrix.
- Forked integration: All the infrastructure is run by a dedicated team who can be the new supported chain itself or an ecosystem third party like Protofire (opens in a new tab) or Den (opens in a new tab).
- Native integration in Safe{Wallet} (opens in a new tab): The Safe team runs all the infrastructure.
- Enter into agreement with your chosen provider.
Cost
- Safe is fully open source but requires someone to run and maintain the web interface (opens in a new tab) and infrastructure (opens in a new tab).
- Cost is based on the individual agreement (if run by any third party, including Safe).
- Primary cost factors:
- Deployment costs.
- Indexing.
- Cloud storage and monitoring services.
Timeline
- Based on the individual agreement with Safe.
- Prioritisation for native integration (app.safe.global (opens in a new tab)) is primarily based on the network's smart account/account abstraction strategy (for example, is every user account a Safe under the hood beyond the usage of Safe as a multi-signature for treasury management?) and additional metrics (opens in a new tab).