Symbiotic Restaking Deep-Dive
Permissionless collateral, immutable slashing, and how rstETH ties it all together
Symbiotic Modular Restaking Protocol 2026
Restaking Flow: Deposit -> rstETH -> AVS Allocation
Watch your ETH flow through Symbiotic's restaking pipeline. The canvas animation traces the path from deposit through vault minting to operator delegation and AVS reward distribution. Use the slider to adjust the deposit amount and see how yield scales.
ETH Amount vs AVS Yield Earned
Model how different ETH deposit amounts affect your annualized AVS reward earnings. Toggle between vault types to see how curator-managed and self-managed vaults differ in their yield delivery.
* Slash Scenario Simulator
Model how different slashing events affect different vault types. The simulator walks through how the slashing oracle fires, how the coverage pool absorbs impact, and what net loss the depositor bears. Select a fault type and vault configuration to see the full cascade.
Restaking Yield Breakdown by Collateral Type
Different collateral types generate different base yields, SYM emission rates, and AVS reward potential. Select a collateral type to see the stacked yield components and understand what drives returns for each asset class.
Operator Performance Comparison
Not all operators are equal. Compare delegated stake, network coverage, uptime, slash history, and net APY across Symbiotic's operator ecosystem. Operators with zero slash events and high uptime earn the right to charge higher commissions.
| Operator | Networks | Delegated Stake | Uptime | Slash Events | Fee | Net APY |
|---|
Note: APY figures are net of operator fees but before curator fees (if using a curator-managed vault). Slush events reflect confirmed slashing oracle firings, not pending disputes.
Symbiotic Vault Types: Self-Managed vs Curator-Managed
Symbiotic supports two vault operating models, each with different risk/reward tradeoff and operational requirements. Understanding these models is essential before depositing collateral.
The depositor controls all delegation decisions - which operators to whitelist, which networks to serve, and per-operator exposure caps. You are fully responsible for monitoring operator performance and reacting to slashing conditions.
A named curator makes delegation decisions on behalf of depositors in exchange for a fee - similar to a Morpho Blue allocator. Curators publish their risk framework on-chain so depositors can compare before depositing.
Network-Specific Restaking by Chain
Symbiotic's networks span multiple chains. Each chain has a distinct set of AVS networks consuming restaked security, with different risk profiles and reward structures. Understanding chain-level distribution helps you diversify across network failure modes.
Solana has the highest average APY due to a smaller vault ecosystem competing for a relatively large AVS reward pool. Ethereum has the deepest liquidity and most diversified network set, but also the highest competition among vault depositors.
Key Concepts: Understanding rstETH Mechanics
Unlike stETH, which accrues value through a continuously compounding staking rate, rstETH price is dynamic based on vault performance. When AVS rewards flow into the vault, rstETH price rises. When slashing events occur, rstETH price drops. The price is not predetermined - it emerges from net vault P&L. This makes rstETH more like a share token in a hedge fund than a simple interest-bearing token.
Once the slashing oracle fires, the collateral release is atomic and irreversible. There is no challenge period, no council vote, and no appeal. The oracle reads the network's on-chain state, validates the proof against the network's slashing condition logic, and triggers the collateral release. This design maximizes speed and minimizes human intervention - but it also means that networks with flawed slashing logic will burn collateral with no recourse.
When a depositor mints rstETH, the vault contract writes a delegation entry to the OperatorRegistry. The operator's total slashable exposure is the sum of all vault delegations routed to it. Each network that accepts that operator adds the operator's slashable exposure to its total consumed security. The routing is transparent - anyone can read the delegation graph on-chain to see exactly how much slashable exposure each operator has and which vaults/_networks are behind it.
The coverage pool accrues from network reward contributions (typically 0.5-2% of each reward distribution). It is shared across all vaults serving a given network. When a slash fires, the oracle draws from the coverage pool first, then from the vault's slashing reserve, then from direct depositor collateral. The coverage pool is replenished over subsequent epochs. In high-slashing periods, the coverage pool can be depleted faster than it accrues, leaving depositors more exposed in subsequent fault events.
- What is rstETH and how is it different from stETH?
- rstETH (restaked ETH) is a vault share token minted when a depositor locks collateral into a Symbiotic vault. Unlike stETH (which represents ETH deposited into Lido's validator pool), rstETH represents exposure to multiple networks simultaneously and is specific to each vault. The same depositor might hold rstETH-vault-A and rstETH-vault-B, each with different risk/reward profiles, and each slashing the underlying USDC or wstETH differently. The key distinction: stETH is an LST issued by a single staking protocol, while rstETH is a vault-share token whose value fluctuates based on the net performance of every network the vault delegates to.
- How does Symbiotic's slashing oracle work compared to EigenLayer's Security Council?
- EigenLayer uses subjective slashing: when an AVS reports a fault, the Security Council votes on whether to confirm the slash before any collateral burns. Symbiotic replaces this with an immutable slashing oracle embedded in the core contracts. When a Network's on-chain rules fire a slashing signal, the oracle validates the proof, determines the slashable amount from each affected vault's delegation graph, and triggers collateral release - all without any external veto. The tradeoff is that networks must write their slashing conditions carefully, because there is no protocol-layer undo button. A buggy slashing condition burns real collateral regardless of intent.
- Can I restake non-ETH assets on Symbiotic?
- Yes. Any ERC-20 can serve as vault collateral, including USDC, DAI, UNI, LDO, MKR, Curve LP tokens, Uniswap V3 NFT positions, and LSTs like wstETH or rETH. A vault's collateral type is defined at deployment, and networks that want to consume security from that vault must explicitly list it in their acceptable-collateral set. This permissionless collateral model is Symbiotic's core architectural bet: by removing the asset-whitelist gate, new networks can launch with their own token as slashable collateral. The risk is that non-ETH collateral may not have the same market depth or liquidation dynamics as ETH-denominated collateral.
- What is the restaking flow from deposit to reward?
- The flow is: (1) depositor selects a vault, approves the ERC-20 transfer, and deposits collateral; (2) the vault mints rstETH shares proportional to the deposited amount; (3) the vault's delegation logic routes the slashable exposure to one or more operators; (4) each operator opts into networks it wants to serve; (5) networks distribute rewards to vaults based on the amount of delegated stake serving them; (6) the vault splits rewards between rstETH holders (via rstETH price appreciation) and the operator (via commission). All steps except operator selection are automatic on-chain logic. The depositor never directly holds or manages the operators - the vault contract handles all routing.
- Who manages risk in Symbiotic's curator vault model?
- The curator does. In a delegated (curator-managed) vault, the curator sets the per-operator cap, the list of allowable networks, the expected reward APR, and the maximum slashable exposure. Depositors review these on-chain parameters - which are publicly readable - before depositing. Curators compete on risk framework quality: a better curator attracts more deposits because they generate higher risk-adjusted returns. Self-managed vaults shift all risk decisions to the individual depositor, who must actively monitor operator performance and network slashing conditions. The curator model is analogous to a Morpho Blue allocator: someone else makes the routing decisions for a fee.
- How is restaking yield broken down?
- Symbiotic restaking yield has three components: (1) base yield - the staking return on the underlying collateral (e.g., ETH staking APY if the vault holds wstETH, or a money-market rate if it holds USDC); (2) SYM emissions - protocol-incentive tokens distributed to early vault depositors during bootstrap periods; (3) AVS rewards - network payments for security services. A concrete example: $100K in a USDC vault at 5% base, SYM emissions at 2%, and AVS payments at 3% nets roughly 10% gross before the operator's 10% fee and a 2% expected slash reserve.
- How does the Slash Scenario Simulator work?
- The Slash Scenario Simulator models different fault types and vault configurations to show how slashing events cascade through Symbiotic's architecture. You select a fault type (oracle drift, bridge failure, sequencer outage, DA provider fault, or MEV resistance breach), choose a vault type (curator-managed or self-managed), and set the collateral amount and delegation concentration. The simulator outputs the initial slashable amount, the coverage pool offset, and the net loss to depositors. It also shows the time-to-slash - how quickly the oracle fires after the fault event - and how the coverage pool replenishes over subsequent epochs. Use it to understand your realistic downside under different network conditions.
- What determines how much collateral gets slashed in a single event?
- Three factors determine slash size: (1) the network's slashing percentage - how much of the delegated stake it burns per fault (typically 1-10%); (2) the vault's delegation ratio - how much of the total vault collateral is delegated to the offending operator; (3) the coverage pool's remaining balance - which offsets a portion of the slash before depositors feel it. A single operator fault in a large curator vault with a full coverage pool might result in 0.1% net depositor loss, while the same fault in a small self-managed vault with a depleted coverage pool could mean 5%+ net loss. Diversification across multiple operators and networks reduces concentration risk and smooths the slash impact across more participants.
- What is the difference between a coverage pool and a slashing reserve?
- The coverage pool is a shared buffer funded by a small percentage of network rewards - typically 0.5-2% of each reward distribution. It sits between the vault's delegated collateral and the final depositor loss, absorbing the first tranche of any slash. All vaults in a network contribute to the same coverage pool, so it's a communal shock absorber. A slashing reserve is an individual vault's own buffer, set aside from yield as insurance. Curator-managed vaults typically maintain a slashing reserve equal to 3-6 months of expected AVS reward revenue. Self-managed stakers must estimate their own reserve based on the networks they serve and their risk tolerance. The reserve is like the deductible in an insurance policy - it kicks in after the coverage pool is exhausted.
- Can a vault be slashed for multiple faults simultaneously?
- Yes. If an operator serves multiple networks and faults on two of them in the same epoch, each network fires its slashing signal independently. The oracle processes them sequentially, and the coverage pool offsets each slash separately, up to its remaining balance. If the coverage pool is exhausted mid-batch, subsequent slashes hit depositors directly. This is why diversification across operators and networks matters - a vault concentrated on a single operator serving a single network faces the highest multi-fault exposure. The Slash Scenario Simulator models concurrent fault scenarios to show how cascading slashes affect the coverage pool depletion curve and how much residual loss a depositor should expect under each scenario.
- How does Symbiotic handle slashing disputes?
- Symbiotic has no dispute resolution mechanism for slashing - by design. The slashing oracle is immutable and deterministic: given the same network state and fault evidence, it always produces the same slash decision. This is a philosophical departure from EigenLayer's Security Council, which can reverse or reduce slashing based on evidence and argumentation. If a network writes a buggy slashing condition, collateral will burn even if the fault was genuinely accidental. This is why due diligence on the networks you serve matters more on Symbiotic than on protocols with a human review layer. The community can mitigate buggy slashing conditions by withdrawing delegation from networks with problematic oracle logic, but the slash itself is final. Choose your networks as carefully as you choose your vault.
- What happens to rstETH when a vault is slashed?
- rstETH is a share token representing proportional ownership of the vault's remaining collateral. When a slash occurs, the vault's total collateral decreases, which means each rstETH share is backed by less underlying asset - the rstETH price drops, reflecting the net asset value decline. If the coverage pool absorbs part of the slash, the price drop is smaller. RstETH holders don't receive any additional minted tokens after a slash; instead, the value of their existing tokens decreases proportionally. This is analogous to an AMM pool's LP token after an impermanent loss event - the token price falls to reflect the new net asset value. After a major slash event, depositors who exit first (by redeeming rstETH before the price fully adjusts) can partially limit their losses. In practice, rstETH redemptions are processed sequentially and the price convergence happens within the same epoch.