Safe

What is Safe?

Safe is a smart-account and custody coordination standard for Ethereum and EVM chains, best known for the battle-tested multi-signature “Safe” contract system and the surrounding infrastructure that lets multiple parties, policies, and modules jointly control assets and onchain permissions without relying on a centralized custodian. In practice, it solves a recurring institutional problem in crypto: key management is not only a cryptographic issue but an operational one, where governance, approvals, spending limits, and recovery need to be enforceable at the account layer. Safe’s moat is less about novel cryptography than about standardization and composability: it has become a widely integrated onchain “ownership primitive” that applications and institutions can build around, and it has extended beyond multisig into modular smart accounts via its account-abstraction stack (often described publicly as Safe{Core}).

In market-position terms, Safe is not a base-layer network competing for blockspace, but a horizontal account layer that can accrue adoption across many chains and applications.

That distinction matters when investors try to map metrics like TVL: aggregators such as DeFiLlama currently show “TVL” effectively as zero under their strict definition (assets deposited into protocol contracts), even while Safe accounts may custody or intermediate very large balances and transaction volumes. A more informative lens is activity and “volume processed” on Safe accounts; for example, Messari’s State of Safe Q1 2025 describes record smart-account transactions and substantial DEX volumes routed by Safe-based accounts, while also highlighting how concentrated that activity can become when a single distribution channel (notably World/World Chain at that time) dominates new account creation and DAUs.

Who Founded Safe and When?

Safe originated as “Gnosis Safe,” emerging from the Gnosis ecosystem and gaining traction during the 2018–2021 period when DeFi and DAO treasuries created acute demand for auditable, multi-party custody.

Over time it was formalized into a distinct project with governance routed through a DAO and supported by a Swiss legal wrapper; the Safe Ecosystem Foundation imprint lists council members including Lukas Schor, Stefan George, and Richard Meissner, reflecting continuity with the original builder cohort while framing a more institutionally legible structure than an informal open-source team.

The project’s narrative evolution tracks a broader industry shift: multisig started as “safer custody for teams,” then became a programmable account surface for governance, modular security, and account abstraction. The September 2022 introduction of a governance token and DAO framework, covered by outlets such as CoinDesk and later analyzed in governance-launch retrospectives like Blockworks, signaled that Safe’s strategic center of gravity was moving from “product” to “ecosystem standard,” with token governance intended to coordinate upgrades, incentives, and treasury policy rather than to represent a claim on protocol cash flows.

How Does the Safe Network Work?

Safe is not a standalone blockchain and therefore has no native consensus mechanism; it inherits security, liveness, and finality from the host chain(s) where Safe smart accounts are deployed (Ethereum mainnet, L2s, and EVM sidechains). Technically, a Safe is a smart-contract account that validates transactions according to its configured policy (e.g., M-of-N signatures) and can be extended via modules/guards, allowing additional verification logic to be inserted at the account layer.

This “account-layer policy enforcement” is categorically different from network-layer consensus: it does not order transactions globally, but it can prevent unauthorized execution from a specific account even if an attacker can submit transactions to the mempool.

Safe’s recent architectural framing emphasizes modular account abstraction infrastructure, with the Safe{Core} direction explicitly positioned as interoperable smart accounts rather than a single wallet UX.

The security model is correspondingly split: the onchain contracts may be robust, but the system’s practical safety also depends on the integrity of signing workflows, hardware devices, and user interfaces that compose transactions for signing. A concrete illustration is the February 2025 Bybit incident discussed in Messari’s State of Safe Q1 2025, where reporting attributed a large theft to a targeted compromise of Safe’s web interface used by Bybit signers rather than an exploit of the Safe contracts themselves; third-party technical writeups such as Ledger’s postmortem-style note, Learning From The Bybit/Safe Attack, similarly frame it as an interface/integration failure mode that institutional users must explicitly threat-model.

What Are the Tokenomics of safe?

SAFE is primarily a governance token for SafeDAO rather than a gas token, and its supply design is best understood as a long-duration unlock schedule with a large treasury allocation rather than an algorithmic emission system tied to network security.

The Safe Foundation’s own explainer, SAFE Tokenomics, describes a fixed maximum supply of 1,000,000,000 tokens and a distribution that heavily favors DAO treasuries (SafeDAO and GnosisDAO) with multi-year vesting, alongside allocations to users, ecosystem “guardians,” core contributors, a strategic raise, and the foundation. Because vesting spans multiple years, SAFE’s circulating supply is structurally time-variant; third-party trackers like Tokenomics.com’s unlock page quantify this as a multi-year sequence of unlock events extending to 2030, implying that dilution dynamics (and the identity of recipients of newly unlocked supply) can matter as much as “demand growth” in any given period.

