---
title: "Safe (multisig treasury)"
url: "https://caper.network/wiki/dao-governance/tooling/treasury/safe"
updated: 2026-08-31
license: CC-BY-4.0
license_url: "https://creativecommons.org/licenses/by/4.0/"
---

# Safe (multisig treasury)

|  |  |
| --- | --- |
| **Category** | Treasury · custody |
| **Origin** | Gnosis Multisig (2017) → Gnosis Safe (2018) → rebranded **Safe** (2022) |
| **What it does** | _m_-of-_n_ smart-contract wallet: funds move only when a threshold of signers approves |
| **Scale** | The default DAO treasury; secures assets across 30+ EVM networks |
| **Extensible via** | Modules & guards — e.g. [Zodiac / SafeSnap](/wiki/dao-governance/tooling/frameworks/zodiac) for governance execution |
| **Site** | [safe.global](https://safe.global/) · [docs](https://docs.safe.global/) |
| **Related** | [SafeDAO](/wiki/daos/infrastructure/safe-dao), [Snapshot](/wiki/dao-governance/tooling/voting/snapshot), [What is a DAO?](/wiki/dao-governance/concepts/fundamentals/what-is-a-dao), [Exit rights](/wiki/dao-governance/concepts/membership/rage-quit-and-exit-rights), [Juicebox](/wiki/dao-governance/tooling/treasury/juicebox) |

**Safe** (formerly Gnosis Safe) is the smart-contract wallet that holds the money for most of the DAO world. It is a **multisignature** account: instead of one private key, a Safe is controlled by a set of signers and a threshold — an “_m_-of-_n_” rule such as 4-of-7 — so no single person can move funds, and a transaction executes only once enough signers approve it on-chain. First shipped as Gnosis Multisig in 2017, rewritten as Gnosis Safe in 2018 and [rebranded to Safe in 2022](https://safe.global/), it has become the base custody layer for [DAO](/wiki/dao-governance/concepts/fundamentals/what-is-a-dao) treasuries. ([Safe docs](https://docs.safe.global/)) On non-EVM chains the same custody role falls to dedicated multisig standards — on Solana, [Squads](/wiki/dao-governance/tooling/treasury/squads).

## How a Safe works

A Safe is deployed as its own contract account with an owner list and a confirmation threshold. To spend from the treasury, an owner proposes a transaction; other owners add their signatures; once the threshold is met the Safe contract executes it atomically. Ownership, threshold and the queued transactions are all on-chain and publicly inspectable, which is why a DAO can hold a nine-figure treasury in a Safe and have every member verify exactly who can authorize a spend. ([what is Safe](https://docs.safe.global/home/what-is-safe))

## Modules, guards and governance execution

Safe is deliberately minimal at its core and extended through **modules** (which can trigger transactions under custom rules) and **guards** (which add pre-execution checks). This is the seam where custody meets governance: [Zodiac](/wiki/dao-governance/tooling/frameworks/zodiac)'s SafeSnap module lets a passed [Snapshot](/wiki/dao-governance/tooling/voting/snapshot) vote execute against the Safe under an [optimistic challenge window](/wiki/dao-governance/concepts/voting/optimistic-governance), turning an off-chain signal into a binding treasury action without handing the keys to a single party. (UMA retired oSnap, the other module of this shape, on [15 December 2025](https://docs.uma.xyz/resources/osnap); treasuries that still have it installed should disable it.) Most DAO payments, streaming and analytics tools build directly on the Safe account model, and a further layer sells the workflow _above_ it — [Den](/wiki/dao-governance/tooling/treasury/den) adds notifications, decoded transactions and gas paid from the Safe without deploying any contract of its own. ([Safe modules](https://docs.safe.global/advanced/smart-account-modules))

## Why DAOs standardize on it

A treasury is a DAO's most valuable and most attacked asset, and Safe hit the pragmatic sweet spot: fully self-custodial and on-chain, but simpler and cheaper to run than a bespoke on-chain governor for a small or early organization. Its ubiquity is self-reinforcing — because nearly every treasury tool integrates Safe, new DAOs adopt it by default, and it secures a large share of all EVM DeFi value. ([Messari: Safe](https://messari.io/project/safe))

## Trade-offs

A multisig is a deliberate compromise. It buys speed, low cost and operational safety, but it concentrates power in the signer set: the treasury is only as decentralized as its _m_-of-_n_, and a colluding or compromised majority of signers is a real risk — which is why mature DAOs pair a Safe with on-chain governance (a Snapshot-plus-SafeSnap bridge or a full Governor) rather than letting a small council spend unchecked.

## How Caper approaches this

Caper folds custody into the protocol instead of bolting on a separate multisig. A caper's treasury is a contract-controlled vault governed directly by member [votes](/wiki/governance/voting) and [executed on-chain](/wiki/governance/execution), so there is no signer set to trust and no threshold to capture. It also adds a property a Safe does not have: members can [exit](/wiki/dao-governance/concepts/membership/rage-quit-and-exit-rights) and redeem a slice of that treasury sized by their canonical [vote weight](/wiki/governance/voting) `(t·v)/(V·T)` — not a pro-rata claim by balance, since the redemption consumes both the governance tokens and the soulbound vote tokens earned by trading or by voting — so custody and exit are governed by the same rules rather than by a council's discretion.

## References

- Safe, [Documentation](https://docs.safe.global/) and [safe.global](https://safe.global/).
- Safe, [Zodiac module collection](https://github.com/gnosisguild/zodiac) (Gnosis Guild).
- Messari, [Safe project profile](https://messari.io/project/safe).