Table · StrataPlanned

Restaking AVSs Ranked by Allocated Stake and Rewards

Which restaking services have the most slashable stake behind them, and which pay restakers?

Every EigenLayer AVS and Symbiotic network ranked by the stake it can slash, with operators, delegated stake, rewards paid and slashings.

ShareEmail itvoltfincrypto.com/apps/restaking-avs-ranking
Blueprint

What the table will hold.

The table as it will open in Strata. Each figure is named here and arrives with its receipt; until its data is published, its place stays empty.

One row One row per restaking service, an EigenLayer AVS or a Symbiotic network, on the latest complete daySorted by Slashable stake, highest first

ServiceProtocolCategoryOperatorsSlashable stakeETHDelegated stakeETHMain assetRewards, 30 daysUSDReward tokensSlashingsRegisteredReceipt
Service service Text
The AVS or network's name, linked to its registration on-chain.
Protocol protocol Text
EigenLayer or Symbiotic, the restaking protocol it registered on.
Category category Text
What it does: data availability, oracle, bridge, sequencing, coprocessor or other, from its own documentation.
Operators operators Number
Operators with stake allocated to it or opted in to it at the latest block.
Slashable stake slashable_stake Exact amount
Stake operators have allocated to it, which it can slash, valued in ETH at the day's last block.
Delegated stake delegated_stake Exact amount
All stake delegated to its operators, including the part it cannot slash.
Main asset main_asset Text
The asset making up the largest part of its slashable stake: native ETH, a liquid staking token, EIGEN or another.
Rewards, 30 days rewards_30d Exact amount
Rewards it submitted on-chain over the last 30 days, valued on the day of each submission.
Reward tokens reward_tokens Text
The tokens it pays rewards in.
Slashings slashings Number
Executed slashing events it requested since slashing went live on its protocol.
Registered registered Date
The day it first registered an operator set or a network.
Receipt receipt Link
The block, contracts and reads behind the row.

Filter by Protocol, Category.

About

What it answers, and for whom.

Restaking services, called AVSs on EigenLayer and networks on Symbiotic, borrow security from staked assets: operators run their software and accept that the stake behind them can be slashed if they break its rules. This table ranks every service by the stake it can actually slash, beside the stake merely delegated to its operators and the rewards it pays.

The difference matters. Since EigenLayer's slashing upgrade, an operator allocates a part of its stake to each operator set it joins, and only that part is at risk for that service. Totals that count all the stake delegated to a service's operators overstate the security behind it. Rewards are read from the submissions services make on-chain, so a service that pays nothing shows nothing.

Sort by slashable stake to see which services carry real security and by rewards to see which pay restakers. Filter by protocol to compare like with like. Every row names its block and the reads behind it.

Method

How it will be measured.

Every figure will be read at a block, kept with its source and its exact read, and open a receipt anyone can re-check.

How receipts work →
  1. On EigenLayer, slashable stake is the part of each operator's delegated stake allocated to the service's operator sets, from the allocation manager's magnitudes at the day's last block.
  2. On Symbiotic, it is the stake each vault's delegator assigns to the network and its operators, read from the vault and delegator contracts at the same block.
  3. Rewards are the amounts in submissions to EigenLayer's rewards coordinator and in Symbiotic reward distributions, valued at oracle prices on the day of submission.
  4. Slashing counts only executed slashes: OperatorSlashed events on EigenLayer and executed slashes from Symbiotic slashers.
  5. Categories come from each service's own documentation and are recorded with their source.

The data it needs

Chain data, with some off-chain sources

  • restaking_dailyTo buildRestaking depositsAssets restaked per restaking protocol, strategy and operator per day, and what is delegated to each service.
  • native_prices_dailyTo buildOracle prices by dayReference prices of major assets read from on-chain oracle feeds (Chainlink latestRoundData) at each day's last block, with each round's update time.
  • lst_rates_dailyTo buildLiquid staking ratesExchange rates of liquid staking and restaking tokens (wstETH, rETH, cbETH, weETH and others) at day end, and the realized yield they imply.
  • address_labelsTo buildAddress labelsLabels for known addresses: exchanges, bridges, protocols, funds, treasuries, sanctioned addresses and known attackers.
  • EigenLayer allocation manager: operator sets, allocations, magnitudes and OperatorSlashed events
  • EigenLayer delegation manager operator shares at day-end blocks
  • EigenLayer rewards coordinator: AVS rewards submissions with token, amount and duration
  • Symbiotic network and operator registries, opt-in services and vault delegator stakes per network
  • Symbiotic slasher and veto slasher events with its reward distribution contracts
  • Each service's documentation for its name and category, recorded with source
Questions

Questions people ask.

What is an AVS?

An actively validated service: a system such as a data availability layer, an oracle or a bridge that uses restaked assets as security. Operators run its software, and it can slash the stake they allocated to it if they break its rules.

What is the difference between delegated and slashable stake?

Delegated stake is everything restakers have delegated to an operator. Slashable stake is the part the operator has allocated to a particular service, the only part that service can slash. A service's real security is its slashable stake.

Do AVSs pay rewards?

Some do, by submitting token rewards on-chain for operators and restakers; others pay nothing yet or rely on incentives from the restaking protocol itself. The table shows what each service submitted over the last 30 days and in which tokens.

How are Symbiotic networks different from EigenLayer AVSs?

Both buy security from restaked assets, but Symbiotic lets each vault choose its collateral, its delegation rules and a resolver that can veto slashing, while EigenLayer runs shared strategy contracts and operator sets. The table measures both on the same terms: stake that can be slashed and rewards paid.

Has any AVS slashed operators?

The table counts executed slashing events per service since slashing went live on each protocol. A count of zero means no slash was executed, not that none was requested; requests that were vetoed or never executed are not counted.

Operator set
A group an EigenLayer AVS defines for operators to join; stake allocated to it can be slashed only by that AVS.
Magnitude
The share of an operator's stake in one asset that it has allocated to a given operator set.
Network
Symbiotic's name for a service that buys security from vaults and their operators.
Resolver
On Symbiotic, a party a network names to review slashing requests and veto unjustified ones.

Build Restaking AVSs Ranked by Allocated Stake and Rewards on verified data.

Start free in Voltfin Studio: boards, tables and reports where every number opens its receipt. Tell us which data you need first and we will build it next.