EigenLayer AVS

Actively Validated Services (AVSes) are the reason EigenLayer exists. EigenLayer itself is the middleware layer that aggregates restaked ETH; AVSes are the services that consume that security. An AVS is any decentralized network, oracle, bridge, DA layer, or computation service that registers with EigenLayer, defines its slashing conditions, and pays operators for validation work. The AVS model transforms EigenLayer into a security marketplace — new protocols no longer need to bootstrap validators or token economies; they can rent cryptoeconomic guarantees from Ethereum’s $30B+ validator set.


How AVSes Work

The following sections cover this in detail.

The Core Mechanism

When an Ethereum validator (or solo staker) restakes via EigenLayer:

  1. Opt in to AVS: Validator (called an “operator”) chooses which AVSes to validate
  2. Accept slashing conditions: The AVS defines what actions constitute a slashable offense (e.g., signing contradictory data, downtime above threshold)
  3. Perform validation tasks: Operator runs the AVS client software (separate node from Ethereum validator)
  4. Earn fees: AVS pays operators from its protocol token or revenue
  5. Risk slashing: If operator misbehaves, ETH collateral can be slashed — not just the restaking-native token

Key insight: The slashing risk is real ETH (or LST). This is what distinguishes EigenLayer security from a normal protocol’s staked token — you can’t just dump the protocol token to escape punishment; operators have real ETH at risk.

Trust Hierarchy

“`

Ethereum validators → Restake → EigenLayer

EigenLayer → Operate → Multiple AVSes

AVSes → Pay → Operators

AVSes → Slash → Operators (from ETH collateral)

“`

Operator vs. Restaker

There are two roles:

  • Restakers: Deposit ETH or LSTs into EigenLayer; delegate to operators
  • Operators: Run AVS infrastructure; accept slashing risk; earn fees; no capital required (operators can be pure service providers)

This allows specialization: large stakers can delegate to professional operators who run complex AVS software stacks.


EigenDA — Flagship AVS

The first and most prominent AVS is EigenDA — a high-throughput data availability layer:

Stats:

  • 10 MB/s throughput target — approximately 10,000× Ethereum’s DA bandwidth
  • Erasure coding: Data split into chunks, distributed across operators; any 1/3 of operators can reconstruct
  • Used by: Mantle (as their DA layer), Celo, AltLayer rollups, Offshore chains
  • Significantly cheaper than Ethereum calldata or blobs for high-volume rollups

Why it’s important:

  • Demonstrates the AVS model working at scale — paying operators EIGEN for DA services
  • Competes with Celestia and Avail in the modular DA market
  • Leverages EigenLayer’s operator base (top 100+ operators participated at launch)

Revenue flow:

“`

Rollup pays EigenDA fee → EigenDA distributes to operators → Operators earn above Ethereum base rate

“`


The EIGEN Token

EIGEN is EigenLayer’s protocol token with a unique dual-role design:

Programmatic Slashing Token

  • Process: Off-chain governance identifies bad actor → slashing of EIGEN stake (separate from ETH slashing)
  • Creates a second layer of cryptoeconomic accountability

Utility Token for AVS Payments

  • Operators can get “delegated” EIGEN to increase their voting weight for intersubjective disputes
  • Foundation allocated EIGEN for early ecosystem bootstrapping

Distribution (Initial):

  • ~15% to investors, ~15% to early contributors, ~29.5% to Eigen Foundation, remainder for community/ecosystem

How AVSes Are Built

Creating an AVS requires:

  1. Define the service: What validation is needed? (e.g., “confirm that L2 batch was processed correctly”)
  2. Define slashing conditions: Onchain contracts encoding what constitutes provable misbehavior
  3. Operator software: Node client that operators run alongside their EVM validator
  4. Staking/delegation minimums: How much restaked ETH must an operator have?
  5. Payment mechanism: How do operators get paid (ERC-20 token, ETH, etc.)?
  6. Register with EigenLayer contracts

Key constraint: slashing must be objective (for ETH) or intersubjective (for EIGEN)

  • EigenLayer won’t support AVSes with purely off-chain or social slashing conditions for ETH
  • Prevents abuse where an AVS could slash operators for arbitrary reasons

Risk Analysis

The approach is detailed in the sections below.

Risks to Restakers/Operators

  • Smart contract risk: Bugs in AVS slashing contracts
  • Systemic risk: If heavily adopted, coordinated slash across many AVSes could destabilize ETH staking

Risks to the Ethereum Ecosystem

  • Complexity risk: Operators managing 10+ AVSes create new attack surfaces
  • Governance capture: AVSes with large EIGEN allocations to operators could vote together

Vitalik Buterin raised concerns about extending Ethereum consensus to validate too many external things (“overloading Ethereum consensus”) — EigenLayer’s intersubjective slashing (EIGEN, not ETH) is partly a design response to this criticism.


AVS Landscape (Active and Upcoming)

AVS Category Status
EigenDA Data availability Live
AltLayer Restaked rollups Live
Lagrange ZK coprocessors Live
Eoracle Oracle network Live
Hyperlane Interchain messaging Live
Near DA Data availability Live
Witness Chain DePIN proofs Live
Brevis ZK data coprocessor Beta
Omni Network L1 interoperability Beta

How to Use EigenLayer

As a restaker:

  1. Stake ETH on Ethereum → receive stETH (Lido) or similar LST
  2. Visit app.eigenlayer.xyz
  3. Deposit ETH or LST
  4. Delegate to an operator

As an operator:

  1. Meet minimum stake requirements (operator minimums set by each AVS)
  2. Register as operator in EigenLayer contracts
  3. Choose which AVSes to opt into
  4. Set up and run AVS node software
  5. Accept slashing conditions

Get ETH to start at . Secure your keys with .


Social Media Sentiment

EigenLayer’s AVS model is intellectually compelling — the idea that protocols can rent Ethereum’s security without bootstrapping their own validator set solves a genuine cold-start problem. EigenDA has demonstrated the model works technically. Criticism centers on systemic risk (concentrated restaking through few operators creating correlated failure scenarios), the EIGEN token’s initially non-transferable status creating confusion, and whether most AVSes actually need Ethereum-grade security or are using EigenLayer for marketing legitimacy. The protocol’s TVL ($10B+ in peak restaking craze of early 2024) showed massive market interest, though much of this was driven by points farming speculation rather than genuine AVS demand. The long-term thesis depends on whether enough real AVS revenue materializes to make restaking economically sustainable without inflationary token incentives.


Last updated: 2026-04

Related Terms


Sources

Eigenlayer Whitepaper. (2023). EigenLayer: The Restaking Collective. EigenLayer Foundation.

Buterin, V. (2023). Don’t Overload Ethereum’s Consensus. Vitalik.ca.

Al-Bassam, M., Sonnino, A., Buterin, V., & Khabbazian, M. (2019). Fraud and Data Availability Proofs. arXiv.

Carlsten, M., Kalodner, H., Weinberg, S. M., & Narayanan, A. (2016). On the Instability of Bitcoin Without the Block Reward. CCS ’16.

Heimbach, L., Kiffer, L., & Wattenhofer, R. (2023). Ethereum’s Restaking Ecosystem. arXiv.