Safe (Multisig) on Arc: Setup for Teams

A multisig is the difference between a team treasury and one person's wallet with a team's name on it. Safe (formerly Gnosis Safe) is the standard EVM multisig, and its contracts are deployed on Arc; this page covers whether the Safe{Wallet} app lists Arc yet, how to design signers and thresholds so the multisig actually protects you, and which project roles belong behind one. If you're launching on Arc for the kind of audience that reads validator lists, this is expected infrastructure.

Last reviewed: September 2026 · Next review by: November 30, 2026. Safe's network support and app status are re-checked every 90 days.

Is Safe available on Arc?

Two things, then. The contracts are on-chain, so a Safe on Arc is technically possible today. Whether you can create and operate one through the official Safe{Wallet} interface depends on Safe's app configuration exposing Arc — Safe's backend configuration references Arc, which suggests app support at or near mainnet, but there is no end-user "add custom network" option in Safe{Wallet}: chains appear when Safe enables them. Check the network picker at app.safe.global; if Arc is there, use the steps below. If it isn't yet, teams have two honest options: wait (and use a hardware-backed single signer meanwhile — Ledger setup), or interact with the deployed Safe contracts via a third-party or self-hosted interface, which is an engineering task rather than a click.

How do you design the multisig before you deploy it?

The design decides the security; the deployment is a form. Follow the Security Alliance's multisig framework, which is what serious teams and auditors reference: at least three signers, never a single owner in a "multisig"; a threshold of at least half — 2-of-3 or 3-of-5 are the common shapes — and never N-of-N, because one lost key would freeze the treasury forever; a hardware wallet for every signer (why), with mixed vendors and geographies where practical; one dedicated key per Safe rather than reusing a personal wallet; and out-of-band verification (a call, not a chat message) before any signer change. Decide, and write down, what the Safe is for — treasury, deployer, lock owner — and who can propose versus who can execute. On Arc specifically, budget nothing for gas anxiety: every Safe transaction costs cents in USDC (fees), so there is no economic reason to batch dangerously or skip a test transaction.

How do you deploy and operate it?

1. Each signer sets up their own hardware-backed wallet on Arc (MetaMask + Arc) and shares their address through a verified channel.
2. In Safe{Wallet}, choose Arc, create a new Safe, add signer addresses, set the threshold, and deploy. The deployer pays cents of USDC gas.
3. Send a small test amount to the Safe and execute a test transaction through the full propose-sign-execute flow before moving anything real.
4. Fund the Safe by bridging USDC or transferring from signers' wallets.
5. Every subsequent action — payroll runs, lock extensions, contract calls — is proposed by one signer, confirmed by others up to threshold, then executed. Each signer verifies the transaction details on their own hardware device; the Bybit loss in February 2025 happened precisely because signers approved a masked transaction their devices couldn't render. Read what you sign, every time.

Which project roles belong behind a Safe?

Three, in order of urgency. The treasury — obviously; a project's USDC and unallocated tokens should never sit behind one key. Lock and vesting ownership — the address that can extend your liquidity lock or manage vesting schedules controls your project's most important promises; Team Finance lets you transfer lock ownership to a Safe, and announcing that transfer is itself a trust signal buyers on Arc notice. And the deployer/admin role for any contracts with owner powers — a mint function behind a single hot wallet is one phishing email from a supply catastrophe (how those attacks work). Running payroll and distributions from the Safe via multisender closes the loop: money in, money out, all under threshold control.

FAQ

Is Safe live on Arc? Safe's contracts are deployed on Arc mainnet and testnet. Whether the official Safe{Wallet} app lists Arc is the practical question — check the network picker; the status table above is updated every 90 days.

What threshold should a small team use? 2-of-3 for small teams, 3-of-5 as you grow. Never 1-of-N (not a multisig) and never N-of-N (one lost key freezes everything).

What does a Safe cost on Arc? Safe charges no protocol fee. You pay Arc gas — cents in USDC — for deployment and each executed transaction.

Can our Team Finance locks be owned by a Safe? Yes. Create the lock from any wallet, then transfer ownership to the Safe address, or create it from the Safe directly once Safe{Wallet} supports Arc. Announce the transfer; on-chain it's visible either way.

Can I add Arc to Safe myself as a custom network? No — Safe{Wallet} has no user-side custom-network option; Safe enables chains centrally. Third-party or self-hosted interfaces to the deployed contracts are possible but are an engineering task.