Safe (SAFE)
System: Safe — Coordination and Governance
Safe provides smart accounts for secure self-custody, on-chain treasury management, multi-party approvals and organisational transaction execution. Safe launched as Gnosis Safe in 2018 and uses Ethereum Virtual Machine (EVM) smart-account contracts, Safe{Wallet} web and mobile interfaces, and Safenet Beta validator components. Inside the system boundary are Safe Smart Account contracts, account modules and guards, Safe{Wallet} where it is material to product access, Safe Labs, Safe Ecosystem Foundation and Safenet Beta components. Underlying EVM chains, independent third-party applications, assets merely held inside user Safe accounts and external protocols such as CoW Protocol, LiFi and Gnosis are excluded except where a Safe-specific routing or treasury component brings them into scope.
Market Data
| Price | $0.084245 |
| Market Cap | $64.65M |
| Fully Diluted Valuation | $84.24M |
| 30d Change | 3.70% |
| 365d Change | -80.80% |
Token Functionalities
Governance
- Process and Meta Parameter Control (Partial)
Right to vote or delegate SAFE on SafeDAO's constitutional and governance framework rules. This functionality is Partial because governance changes use recognised SafeDAO voting processes, but the full execution path is not evidenced as automatic or wholly non-discretionary across all affected components.
- Actor Set Permissioning (Partial)
Right to vote or delegate SAFE on the appointment, mandate or termination of certain SafeDAO treasury or service-provider actors. This functionality is Partial and narrow in scope. It does not cover Safenet Beta validator admission, which is controlled by the Safe Ecosystem Foundation during the Beta phase.
- Economic Design/Parameter Control (Partial)
Right to vote or delegate SAFE on economic-design decisions that affect SafeDAO monetary flows, including Native Swaps revenue acceptance, fee-routing treatment and Safenet Beta reward funding. This functionality is Partial because approved decisions may still require Safe Ecosystem Foundation, legal-wrapper, treasury or implementation execution.
- Treasury Control (Partial)
Right to vote or delegate SAFE to direct SafeDAO treasury and resource allocation, including funding for SafeDAO programmes such as Safenet Beta and relevant treasury mandates. This functionality is Partial because treasury execution may require signers, Safe Ecosystem Foundation, legal-wrapper steps, service providers or joint-treasury actors.
Service Provision
- Distributed Oracle Service
Right to emit transaction-safety attestations that Safe guard contracts treat as execution-relevant truth, after being admitted as a Safenet Beta validator and meeting the SAFE self-stake requirement. Delegated SAFE is not included in this classification because delegators do not perform the validator attestation service, either directly or by proxy.
Value Distribution
- Direct Entitlement (Discretionary but Regular)
Right to claim a share of the Safenet Beta reward pool by staking and delegating SAFE to a Safenet validator. This functionality is Discretionary but Regular. Delegators do not operate validator infrastructure, do not join the permissioned validator set and are not exposed to slashing in Beta.
System Attributes
Operating Model
<p>Safe has a Hybrid Operating Model. The on-chain side is the Safe Smart Account contract system, where owner lists, signature verification, transaction thresholds, modules and guards enforce account-level control. The off-chain side is material because Safe{Wallet} is a Safe Labs-operated web and mobile access channel, Safe Ecosystem Foundation executes foundation and treasury-related roles, and Safenet Beta uses a permissioned validator-selection process. Core account execution is not dependent on a custodial database, but product access, fee-setting, legal-wrapper routing and Safenet Beta administration include identifiable off-chain entities.</p>
Value Creation
<p>Safe has Hybrid Value Creation. On-chain value is created by Safe Smart Account contracts that verify account owners, enforce signature thresholds, execute transactions, and support modules and guards for account-specific logic. This is the core productive activity for shared custody, treasury execution and account-based access control. Off-chain value is created through Safe{Wallet} interfaces, transaction-building flows, Safe Shield security surfaces, Safe Labs product work, Safe Ecosystem Foundation coordination and Safenet Beta validator checks. Safenet Beta adds a hybrid security layer: validators assess transactions, and Safe guard contracts use their attestations before execution. The product value, therefore, comes from both contract-enforced account control and entity-operated interfaces, coordination and validator services.</p>
Value Capture
<p>Safe has Hybrid Value Capture and Routing. User assets held in Safe accounts are not Safe revenue; they remain controlled by the account owners. The clearest live value-capture path is Safe{Wallet} Native Swaps, where swap users pay widget fees through CoW Swap or LiFi and a portion is distributed to Safe Foundation. Under the Native Swaps revenue proposal, fees may be converted into SAFE and routed through the Safe Ecosystem Foundation or a subsidiary legal wrapper into a SafeDAO-designated treasury account. Safenet Beta also routes value from the SafeDAO treasury to Safe Ecosystem Foundation, validators, delegators and request-for-proposal recipients. On-chain transfers and claim paths exist, but final routing depends materially on Safe Labs, Safe Ecosystem Foundation, legal-wrapper execution and SafeDAO treasury decisions.</p>
Governance
Token-Based: <p>Token-Based Governance applies to specific SafeDAO components: treasury and resource allocation, constitutional and governance-framework changes, Native Swaps revenue acceptance, Safenet Beta funding and certain treasury or service-provider mandates. SAFE holders and delegates vote through recognised SafeDAO processes over those components. Execution may involve Safe Ecosystem Foundation, subsidiary legal wrappers, treasury signers, service providers, GnosisDAO in joint-treasury matters or other implementation paths.</p> Participant-Based: <p>Participant-Based Governance applies at the individual Safe account and role-gated execution layers. Each Safe account is controlled by its configured owners and threshold: owners approve transactions, change the owner set, change the threshold and enable or disable modules and guards. Enabled modules can execute account-level logic only because the account owners authorised them. Safenet Beta transaction attestations are also participant-based execution: admitted validators perform the transaction-checking role and produce attestations that Safe guard contracts consume. These powers depend on account-owner status or validator role, not merely on holding SAFE.</p> Entity-Based: <p>Entity-Based Governance applies to specific off-chain components, not to the whole system. Safe Labs controls the Safe{Wallet} interface and may change its own Safe{Wallet} fees. Safe Ecosystem Foundation or a subsidiary can act as the legal wrapper for Native Swaps revenue before it reaches a SafeDAO-designated treasury account. Safe Ecosystem Foundation also controls material Safenet Beta components, including permissioned validator admission, reward-distribution administration, request-for-proposal execution and compliance checks. These entity-controlled components can affect product access, monetary flows, actor admission and reward execution.</p>