🔗 Symbiotic Restaking
Symbiotic is a permissionless restaking protocol with a modular architecture. Unlike EigenLayer's ETH-centric approach, Symbiotic lets any ERC-20 token serve as restaking collateral. Its design cleanly separates three layers — vaults (collateral), operators (infrastructure), and networks (services) — enabling maximum flexibility for all participants.
Restaking Model
How Symbiotic's permissionless, modular restaking differs from EigenLayer — any ERC-20 as collateral
Vaults
Multi-asset vault mechanics — delegated vs self-managed, risk/reward tradeoffs, and collateral configuration
Networks & Operators
How networks (AVSs) connect to operators and vaults in Symbiotic's three-layer architecture
The Three-Layer Architecture
Vaults hold collateral and delegate it to operators. Operators run infrastructure and validate for networks. Networks consume security and define slashing conditions. Each layer is independently configurable — no monolithic coupling.
Related Topics
How Symbiotic works in 90 seconds
Symbiotic is a restaking substrate built around three independent contract layers — Vaults for collateral, Operators for infrastructure, and Networks for consuming services — and a small set of immutable core contracts that wire them together. A depositor picks a Vault whose collateral token and risk parameters match their preference, transfers the asset in, and receives a vault share. Because the Vault contract treats the collateral as a generic ERC-20, the same architecture accepts stablecoins, governance tokens, LP positions, or LSTs without requiring protocol governance to whitelist each one.
The Vault's delegation logic decides which Operators can draw security from it. A self-managed vault lets the depositor set operator allowlists directly; a curator-managed vault delegates that decision to a named third party whose on-chain configuration — per-operator caps, permitted networks, minimum reward thresholds — is visible to depositors before they lock funds. Operators register once in the OperatorRegistry and then explicitly opt into each Network through that Network's registration call, so an Operator's slashable exposure is the union of every Network it has signed into, not every Vault that happens to delegate to it.
Networks define their own slashing criteria in the Network contract. When a Network's on-chain rules determine that an Operator faulted, the slash propagates through the Vault's delegation graph and burns collateral directly — there is no protocol-wide veto committee between the network judgment and the asset burn. Rewards move along the same edges in the opposite direction: a Network funds its reward pool, the pool distributes to Vaults weighted by delegation, and each Vault splits payouts between depositors and the Operator's commission.
Key concepts
- Permissionless collateral
- Any ERC-20 can collateralize a Symbiotic vault. That includes stablecoins (USDC, DAI, crvUSD), governance tokens (UNI, LDO, MKR), LP positions, LSTs, and RWA-backed tokens. Networks choose which collateral types they will accept, which lets a new app-specific network bootstrap on its own token without needing the protocol to grant approval for the asset.
- Vault
- A vault is a single-collateral contract that accepts deposits, mints shares, and routes slashable exposure to Operators. Each vault publishes its delegation logic, reward-distribution rules, slashing caps per operator, and the Networks it opts into. Vaults are the only place where collateral physically sits, which keeps the operator and network layers light and purely behavioral.
- Operator
- An Operator is any entity that registers in the OperatorRegistry, runs the Network's off-chain software, and accepts slashing risk in exchange for fees. Operators opt into Networks one at a time, and the Networks they have signed into define the full set of slashable conditions that can hit collateral delegated to that operator — there is no implicit opt-in.
- Network
- A Network is a service that consumes restaked security: an oracle committee, a decentralized sequencer, a bridge validator set, a data-availability provider, a cross-chain messaging network, or any other off-chain workload. The Network contract encodes the slashing conditions, the reward schedule, and the list of Vaults the Network is willing to pull security from.
- Delegated vs self-managed vaults
- Self-managed vaults expose operator allowlists and risk caps directly to the depositor. Delegated vaults hand those decisions to a curator who earns a fee for portfolio construction — similar in spirit to Morpho Blue allocators. Curators compete on explicit on-chain parameters: concentration limits, permitted networks, expected reward APR, and slashing-loss tolerance.
- Slashing without a protocol veto
- Symbiotic's core contracts are immutable and do not interpose a Security Council. When a Network's on-chain slashing rule fires, the Vault releases the configured slashable amount immediately. Networks therefore bear the full responsibility for their slashing logic — a badly specified condition can burn real collateral without any protocol layer available to reverse it.
Why Symbiotic matters
Symbiotic unbundles restaking. Where EigenLayer bakes ETH, operator, and AVS layers into one integrated product, Symbiotic ships a minimal set of immutable primitives and lets Vault curators compose their own product on top. The practical consequence is that any new Network — a Layer-2 sequencer, a yield-bearing stablecoin's oracle, a cross-chain bridge — can launch with its own token as slashable collateral instead of renting ETH security, while still sourcing a secondary tranche of ETH-denominated exposure from wstETH-collateralized vaults if it wants diversification.
As of April 2026, Symbiotic is the home venue for restaked stablecoin security (oracle committees collateralized in USDC), for LP-collateralized validator sets on app-rollups, and for curator-managed vaults that competed with EigenLayer-backed liquid restaking tokens throughout 2025. A representative numeric example from the protocol's own documentation: $100K of collateral into a curator vault, 8% gross network reward, 10% operator fee, 5% expected slash loss, and 2.2% risk-adjusted return after fees — the exact same vault architecture can be re-pointed at different Network sets to push that number up or down.
Frequently asked questions
- What makes Symbiotic's collateral set permissionless?
- Symbiotic's vault contracts accept any ERC-20 as restaked collateral — not just ETH or ETH-denominated LSTs. Stablecoins like USDC, governance tokens like UNI or LDO, LP tokens from Curve or Uniswap V3, and protocol treasury assets can all serve as slashable backing. Each vault explicitly lists the collateral token it holds, and networks choose which vaults they will accept when they define their slashing criteria.
- How do Symbiotic's three layers interact?
- Vaults hold collateral and set delegation rules. Operators run infrastructure and register with the OperatorRegistry. Networks define the services consuming security and their slashing conditions. A typical flow: a depositor locks stablecoins into a curator-managed vault, the vault delegates that exposure to two operators, each operator opts into three networks, and rewards and slashings travel bidirectionally across the same vault–operator–network edges.
- Who actually decides when to slash on Symbiotic?
- Each network owns its slashing logic. The network contract defines what counts as a fault, which operators are in scope, and how much of the delegated stake to burn. There is no protocol-wide veto committee — if a network's on-chain rules fire, the vault releases slashable collateral directly. This is the sharpest philosophical divergence from EigenLayer, which interposes the Security Council's veto window before any burn executes.
- What kinds of networks are using Symbiotic?
- As of April 2026, Symbiotic's network set includes oracle committees that settle price attestations, decentralized sequencers for app-specific rollups, cross-chain bridge validator sets, data-availability providers, and MEV-resistance networks that police block-building. Because any ERC-20 can be posted as collateral, networks denominated in their own token can launch with native economic alignment rather than paying for ETH security.
- How do delegated versus self-managed vaults differ?
- A self-managed vault gives the depositor full control — they pick which operators to delegate to and which networks those operators serve. A delegated (curator-managed) vault hands those decisions to a named curator who is compensated via a fee, similar to a Morpho Blue allocator. Curators compete on risk framework quality: caps per operator, allowable networks, target reward APR, and slashing-loss tolerances are all on-chain parameters depositors can inspect before they deposit.
- How are Symbiotic's rewards actually paid?
- Networks distribute rewards to the vaults they pull security from, and vaults split those flows among operators and depositors per their configuration. A typical example from Symbiotic's documentation: $100,000 collateral, 8% gross network reward, 10% operator fee, and a 5% expected slash loss nets depositors roughly a 2.2% risk-adjusted return — numbers that vary sharply by collateral type and by which networks the vault has opted into.
- Does Symbiotic or EigenLayer win for a given use case?
- EigenLayer is the deeper pool when a service specifically needs ETH-denominated slashable security and can accept the opinionated operator/AVSDirectory model. Symbiotic wins when a network wants its own token (or stablecoins, or LP tokens) to be the slashable unit, wants vault-level diversification across collateral types, or wants slashing logic with no protocol-layer veto. Many AVSs run on both to diversify where their security comes from.