Utility and value accrual remain the central open question for SAFE as an asset. DeFiLlama’s protocol page for Safe attributes protocol fees/revenue largely to swap-related flows (e.g., via integrated trading paths), while also showing “holder revenue” as effectively zero, underscoring that tokenholders should not assume a direct fee claim is either implemented or inevitable.

In that framing, SAFE resembles many governance tokens: it can coordinate treasury spending, grants, and protocol direction, but whether it becomes “network-essential” depends on future governance decisions and credible mechanisms that link adoption of Safe accounts (which can grow rapidly) to token demand (which does not automatically follow).

Who Is Using Safe?

Safe’s onchain footprint is best characterized as infrastructure usage rather than speculative turnover: it is embedded in treasury operations, custody workflows, and application accounts where policy-based control is a functional requirement.

That said, usage is not evenly distributed across segments; Messari’s State of Safe Q1 2025 describes a period in which Safe smart-account activity and DAUs were highly concentrated on World Chain, and where DEX volume routed through Safe accounts spiked sharply on specific L2s. This matters because “real usage” can still be pro-cyclical and partner-driven: a large integrator can create millions of accounts, but that does not automatically imply comparable decentralization of demand across independent applications.

Institutional and enterprise adoption is one of Safe’s more credible differentiators, but it should be discussed precisely: the strongest evidence is not brand-name anecdotes but the persistence of Safe as a default multisig standard for teams managing high-value assets and for applications needing programmable custody. At the same time, the Bybit event highlighted in State of Safe Q1 2025 and further dissected by security vendors and integrators, including Ledger, demonstrates that “enterprise use” can amplify systemic risk if many institutions converge on the same interface and operational patterns. In other words, adoption can be both a moat and a correlated-risk vector.

What Are the Risks and Challenges for Safe?

From a regulatory perspective, Safe’s risk profile is typically more muted than that of L1 tokens because it is not selling blockspace and does not sit at the center of market-structure debates about exchange intermediation; however, SAFE is still a governance token with a large treasury and identifiable development stakeholders, and it operates in an environment where the boundary between “software coordination” and “financial product” can be contested depending on jurisdiction and future token utility.

The more immediate “regulatory” exposure may be indirect: custody failures, sanctions compliance expectations for institutions, and potential scrutiny after high-profile incidents, even when root causes are integration-layer compromises rather than onchain contract flaws.

Operational and technical centralization risks are more concrete.

The Bybit case shows a category of failure where the smart contracts can remain uncompromised while the signing environment is manipulated via a compromised web application supply chain; analyses such as Curvegrid’s breakdown emphasize the “single point of failure” created when a large institution relies on a shared hosted UI for transaction construction and display. Competition is also intensifying: alternative multisig frameworks, exchange and custodian internal MPC stacks, and newer account-abstraction ecosystems can all erode Safe’s mindshare if they offer comparable security with better policy tooling, better UX, or tighter enterprise controls.

Finally, because Safe is a standard, it must balance backward compatibility and ossification against the need to evolve with account abstraction, L2 fragmentation, and new threat models; standards that move too slowly risk being routed around.

What Is the Future Outlook for Safe?

Safe’s near- to mid-term outlook hinges on whether it can translate its position as a de facto smart-account standard into a sustainable platform with resilient interfaces, diversified integrator demand, and clearer token-aligned incentives.

The project’s own ecosystem communications, such as the Safe forum post 2025 Reflections and 2026 Outlook, emphasize operational maturity goals like efficiency, internalization of key capabilities, and revenue discipline, which is consistent with an infrastructure provider trying to be durable rather than growth-at-all-costs.

On the technical side, the direction implied by Safe{Core} protocol framing suggests continued modularization around account abstraction, which is strategically sensible as Ethereum’s roadmap and wallet ecosystem increasingly treat smart accounts as a core UX and security primitive.

The structural hurdles are equally clear: Safe must reduce reliance on any single hosted interface for high-stakes signing, harden the end-to-end transaction review surface for institutional operators, and avoid an ecosystem where adoption is dominated by one distribution partner whose activity patterns can swing aggregate metrics.

For SAFE the token, the key question is whether governance remains its primary function indefinitely or whether the ecosystem converges on additional, explicitly defined utilities that create non-speculative demand; until such mechanisms are both specified and adopted, SAFE’s investment case is likely to remain more about governance optionality and ecosystem coordination than about cash-flow-like value capture.