This entry summarizes Safe’s current smart-account documentation. It is not a single 2018 whitepaper: the source is living technical documentation, which does not name individual authors or state a document-specific license. The LGPL-3.0 notice on the Safe smart-account code repository applies to that code repository; it does not by itself establish a license for every documentation page. Safe’s foundation announced the transition from the Gnosis Safe name to Safe on July 12, 2022.
| Protocol documentation | Documentation |
|---|---|
| Directories | Ethereum Whitepapers & Research |
What a Safe account is
A Safe is a smart-contract account configured with owners and a signature threshold. For a standard Safe transaction, the required number of owners must confirm the transaction before it can execute. For example, a 3-of-5 Safe has five owners and requires any three confirmations. Current docs say owners can be externally owned accounts, other smart accounts, or passkeys. A Safe is therefore a programmable account with a policy, not simply a wallet application or a single private key.
A Safe address is a proxy that delegates calls to a shared implementation contract. The Safe account contract and the hosted Safe{Wallet} interface are different parts of the system: the interface helps users build, review, and submit transactions, while the on-chain account enforces the configured owner and execution rules. The interface can be important for usability, but it is not the owner threshold itself.
Modules, guards, and fallback handlers
A basic Safe does not need modules. Owners can approve a module through the configured threshold; once enabled, a module may use an alternative execution path, including some transactions that do not collect the standard owner signatures. This can support recovery, limited spending, automation, or account-abstraction integrations, but it also expands the trust boundary. A module with unsafe logic may gain powerful authority over the account.
A Guard can check a standard Safe transaction before and after execution. It can reject a transaction, which can enforce a policy but can also block the account if the Guard is faulty or malicious. The Safe Guard tutorial distinguishes owner-approved Safe transactions from module transactions: a standard Guard does not automatically inspect every module transaction. Module Guards are a separate configuration. Users should confirm which transaction paths are covered before relying on a Guard as a complete policy.
A fallback handler can extend a Safe with additional function behavior. For example, a compatibility handler can implement ERC-1271 message-signature checks, and a Safe4337Module can connect a Safe to ERC-4337 user operations. These handlers are optional; they are not all active on every Safe. Because a handler can execute additional logic in the account’s context, its provenance and permissions matter.
Safe and account abstraction
Safe’s multisig threshold is one possible authorization policy for a smart account. Account abstraction describes a broader set of ways to validate and execute account operations. Safe’s documentation lists a 4337 module among its integrations, so a Safe may participate in an ERC-4337 flow when the relevant module and infrastructure are configured. That does not mean every Safe automatically uses ERC-4337, supports every passkey, or can sponsor gas on every network. Features depend on the particular deployment, modules, services, and chain.
Security and operational trade-offs
A threshold reduces dependence on one signing key, but it does not make an account impossible to compromise. An attacker who controls enough owners can meet the threshold; a mistaken threshold or poorly managed owners can create recovery and availability problems. Modules, Guards, fallback handlers, and delegatecall add logic that owners must understand. A broken Guard can prevent transactions, and an unsafe module can take an alternate route around the expected signature flow.
Before depositing funds, owners should check the deployed account and version, owner list and threshold, enabled modules, Guards and module Guards, fallback handler, and the exact transaction shown by each signer. Recovery plans should be tested before an emergency. A Safe deployment or a hosted interface should not be described as universally safe based on an audit, TVL figure, or past incident record alone.
Related Terms
See Also
- ERC-4337: Account Abstraction Using Alt Mempool
- EIP-7702: Persistent EOA Delegation and Authorization Rules
- Biconomy: Nexus, Smart Sessions and MEE Documentation
Social Media Sentiment
An October 2025 r/ethereum thread raised concerns about a prompt to accept new terms in the hosted Safe{Wallet} interface and whether the user could keep using the older interface. Other replies distinguished the hosted client from the on-chain account and said the contracts could still be accessed through other tools. This was a small, polarized discussion about interface continuity; it does not verify that the account’s funds were inaccessible on-chain or represent broad Safe-user sentiment.
Last updated: 2026-10
Sources
- How do Safe Smart Accounts work?: Official explanation of threshold owners, proxies, modules, Guards, fallback handlers, and account features.
- Building a Guard for Safe Smart Account: Describes transaction checks, the distinction between Safe and module transactions, and the risks of a blocking Guard.
- Safe Fallback Handler: Explains optional fallback behavior and examples such as ERC-1271 and Safe4337Module.
- Safe announces its rebrand from Gnosis Safe: Official July 12, 2022 announcement of the transition to the Safe name.
- Safe smart-account source-code license: Repository license file; cited to distinguish code licensing from the documentation license.
- Safe{Wallet} multisig removes support for old interface, with no warning – r/ethereum: One October 2025 user report about the hosted interface, used only as a limited sentiment sample.
Last updated: 2026-10-11