Safe

• Safe, formerly Gnosis Safe, is the dominant smart contract wallet standard for multi-signature custody.

• It secures a very large share of DAO treasuries and institutional on-chain holdings.

• SAFE is the governance token of SafeDAO.

• Supply allocated across community, ecosystem and contributors.

• Governance over protocol direction; the token does not capture wallet fees.

Pros:

• The default standard for on-chain treasury custody, with enormous assets secured.

• Modular design allows custom transaction policies and recovery mechanisms.

• Long operating history with extensive audit coverage.

Cons:

• In February 2025 the Bybit exchange lost approximately $1.5 billion when attackers compromised a Safe developer's machine and served a malicious interface to the signers. The smart contracts themselves were not exploited, but the incident showed that the surrounding infrastructure is part of the attack surface.

• The token has no claim on the value the protocol secures.

• Competition from newer smart account standards built on ERC-4337.

• Exposure to the dominant on-chain custody standard by assets secured.

• Track record and audit coverage are substantial.

• The Bybit incident is essential context: contract security and interface security are different things.

• The default multi-signature standard for on-chain treasuries, securing a larger share of DAO and institutional assets than any alternative.

• A single private key controlling a treasury is a single point of catastrophic failure.

• Requiring multiple signatures distributes that risk across parties, provided the interface they sign through is trustworthy.

• Originated within Gnosis, founded by Martin Köppelmann and Stefan George, later spun out as an independent entity.

• Governed by SafeDAO with core development by Safe Ecosystem Foundation.

• No public ICO. SAFE was distributed via airdrop to users and ecosystem participants in 2022.

• The Bybit incident demonstrated that interface and developer infrastructure compromise can defeat correct contracts.

• Token captures no fees from the assets the protocol secures.

• Competition from ERC-4337 smart account implementations.

• Signer key management remains the user's responsibility and a frequent failure point.