Skip to main content
The Safe Singleton Factory is a minimal proxy factory that enables deterministic deployment of Safe (formerly Gnosis Safe) multisig wallets and related contracts. It uses CREATE2 to ensure the same wallet addresses across all EVM chains. Contract Address: 0x914d7Fec6aaC8cd542e72Bca78B30650d45643d7 Deployment Status: Default preinstall Repository: github.com/safe-global/safe-singleton-factory
Known Issue - Bytecode Verification RequiredThe Safe Singleton Factory bytecode in the current DefaultPreinstalls (x/vm/types/preinstall.go:30-32) is currently identical to the Create2 factory bytecode, which is incorrect.Before deploying this contract in production:
  1. Verify the correct Safe Singleton Factory bytecode from the official repository
  2. Update your genesis configuration with the correct bytecode
  3. Test the deployment on a testnet first
This issue is tracked and will be addressed in a future release. For now, you should manually verify and update the bytecode if you need Safe Factory functionality.

Key Features

  • Deterministic Deployment: Same Safe addresses across all chains
  • Minimal Implementation: Simple factory pattern using CREATE2
  • Version Agnostic: Deploy any version of Safe contracts
  • Gas Efficient: Optimized proxy deployment pattern
  • Ecosystem Standard: Used by Safe infrastructure globally

How It Works

The factory uses a two-step deployment process:
  1. Deploy Singleton: Deploy the Safe master copy (implementation)
  2. Deploy Proxy: Deploy minimal proxies pointing to the singleton
This pattern enables gas-efficient deployment of multiple Safe wallets sharing the same implementation.

Core Method

The factory has a single method that deploys contracts using CREATE2.

Usage Examples

Deploy a Safe Wallet

Predict Safe Address

Calculate the deployment address before deploying:

Deploy with Custom Configuration

Deployment Patterns

Organization Wallets

Deploy consistent treasury addresses across chains:

Counterfactual Wallets

Create wallets that can receive funds before deployment:

Integration with Safe Ecosystem

Safe Modules

Deploy and enable Safe modules:

Safe Guards

Deploy transaction guards for additional security:

Best Practices

Salt Management

Version Control

Gas Optimization

  • Deploy singleton once per chain
  • Reuse proxy bytecode
  • Batch deployments when possible
  • Use minimal initializers

Security Considerations

  • Initialization: Ensure Safes are properly initialized after deployment
  • Salt Uniqueness: Use unique salts to prevent address collisions
  • Singleton Verification: Verify singleton contract before deployment
  • Access Control: The factory itself has no access control - anyone can deploy

Troubleshooting

Safe Infrastructure

Further Reading