All guides

CONCEPTS

What is a multisig?

A multisig (multi-signature) wallet is a shared wallet that requires multiple people to approve a transaction before it can be executed. No single person can move funds alone.

The problem with a single key

A regular wallet is controlled by one private key. Whoever holds that key has complete control: they can send funds anywhere, at any time, with no oversight. That is fine for personal spending money, but it becomes a liability the moment the wallet holds funds that belong to more than one person — a team treasury, a community fund, protocol reserves. One compromised laptop, one lost seed phrase, or one bad actor is all it takes.

How a multisig fixes it

A multisig is a smart contract that holds the funds instead of any individual. The contract keeps a list of owners and a threshold — the number of owner approvals a transaction needs before it can run. A “2 of 3” multisig has three owners and executes only when at least two of them approve.

  • No single point of failure. One leaked key cannot drain the wallet — an attacker would need to compromise enough keys to meet the threshold.
  • Built-in accountability. Every transaction is proposed, reviewed, and approved by multiple people before it moves funds.
  • Enforced onchain. The rules live in the contract, not in a company policy. Nobody — including the app you use to manage it — can bypass the threshold.

Choosing a threshold

The threshold is a trade-off between security and convenience. Higher thresholds are harder to abuse but also harder to operate — if too many owners lose access, funds can be stuck. Common setups:

  • 2 of 3 — a solid default for small teams: one lost key does not lock the wallet, one stolen key does not empty it.
  • 3 of 5 — common for DAOs and larger treasuries; tolerates two unavailable owners.
  • 2 of 2 — maximum mutual control, but a single lost key freezes the funds. Use with care.

How MyMultiSig implements it

MyMultiSig deploys a lightweight, open-source multisig contract on 15 EVM networks. Owners approve transactions by producing EIP-712 signatures — structured, human-readable messages signed with their own wallets. Signatures are collected offchain (no gas to approve), and once the threshold is met, any owner submits a single execution transaction. The contract verifies every signature onchain before anything moves.

Early-stage project: the contracts are open-source and available for review, but they have not been professionally audited. Use at your own risk, and try it on a testnet first.

Next steps

Ready to try it? Create a multisig in a few minutes, or import one you already deployed.