Skip to content
Regen Web3 Toolkit

Multisig Setup for Community Treasuries

Multisig Setup for Community Treasuries

Section titled “Multisig Setup for Community Treasuries”

How to secure community funds with distributed control

Why This Matters for Community Treasuries

Section titled “Why This Matters for Community Treasuries”

If your community holds any funds, from membership dues, grants, or program funding, at some point you will need to make decisions about that money. Who approves spending? What happens if a committee member leaves? What stops one person from taking everything?

These are not abstract questions. Every community fund that has ever been mismanaged failed to answer them clearly in advance. A multi-signature wallet, multisig, is a tool that builds these protections directly into how the money moves.

This article explains what a multisig is, how it works, what configuration makes sense for different communities, and how to set one up step by step.

What Is a Multisig?

Section titled “What Is a Multisig?”

A multi-signature wallet requires multiple people to approve a transaction before it can be executed. Instead of one person holding the keys to all the funds, a threshold of signers must agree before any money moves.

For example, a 3-of-5 multisig means that any 3 out of 5 designated signers must approve a transaction. If one signer is compromised, their phone is stolen, they act in bad faith, or they simply become unavailable, they cannot move funds alone. No single point of failure can take down the whole system.

This matters for communities for several reasons:

It eliminates single points of failure. One person losing their key, going offline, or acting maliciously does not compromise the funds.

It enables genuine distributed governance. Signers can be different community members, each representing different interests, a core team member, a general member, a representative from a local working group.

It creates accountability. Transactions require multiple approvals. Everyone can see what was proposed, who approved it, and when it happened. This is public record on the blockchain.

It survives personnel changes. When a signer leaves the community, you remove them from the multisig and add a new signer. The funds are never held hostage by a departing individual’s keys.

Key Concepts

Section titled “Key Concepts”

The Threshold

Section titled “The Threshold”

The threshold is the number of signatures required to execute a transaction. Common configurations:

  • 2-of-3: Any 2 of 3 signers can approve. Useful for small teams of 3 people. The risk: if you lose any two signers, you lose access to the funds.
  • 3-of-5: Any 3 of 5 signers can approve. A good default for most communities. It tolerates two signers being unavailable or compromised.
  • 4-of-7: For larger organizations. More distributed, more secure against collusion, but requires more coordination.

A useful rule: the threshold should be more than half the signers, but less than all of them. You want to be able to act without needing everyone. But you also want enough signers that no one or two people can override the community’s interests.

For most community treasuries, 3-of-5 is a sensible starting point.

The Signers

Section titled “The Signers”

The signers are the individuals who hold the keys, literally, the private keys to their wallets, that allow them to approve transactions. Choosing your signers carefully matters.

Consider:

  • Geographic spread: Signers in different locations are less likely to face the same disruptions, a power outage, a flood, an internet shutdown.
  • Role diversity: Include people with different relationships to the funds, core team members, general community members, perhaps an external advisor.
  • Technical capacity: Signers need to be able to use the wallet software. This is a real consideration, do not assume everyone is comfortable with blockchain tools.

You want identifiable humans as signers, not anonymous addresses. Communities benefit when signers are known and can be held accountable.

Timelock

Section titled “Timelock”

A timelock is a delay between when a transaction is proposed and when it executes. It allows other signers, and the broader community, to review large transactions and cancel them if something looks wrong.

For small, routine transactions, you might allow immediate execution. For large transactions, say, more than 10% of the total treasury, a 24-hour timelock gives people time to notice and respond if something is wrong.

Timelocks are not always available on all multisig setups. Gnosis Safe supports them. They are worth asking about when you are setting up.

Setting Up Step by Step

Section titled “Setting Up Step by Step”

Step 1: Choose Your Platform

Section titled “Step 1: Choose Your Platform”

Gnosis Safe is the most widely used multisig wallet. It works on Ethereum and related networks, is well-audited by security researchers, and has a straightforward interface. It is free to create and use.

Argent offers a mobile-focused experience with social recovery built in, a trusted guardian can help you recover access if you lose your keys.

Multis is more business-oriented, with integrations to banking.

For most regenerative communities, Gnosis Safe is the right starting point.

Step 2: Decide Your Configuration

Section titled “Step 2: Decide Your Configuration”

