Set Up Multisig Wallet (Gnosis Safe): Step-by-Step
Managing shared crypto funds with a team is risky if a single person holds the keys. One compromised device can drain an entire treasury. A multisig wallet solves this by requiring multiple approvals for transactions. Gnosis Safe (now just 'Safe') is the most battle-tested multisig solution on Ethereum and compatible EVM chains, used by DAOs, investment clubs, and developer teams.
In this guide, you will learn how to create a Safe wallet from scratch, add co-signers, choose a sensible threshold, and fund it. We'll also cover security best practices such as using hardware wallets for signers, rotating owners, and understanding transaction queue management. By the end, you'll have a production-ready shared wallet that protects team funds against single points of failure.
- Gnosis Safe is the most trusted multisig wallet: non-custodial, audited, supports Ethereum and major L2s.
- A simple 2-of-3 configuration protects team funds against a single compromised key while remaining convenient.
- Always use hardware wallets for signers and verify all transaction details off-chain before confirming.
- Owner management (add/remove) requires the current threshold approval — no one can change the setup alone.
- Whoever executes a transaction pays gas from their own wallet, so each signer should keep a small buffer of the native token; on L2s this is negligible.
- Treat the Safe address as you would an account number: never share its private keys (there are none) but monitor its activity.
What Is a Multisig Wallet and Why Use Gnosis Safe?
A multisignature (multisig) wallet requires more than one private key to authorize a transaction. Instead of a single owner, you define a set of signers and a threshold — for example, 2-of-3 or 3-of-5. Gnosis Safe is a non-custodial smart contract wallet that implements this logic on-chain. It is one of the most audited contracts in DeFi, with a track record of securing billions of dollars.
Using Safe for team funds eliminates the risk of a single leaked key. Even if one signer's device is compromised, an attacker cannot move funds without the other signers' approval. Safe also supports advanced features: spending limits, session keys for automation, and modules like Zodiac for DAO governance. The web interface is intuitive and works with all major wallets (MetaMask, Ledger, WalletConnect).
Security tip: Always deploy a new Safe with a threshold of at least 2-of-3 if there are three signers. Never use a 1-of-N setup — that defeats the purpose of a multisig.
Prerequisites: Wallets, Networks, and Signer Requirements
Before creating a Safe, each team member needs their own wallet. For maximum security, use a hardware wallet like Ledger or Trezor. Software wallets (MetaMask, Rainbow) are acceptable for testing small amounts but are more vulnerable. Decide how many signers you want and what threshold (minimum approvals needed). A common setup for a small team is 3 signers with a threshold of 2.
Choose the blockchain network: Safe works on Ethereum Mainnet, Polygon, Arbitrum, Optimism, Gnosis Chain, and many others. For teams, mainnet is typical but gas fees can be high; consider a low-fee L2 like Arbitrum for frequent transactions. Each signer needs at least some native coin (ETH, MATIC, etc.) in their own wallet to pay gas when they execute a transaction — confirmations themselves are gasless off-chain signatures, and by default the gas for an outgoing transfer is paid by the executing signer's wallet, not from the Safe's own balance.
| Number of Signers | Recommended Threshold | Use Case |
|---|---|---|
| 3 | 2-of-3 | Small team, daily operations |
| 5 | 3-of-5 | Larger team, higher security |
| 7 | 4-of-7 | DAOs with broader member base |
Step 1: Create a New Safe on the Web App
Navigate to app.safe.global (formerly gnosis-safe.io). Connect your wallet (e.g., MetaMask) and select the network where you want to deploy the Safe. Click 'Create Safe'. You will be prompted to give your Safe a name — this is only stored locally for display, not on-chain.
Next, add signers. Paste each team member's address (Ethereum address) or ENS name. You must add at least two owners. Set the threshold: the minimum number of approvals needed. For a 3-signer team, 2 is the sweet spot — balances security with convenience. Confirm the addresses carefully. Once submitted, you'll need to sign a transaction to deploy the Safe smart contract. This costs gas (paid by the creator). After a few block confirmations, your Safe is live with its own address.
Important: Write down the Safe address and share it with all team members. You can also bookmark the Safe's page on the web app for easy access.
Step 2: Fund the Safe and Execute Your First Transaction
To use the Safe, you need to send assets (ETH, ERC-20 tokens, NFTs) to its address. Use any wallet to transfer funds normally. Since the Safe is a smart contract with no private key, funds are controlled by the signer set. Once funded, you can propose transactions.
From the Safe app, click 'New transaction'. Choose the token and recipient. Specify the amount and optionally add a detailed description (e.g., 'Q1 marketing budget payment'). Click 'Submit' — your wallet will prompt you to sign a message (not a gas transaction yet). This creates a 'proposal' visible to all signers. Other owners then go to the 'Queue' or 'Transactions' tab and 'Confirm' the transaction. Once the threshold is reached, the transaction is executed automatically (if you choose the 'execute' option) or you can batch multiple confirmations and execute later. Confirmers will pay gas on Mainnet; on L2s gas is trivial.
Pro tip: Always use the 'Comment' field to explain the purpose of a transaction. This creates an auditable trail for the team.
Step 3: Advanced Security and Owner Management
Over time, team members may leave or devices change. Safe allows you to add or remove owners without creating a new wallet — but it requires a transaction signed by the current threshold. For example, to remove a signer, propose a transaction to the Safe's 'Settings' > 'Owners' section. The full signer set must approve the change. This is a key security feature: no unilateral changes.
You can also set up spending limits for individual signers — useful for routine small payments without needing full multisig approval each time. Additionally, consider using a 'delay module' that adds a time lock between confirmation and execution, or integrate with Zodiac for advanced governance. For maximum security, each signer should use a separate hardware wallet, never store seed phrases online, and verify all addresses before signing.
| Action | Approval Needed | Gas Cost |
|---|---|---|
| Add new signer | Existing threshold | Low (transaction) |
| Remove signer | Existing threshold | Low |
| Change threshold | Existing threshold | Low |
Step 4: Using the Safe Day-to-Day – Queues, Confirmations, and Notifications
All pending transactions appear in the 'Queue' tab. Each signer should regularly check the queue, even if not the proposer. Confirmations are simply signing messages — you are not executing the send yet. Only when the threshold is met and someone clicks 'Execute' does the blockchain transaction happen. This execution can be done by anyone, not just a signer, to distribute gas costs.
For notifications, use the Safe Mobile App (iOS/Android) or set up a Discord/Telegram bot via Safe's webhook APIs. Some teams use third-party tools like Multis or Parcel to track approvals. The important habit: never rush. Always verify the recipient address and amount with the rest of the team through a separate communication channel (e.g., Signal or Slack) before confirming.
If a transaction is incorrectly proposed, it can be rejected: any signer can mark it as 'Rejected'. Rejected transactions are removed from the queue but stay on the history.
Common Pitfalls and How to Avoid Them
- Losing threshold access: If you lose enough signers to reach below threshold, funds are locked forever. Always keep at least one backup signer (e.g., a multisig you control) or document recovery procedures.
- Phishing for Safe approvals: Never sign messages outside the official Safe app. Verify you are on app.safe.global. Use browser bookmarks.
- Over-relying on software wallets: A hot wallet as a signer is a risk. Encourage team members to use hardware wallets for signing.
- Ignoring gas fees on execution: Executing a Safe transaction costs gas, paid by the executing signer's own wallet. Make sure signers keep a small buffer of ETH/MATIC to cover it.
Security rule: For any transaction over $10,000 (or your team's risk threshold), require at least two signers to verify the destination address via a separate call or video confirmation.
Frequently asked questions
Can I use a Ledger as a signer for a Gnosis Safe?
Yes. Connect your Ledger via MetaMask or WalletConnect. The Safe app recognizes it as a signer. Each signer should use their own hardware wallet for maximum security.
What happens if I lose my hardware wallet or seed phrase?
If you are one of several signers and the threshold is still reachable by the remaining signers, you can remove the lost owner via a transaction. If you lose so many that threshold cannot be met, the funds are permanently locked. Always maintain a backup signer (e.g., a second hardware wallet) or a time-locked recovery module.
Is it free to create a Safe?
No, deploying the Safe smart contract costs gas (network transaction fee). On Ethereum Mainnet this can be significant; on L2s like Arbitrum it is minimal. The cost is paid by the creator's wallet.
Can I change the threshold after creation?
Yes. Go to Safe Settings > Owners & Modules. You can propose a change to the threshold. It requires approval from the current number of signers equal to the existing threshold.
Related reading
Track the entities behind the concepts
DeFi Intel maps 11,000+ protocols, tokens and companies to a typed knowledge graph — with live data, incidents and regulation.