I plan to deploy Safe Smart Wallet contracts on a new emerging chain that isn’t currently listed by Safe Labs and Safe Foundation. After reviewing the README, I noticed that it requires your signature for deployment on the chain, correct? What happens if I deploy the project without your signature? Is there an alternative way to do that? If I proceed without the signature, will I still be able to initialize it?
Hi there. For support, please open a ticket via the chat bubble at the bottom-right of the OFFICIAL Safe Help Center only. Safe{Wallet} Help Center and Support.
You can technically deploy the Singleton and related Safe contracts on a new chain without an official signature from Safe, but there are a few important trade-offs to understand.
The signature requirement in the README is mainly about official recognition and trust. Safe uses those signatures so that interfaces (like the Safe web app and other ecosystem tools) can verify that the deployment is authentic and hasn’t been tampered with. If you skip that step, your deployment won’t be recognized as “official,” which can limit compatibility with existing tooling.
From a purely technical standpoint, yes—you can still deploy and initialize the contracts yourself. The contracts don’t inherently block initialization just because they aren’t signed. However:
-
You’ll be responsible for ensuring everything is deployed correctly (addresses, proxies, configs, etc.)
-
Some Safe services (like transaction services or UI integrations) may not support your chain or deployment
-
Users may have to interact with your setup manually or through custom interfaces
If your goal is experimentation or internal use, going unsigned is usually fine. But if you’re aiming for broader adoption, it’s worth coordinating with the Safe team to get an official deployment.