Multisig Wallets for Ethereum

What is a multisig wallet? It is a wallet that needs more than one private key to approve a transaction. For small teams and communities, a 2-of-3 setup suits shared custody because no single signer can move funds alone.

Multisig is one part of choosing where to hold coins and tokens. For the wider comparison of options, see the guide to the best wallet for ethereum based coins. This article stays on shared control: how approvals work, how to pick a threshold, how to set up a Safe and how to plan for a lost key.

How a multisig wallet works

A multisig wallet replaces one all-powerful key with a group rule. The rule is usually written as M-of-N, where M signatures from N total signers are required to authorize a transaction. Each signer is a person or device holding one of the keys, and the threshold is the number M.

In practice, a payment moves through four stages:

1. Signers are named. Each signer holds a separate private key, ideally on their own hardware wallet.
2. A signer proposes a transaction. Safe, for example, tracks pending transactions and provides a user interface for proposal creation and approval workflows, as Zealynx’s glossary describes.
3. Other signers review and approve. The transaction stays pending until the threshold is reached.
4. The transaction is authorised. Once enough signatures are collected, the wallet accepts it. Until then, nothing moves.

Smart contract accounts and single-key accounts

A typical wallet has one private key attached to it, so whoever holds that key controls everything. A smart contract account works differently. Safe implements on-chain multisig logic through smart contracts that enforce the signature requirements. The approval rule lives in contract code, not in the secrecy of a single key.

This is why multisig on Ethereum is usually discussed as a smart contract wallet feature. The wallet is a contract that checks signatures before it releases funds. Anyone planning to hold tokens in such a contract should first understand what is an erc20 token and how wallets treat it.

A 2-of-3 setup versus a single-key wallet

A 2-of-3 multisig has three keys, and only two of them (M=2) are needed to approve any transaction. A single-key wallet is the opposite extreme: one key, one decision. The table sets out what that changes.

These comparisons draw on Material Bitcoin’s multisig explainer and Nonbank’s multisig overview.

Choosing signers and a threshold

The threshold is the main design decision, and it is a trade-off between safety and convenience. A higher M makes theft harder but makes every payment need more people. A lower M is quicker but lets fewer compromised keys cause damage.

• Small teams or families: 2-of-3 is described as good for small teams or families. It tolerates one unavailable signer and still blocks any single person.
• Larger treasuries: treasury multisigs holding protocol reserves or DAO funds typically use higher thresholds like 4-of-7 or 6-of-9. These are examples of what bigger groups use, not targets for a small group, which would struggle to gather that many approvals.
• Signer devices: each signer can store their private key on a hardware wallet for protection against software attacks, and signers should use diverse hardware wallet models rather than identical devices, per the same glossary. A flaw in one model then cannot affect every key.

The signer set and threshold are not permanent. They can typically be changed through transactions that meet the existing threshold, so a group can start small and adjust as membership changes.

Setting up a Safe wallet

Safe, formerly known as Gnosis Safe, is described as the most widely adopted multisig implementation for Ethereum. Its app handles proposals and approvals, so a group does not need to build its own process. General multisig guidance is to pick a trusted provider and follow its setup prompts, and that applies to Safe too. Decisions should be made before creating the wallet, in this order:

1. List the signers. Choose people who will respond reliably and who can each hold a key securely.
2. Give each signer a hardware wallet. Use different models where possible.
3. Set the threshold. Match it to the group size using the guidance above.
4. Create the Safe by following the app’s prompts. Confirm that every listed owner address is correct before continuing.
5. Test the approval flow. Propose a small transaction and have the other signers approve it, so everyone has seen the pending-transaction workflow before real funds arrive.

Signers who also use an everyday software wallet for personal spending can compare options in metamask vs trust wallet. Keep that wallet separate from the hardware-held signer keys.

Multisig for small teams and communities

Multisig suits a small team or community treasury when the money belongs to a group and nobody should be able to spend it alone. Business and organizational accounts benefit because shared control over funds facilitates accountability. Each payment has a visible set of approvers, which makes it easier to explain later.

The cost is coordination. Because transactions may take longer because of multiple approvals, a community should decide who may propose payments, who reviews them and how quickly signers are expected to respond. If a group cannot commit to this, a lower-friction arrangement may fit better. If it can, multisig removes the situation where one member’s mistake or dishonesty empties the treasury.

If a signer loses their key

Losing one key does not have to mean losing the wallet. In a setup where not all signers are required, users can still recover funds even if one or more private keys are lost. In a 2-of-3 wallet, the remaining signers can still reach the threshold, and nothing can be done without the other keys, so a stolen or lost key alone is not enough to take funds.

A sensible plan has three parts:

• Act promptly after a loss. The remaining signers should replace the missing signer, using a transaction that meets the existing threshold, before a second key is lost.
• Back up each key on its own. Every signer needs a separate recovery backup. Electrum, for example, provides a seed phrase of 12 recovery words at setup. Each seed phrase should be stored apart from the others.
• Do not pool backups. Keeping all backups in one place recreates the single point of failure that multisig exists to remove.

Frequently asked questions