Before you touch the software, decide:

  • How many signers? Five to seven is a good range.
  • What is the threshold? More than half, less than all.
  • Who are the signers? Choose identifiable, trusted people.
  • What is the timelock policy? Immediate for small transactions, delayed for large ones.

Document these decisions somewhere the whole community can see. This is governance, not just technology.

Step 3: Create the Wallet

Section titled “Step 3: Create the Wallet”

On Gnosis Safe:

  1. Go to https://gnosis-safe.io
  2. Connect your wallet or create a new one
  3. Click “Create new Safe”
  4. Add the signer addresses and set the threshold
  5. Deploy the Safe to the blockchain

Each signer needs their own wallet. Keys are never shared. This is fundamental.

Step 4: Test Thoroughly

Section titled “Step 4: Test Thoroughly”

Before depositing real funds:

  • Send small test transactions
  • Verify every signer can propose and approve
  • Confirm the threshold enforcement works correctly
  • Document the process so that future signers can understand it

This is not optional. You need to know the system works before you trust it with real money.

Step 5: Fund Gradually

Section titled “Step 5: Fund Gradually”

Start small. Deposit a modest amount first, make a transaction, confirm everything works. Increase the balance over time as confidence builds.

Ongoing Operations

Section titled “Ongoing Operations”

Proposing a Transaction

Section titled “Proposing a Transaction”

Any signer can propose a transaction. A proposal includes:

  • The recipient address, the wallet that will receive the funds
  • The amount, how much to send
  • Any data, if interacting with a contract, the data field carries instructions

The Approval Process

Section titled “The Approval Process”
  1. A signer proposes the transaction
  2. Other signers review it and approve (by signing with their own keys)
  3. Once the threshold number of approvals is reached, the transaction executes

What the Community Should See

Section titled “What the Community Should See”

All transactions are permanently recorded on the blockchain. Anyone can look them up. Maintain off-chain records as well, a shared document explaining why each transaction was made. This builds trust and helps future signers understand the community’s priorities.

Security Best Practices

Section titled “Security Best Practices”

Key management: Each signer should use a hardware wallet, a physical device that stores keys offline, or at minimum a secure mobile wallet. Keys are never stored in plain text, never shared over email or chat, never kept on a shared computer.

Access control: There should be a clear process for adding and removing signers. When someone leaves, they are removed from the multisig. This requires a transaction, which itself needs the threshold number of approvals.

Operational security: Signers verify every transaction on their hardware wallet screen before approving. They do not approve transactions they do not understand. They use address books to avoid typos in recipient addresses.

Disaster recovery: If a signer loses access, there should be a documented process for recovery or replacement. This process should be known to at least a few people in the community.

Common Mistakes

Section titled “Common Mistakes”

Threshold set too low: A 2-of-3 multisig is vulnerable. If any two signers collude or become unavailable, the funds are at risk or inaccessible. Use 3-of-5 or higher for community treasuries.

All signers from the same group: If the entire multisig team works in the same office and talks to each other every day, the multisig adds less security. Include diverse signers, different roles, different locations, different relationships to the funds.

No timelock for large transactions: Without a delay, a compromised signer could approve a large transfer before anyone notices. Configure timelocks for transactions above a set threshold.

Not testing before trusting: Always test with small amounts first. Unexpected behavior in a multisig can mean losing access to all funds permanently.

Social Recovery as an Alternative

Section titled “Social Recovery as an Alternative”

Some wallets, Argent and SoulWallet are examples, offer social recovery instead of multisig. With social recovery, a designated guardian (a device, a trusted person, or both) can help you recover access to your wallet if you lose your keys.

Social recovery is simpler for individual wallets and offers more flexibility. For community treasuries, where multiple people should have ongoing, legitimate access, multisig remains the better choice. The two approaches address different problems.

Try This

Section titled “Try This”

Before setting up a multisig, map your community’s current financial decision-making:

  • Who currently decides how community funds are spent?
  • What process exists for approving a large expenditure?
  • What happens if the person who holds the money leaves or is unavailable?
  • How many people would you want to have a say in a major spending decision?

Write these answers down. Then compare them to what a multisig actually provides. If a multisig would meaningfully improve your current process, it is worth setting up. If your community is very small or your funds are minimal, a simpler solution might serve you better.

References

Section titled “References”