Safe Multisig Deployment and Operations for EVM Networks
Protofire deploys Safe on EVM networks that Safe Labs does not host. Under a written scope, we run the interface and its services, and the scope names who answers when the indexer stalls. The Optimism Foundation selected us in December 2023 and closed the mission as completed in January 2025.

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
On this page
Work shipped for 60+ networks and 95+ protocols, including
Safe for networks that Safe Labs does not host
Safe Labs hosts Safe{Wallet} only on the chains it selects, so most networks have no Safe-hosted screen to sign on. For example, your chain is live, and treasuries ask where they can create a Safe. Today the answer is a contract address.
Protofire delivers the Safe multisig deployment your network is missing, for foundations, DAOs and treasuries that cannot wait for Safe Labs to list their chain. If your institution only needs its own Safes set up with owners, thresholds and recovery, we do that work too.
Layers of Safe on your network and who runs them
Safe publishes the contracts and the code. On a chain Safe Labs does not host, someone has to run the three middle layers. Protofire builds them and runs them under a written scope.
Owners and their keys
Interface
Client Gateway and Config Service
Transaction, Decoder and Events Services
RPC and block explorer
Safe contracts
Why a chain needs a Safe interface and offchain services
On a new chain, Safe's contracts are the easy part, and the interface and its offchain services are the hard part.In September 2025 BGD Labs, Aave's technical provider, checked for a Safe interface when it evaluated Plasma. BGD Labs noted that the official Safe{Wallet} instance did not support Plasma. It named the Protofire Safe interface as an alternative interface for Plasma's Safe contracts.
Chainlink lists "a supported and audited multi-signature wallet implementation with a UI" among its requirements for a new chain. Protofire's oracle integration page covers the rest of Chainlink's list.
Safe{Wallet}, the interface Safe Labs hosts, listed 58 chains on 6 November 2026, 42 of them mainnets. Safe Labs adds chains quarterly, and "only for medium to large chains based on a strict scoring framework". Outside that list, Safes exist onchain with no Safe-hosted interface until someone runs one.
Each chain needs its own Transaction Service, which keeps a database and queues and reads the chain through RPC. If an RPC provider silently trims eth_getLogs results, the indexer breaks and owners can stop seeing new transactions. Only the service's database stores unexecuted proposals and their signatures.
The signing interface is a second risk. In February 2025 attackers altered the JavaScript of the hosted Safe{Wallet} front end, and Bybit's signers approved a disguised delegatecall. So the interface's build pipeline and file hosting belong inside the security boundary. Hosted interfaces have that risk, including the one Protofire hosts.
Without a Safe interface on the chain, a treasury that arrives has nowhere to sign, or it runs its own copy of the stack.
Our Safe record: networks, the Optimism Foundation and Lido
Protofire has worked on Safe since 2018.Four records are published on other people's pages.
- Network docs and postsImmutable's docs list safe.immutable.com as a "fork maintained by Protofire". Chiliz's docs say the Safe at safe.chiliz.com was deployed by Protofire. In 2023 we brought Safe to Rootstock with Sovryn, and we maintain it. We launched Zilliqa Safe in June 2024. In July 2026 Taiko moved its Safe users to our interface, together with their pending transactions.
- Optimism FoundationIn December 2023 the Optimism Foundation selected Protofire to deploy and maintain the Safe interface and backend for OP Chains. The Foundation closed the mission as completed in January 2025.
- LidoLido funded Protofire's Safe deployment on the Holesky testnet from October 2023 until that project closed in July 2025. Lido has funded our deployment on the Hoodi testnet since March 2025. We post a public report on Lido's forum at the end of each funding period. The reports list a Decoder Service rollout and checks for compromised npm packages. They also trace indexing failures to inconsistent RPC log ranges and record the move to Safe 1.5.0.
- Safe's own codeFrom late 2019 to mid 2021, Protofire engineers helped build the Gnosis Safe web app. In that period they wrote about 950 commits and about half of the app's merged pull requests, including the Safe Apps tab. In October 2025 the Safe Foundation named Protofire, at app.safe.protofire.io, among the independent teams that operated Safe{Wallet} instances. The Safe Foundation also granted funds for our separate SAFE staking interface on Safenet.
What Protofire delivers for Safe on your network
Safe contracts deployed, verified and submitted to Safe's registries
A team that checks for a Safe before it deploys finds one on your chain. Protofire checks your chain against what Safe's contracts need, deploys and verifies them, and opens the pull requests to Safe's deployments registries. Wallets and SDKs find the contracts at their registered addresses once Safe merges those pull requests and ships its next release. Safe decides the merge and the release.
A Safe interface and the services behind it
Treasury owners propose, review and sign in an interface that decodes a transaction where the contract's ABI is known. Your own systems receive webhooks. Protofire runs the services behind that interface and puts it on your domain, or your chain joins Protofire Multisig at app.safe.protofire.io.
Monitoring and maintenance of the Safe services
Protofire runs the Safe services under a written scope. When an owner's queue stops updating, the scope names who looks for the cause. We monitor indexer lag, RPC errors and service health. We back up the database that stores pending proposals and ship tested service updates in planned batches. A stalled indexer gets a written root cause. Each support period closes with a written log of updates and incidents, as in the reports we post for Lido's testnet work. We also host RPC nodes for chains that lack them, under the same scope, and build a Blockscout explorer for chains without one.
Owners, thresholds and recovery for an institution's Safes
If your institution sets up its own Safes, an auditor can read how money is approved. Protofire maps your authority matrix onto owners and thresholds, with separate Safes for separate approval tiers. Recovery runs through Safe{RecoveryHub} or a spare owner. Owners sign with hardware wallets, HSM keys or MPC keys. A guard set up wrongly can lock funds. An enabled module, such as the Allowance Module, can move funds without the owners' signatures. So we review guards and modules with your owners before they go live. RecoveryHub changes owners after a delay of 28 days by default and sends no alert, so your team watches the queue. On a chain that Safe{Wallet} already serves, this setup may be all you need from Protofire. Our treasuries page covers the wider treasury setup.
Safe Apps and backends for your own workflows
Your own systems can propose and track transactions without a person in the interface. Protofire builds Safe Apps that run inside the Safe interface, and backends that use Safe's Protocol Kit and API Kit. A delegate key can propose a transaction but cannot sign one, and your team keeps that key.
How a Safe multisig deployment with Protofire runs
You send your chain ID, RPC endpoints and explorer, or the approval rules your Safes must follow.A Protofire engineer studies them before the discovery call.
- Step 1
Written proposal
After the call you get a written proposal. It splits the work into the modules you need, so you commission one phase at a time. - Step 2
Chain checks and contract deployment
Protofire runs the chain checks first, then files the singleton factory request with Safe or uses the factory your stack ships with. We deploy and verify Safe 1.5.0, plus 1.4.1 and 1.3.0 where your tools expect them, and the Allowance Module for spending limits. On OP Stack chains, the factory and the 1.3.0 singletons are pre-installed. Safe asks that the chain be listed on chainlist.org. On legacy ZKsync EraVM chains, the newest Safe version is 1.4.1. - Step 3
Services and interface setup
Protofire sets the indexing mode with you. The mode is SafeL2 with event logs, unless the chain has a tracing archive node and a reason to index the L1 Safe. We register the contracts in the Transaction Service, set the reorg depth from your chain's finality and configure the gas price source. Owners see proposals and history from the first block you choose to index. - Step 4
Operation and handover
Protofire runs monitoring, backups, updates and reports for the period the written scope names. When you decide, the scope covers a handover. We pass the services to your own team with the database, configuration and runbooks. Or we prepare the switch to Safe Labs' hosting once Safe Labs lists the chain. Safes keep their addresses and no funds move. Safes on the L1 singleton, on a modified fork or on legacy ZKsync EraVM migrate first.
Who owns the Safes, keys and code
Whoever runs the services, the owners of your users' Safes control those Safes, their funds and their keys.With a dedicated deployment, your agreement with Protofire makes the code and the contracts yours. A network that joins Protofire Multisig at app.safe.protofire.io shares an interface that runs on Protofire's servers. The full terms are on how we work.
- Proposal
- In writing, one business day after the discovery call: findings, a plan in phases and the first step we recommend.
- Price
- Fixed per phase when you commission it, against written acceptance criteria. Overruns inside them are ours to absorb, invoices follow delivered milestones, and you can stop at any phase boundary. Anything we operate after launch is priced in the proposal as its own recurring line, with the notice to end it.
- Ownership
- Code we write for you, contracts, the keys and credentials this work creates and the accounts your infrastructure runs in are yours by contract, within the license of any third-party software involved. Keys that a custody platform or a staking provider holds under its own key model stay with it under your contract; every other custody key stays with you or the custodian you appoint. Where the scope places something on servers we rent, it says what moves to you and when. An NDA is available from your first message, and we sign a data processing agreement (DPA) together with it.
- After launch
- Delivery closes with a hypercare window and a defect warranty, with their terms written into the proposal. A service we operate continues under its written scope until that scope ends.
- Access
- Read-only by default. A role that can start requests only if your written scope names one; never a signer, approver, administrator, key holder or recovery role on your contracts, wallets or custody platform. Services we build call each platform on credentials your staff issue and keep in your vault. Anything that approves or moves funds runs in your environment, and a scope under which we operate a service lists every write call it makes. Where the scope has us operate nodes, validators, monitors, explorers or indexers, it names the role and any key we hold on those servers, and in your own cloud account you can remove it.
- Licenses
- Protofire is an engineering firm and holds no financial or crypto-asset license; licensed activity stays with you and your providers.
How we work shows a worked proposal.
When a Safe deployment with Protofire does not fit
Safe Labs' own hosting, a contracts-only deployment or MPC custody serves some buyers better.
- Your chain qualifies for Safe Labs' own hosting, and you want it in app.safe.global. Safe Labs sells that hosting directly, and your users reach the chain from the app they already use.
- You need only the contracts. A team can deploy them through Safe's factory and registry, and the cost is gas.
- Your assets are on Bitcoin, Solana or other non-EVM chains, or they must be held in a qualified custodian's own wallets. The same applies if your approval structure must be kept off a public chain. Safe has said it does not plan to go beyond EVM. Anyone can read a Safe's owners and threshold onchain. Our crypto custody guide compares MPC custody and qualified custodians.
- Your chain needs changes to Safe's core contracts. Such changes make a fork, which needs its own audit and is outside Safe's audits and registry.
FAQ
Who can deploy and run Safe multisig on a new EVM network?
What does a network need to run Safe besides the contracts?
Does Safe already support our chain?
Who operates Safe once a chain is live?
Who holds the keys to a Safe that Protofire deploys?
What happens to our Safes if Protofire stops running the services?
Can our network move to app.safe.global later?
Get a proposal
Tell us what you are building. An engineer reads it, we have a short call, and the written proposal follows within one business day.
