How to Use a Multisig Wallet (Safe)

How to set up a Safe (formerly Gnosis Safe) multisig: signers, threshold, modules, and recovery best practices.

What you'll need (prerequisites)

• Self-custodial wallet
• A second device for verification
• Block explorer (Etherscan, Solscan, etc.) familiarity

Step-by-step

1. Step 1: Understand what multisig is

   A multisig wallet requires several independent signatures — M of N owners — before any transaction can move funds, so no single compromised key can drain the account. A 2-of-3 setup, for example, needs any two of three owners to approve. This removes the single point of failure that makes ordinary single-key wallets risky for treasuries and long-term holdings.

2. Step 2: Choose your owners and threshold

   Decide who the owner keys are and how many must sign (the threshold), balancing security against the risk of losing access. Common choices are 2-of-3 for individuals and 3-of-5 for teams, giving redundancy if one key is lost while still blocking a lone attacker. Avoid a threshold equal to the owner count (such as 3-of-3), which leaves no margin if a single key is lost.

3. Step 3: Deploy a Safe on your chain

   Go to app.safe.global, connect a signer wallet, select the network you want the Safe on (Ethereum, an L2, and so on), and create a new Safe. Deployment is an on-chain transaction, so keep some native gas token in the connecting wallet. The Safe you create lives at its own address on that specific chain.

4. Step 4: Add owner addresses and set the threshold

   During creation, enter each owner's address and set the number of required confirmations. Double-check every address, ideally by verifying it on each owner's own device, before finalizing. You can change owners or the threshold later, but each change is itself a multisig transaction that must clear the current threshold.

5. Step 5: Propose, confirm, and execute a transaction

   To move funds, one owner proposes a transaction, then the required owners review and confirm it with their own wallets. Once the threshold of confirmations is reached, any owner can execute it on-chain. Each signer should verify the destination and amount on their own hardware device before confirming.

6. Step 6: Follow signer best practices

   Use hardware-wallet signers and spread the owner keys across different devices, people, and physical locations so no single breach or disaster can reach the threshold. Keep secure backups of every owner key and document a recovery path for replacing a lost or compromised owner. Periodically review the owner set and threshold as your team or holdings change.

Common errors and fixes

• Approval can't be revoked due to insufficient gas. Revoke transactions cost the same gas as a normal token transfer. Top up the wallet with a small amount of native gas token before revoking.
• Funds already drained. On-chain theft is generally irreversible. Document everything, file police / IC3 / Chainalysis Reactor reports, and contact the protocol team if a known exploit. CEX-side funds may be recoverable if the attacker on-ramped to a regulated exchange.
• Suspected key leak but no losses yet. Move all funds immediately to a freshly created wallet. Burn the old seed. Audit every device the seed touched (browser extensions, cloud backups, email).
• Cannot identify the malicious contract. Use Etherscan's "advanced filter" to filter by token approvals and unusual contract calls. Run the suspicious tx through Tenderly to decode the call.
• Phishing email looks real. Always verify by typing the URL manually. Real exchanges and protocols never email asking for seed phrase, password, or 2FA codes — full stop.

FAQ