Liquid Staking, Restaking & Shared Security: EigenLayer, LSTs & Economic Security Pooling

EigenLayer & The Shared Security Paradigm: Repurposing Economic Consensus

Historically, every new decentralized infrastructure protocol—such as data availability layers, cross-chain bridges, oracle networks, keeper networks, and coprocessors—was forced to bootstrap its own sovereign Proof-of-Stake consensus network from scratch. This introduced severe economic vulnerabilities:

• Bootstrapping Problem: A new oracle network with only $50M in native staked tokens can be corrupted by an attacker for $35M, even if it secures billions of dollars in DeFi value.
• Capital Inefficiency: Validators must fragment their capital across dozens of individual network tokens.

EigenLayer introduced the Restaking Paradigm, allowing validators and LST holders to repurpose their already-staked Ethereum capital to simultaneously secure supplementary distributed systems—known as Actively Validated Services (AVSs).

By extending the validator's commitment via Ethereum's withdrawal_credentials pointing to the EigenLayer Strategy Manager contract:

• The staker continues earning standard Ethereum consensus staking yield (~3.5% APR).
• The staker opts into securing one or more AVSs (such as EigenDA, Witness Chain, or Hyperlane), earning supplementary protocol fees.
• In exchange, the staker grants the AVS smart contract the authority to enforce custom Slashing Rules against their underlying staked ETH if the node operator violates the specific cryptographic rules of the AVS.

This architecture creates a unified pooled cryptoeconomic security blanket across the entire Web3 infrastructure stack, making it economically unfeasible to attack individual middleware components.

Actively Validated Services (AVS) Architecture & Slashing Logic

An Actively Validated Service (AVS) in the EigenLayer ecosystem consists of five core components:

1. Service Manager Contract: The central coordinator contract on Ethereum that registers AVS tasks and defines quorum requirements.
2. Operator Registry: Maintains the directory of registered node operators and their delegated restaked voting power.
3. Off-Chain Node Client: Software run by operators that executes the AVS workload (e.g., verifying off-chain compute, generating data availability proofs, or signing oracle attestations).
4. Stake Registry & Quorum Slicer: Calculates operator quorum weights across multiple staking strategies (e.g., native ETH, stETH, rETH, and native AVS tokens).
5. Slasher Module: An immutable on-chain adjudication contract containing the cryptographic fault-proof verification logic.

If an operator signs two conflicting data availability commitments or submits an invalid state transition proof to an AVS, the fault proof is submitted to the Slasher Module. Upon successful on-chain verification, the slasher burns a predefined percentage of the operator's restaked collateral, immediately expelling them from the active set and compensating the affected service.

The mathematical beauty of AVS slashing lies in programmable attribution: each AVS defines its own deterministic fault specifications, ensuring honest operators are never penalized for ambiguous network latency while provable Byzantine malicious acts result in instant capital confiscation.

Liquid Restaking Tokens (LRTs) & Systemic Financialization Loops

To optimize yield across multiple AVSs, the market developed Liquid Restaking Protocols (such as Ether.fi, Renzo, and Kelp DAO) which issue Liquid Restaking Tokens (LRTs) like eETH and ezETH.

LRT protocols manage the complex operational task of selecting high-performing AVS operators, balancing risk profiles, and automatically compounding multiple streams of AVS reward tokens.

However, the rapid financialization of LRTs has introduced profound systemic cryptoeconomic risks:

• Cascading Slashing Contagion: If an operator securing 5 distinct AVSs experiences a correlated software bug or validator configuration failure, they could be slashed simultaneously across all 5 protocols, destroying 100% of deposited capital.
• De-Pegging Liquidity Liquidation Spirals: When LRTs are deposited into DeFi lending protocols (like Aave or Morpho) as collateral to borrow pure ETH and restake again (leveraged looping up to $5\times$), any slight secondary market discount on the LRT can trigger mass automated liquidations, dumping LRTs into illiquid AMM pools and causing severe de-peg cascades.
• Intersystemic Coordination Risks: Vitalik Buterin highlighted the danger of overloading Ethereum's social consensus: if a massive multi-billion-dollar AVS fails and attempts to fork Ethereum to recover lost restaked funds, it threatens the political and cryptographic neutral base of Layer-1.

## Dual Staking Models & Native AVS Token Utility Mechanisms

While restaking pure ETH provides immense baseline cryptoeconomic security, early AVS protocols faced a tokenomic dilemma: relying entirely on ETH restaking diluted the economic utility and governance demand for the AVS protocol's native token.

To solve this, advanced restaking protocols implement Dual-Staking Architectures:

• Two-Tier Security Quorum: An AVS defines two independent security quorums: a Universal Security Quorum denominated in restaked ETH (providing deep macroeconomic crash resistance) and a Native Security Quorum denominated in the native AVS token.
• Consensus Validation Thresholds: To finalize a state commitment or data availability batch, an operator payload must achieve a $2\mathrm{/}3$ supermajority vote in both the ETH quorum AND the native token quorum simultaneously.
• Dynamic Slashing Proportions: Slashing events are partitioned across the two pools, ensuring that native token holders have direct skin-in-the-game while shielding external ETH stakers from hyper-volatile governance capture events.

This dual-tier approach guarantees that native token holders retain active governance control and protocol accrual rights, while leveraging the multi-billion-dollar economic fortress of restaked Ethereum assets to prevent low-cost hostile 51% takeover attacks.

Symbiotic, Karak & Multi-Asset Restaking Competition

The restaking design space has expanded beyond Ethereum-native assets into generalized multi-asset shared security protocols, notably Symbiotic and Karak:

• Symbiotic: A modular, permissionless shared security network backed by Paradigm. Symbiotic allows any ERC-20 token (including stablecoins, LP tokens, and wrapped governance tokens) to serve as restaked collateral. It introduces immutable Core Vaults that decouple collateral deposit logic from slasher contract execution, offering maximum flexibility to custom AVS developers.
• Karak Network: Multi-chain restaking layer that accepts multi-asset deposits (USDC, staked SOL, BTC wrappers) across multiple L2 networks, allowing new rollups to bootstrap cross-chain economic security without forcing users to bridge back to Ethereum mainnet.
• Restaking for Bitcoin & Solana (Babylon & Jito): Babylon brings PoS restaking security to Bitcoin without bridging, using cryptographic extractable one-time signatures (EOTS) to slash UTXOs on the Bitcoin blockchain if a validator double-signs on an external PoS chain. Jito (Re)staking brings similar restaking capabilities to the Solana validator ecosystem.

## Frequently asked questions

What is the main difference between an LST and an LRT?

An LST (like stETH) represents ETH staked only to secure the Ethereum Layer-1 consensus layer. An LRT (like eETH) represents ETH that is restaked across both Ethereum L1 and multiple supplementary AVS middleware protocols.

How does EigenLayer enforce slashing on native staked ETH?

Native stakers point their Beacon chain validator withdrawal credentials to an EigenLayer EigenPod contract, which can freeze and burn the validator withdrawal balance if an AVS slashing proof is submitted.

What is an Actively Validated Service (AVS)?

An AVS is any decentralized middleware service (such as an oracle, bridge, sequencer, or data availability network) that rents economic security from Ethereum validators via restaking.

Related reading

• Ethereum base-layer validator staking and slashing — Understand the primary consensus layer that provides the underlying capital for EigenLayer restaking.
• LST and LRT collateral loops in lending markets — Explore how leveraged staking loops in money markets amplify systemic yield and liquidation risks.

## Sources

• Lido documentation: stETH and liquid staking — Lido
• EigenLayer documentation: restaking and shared security — EigenLayer

No contributor to this article holds a professional cryptography or security credential. Every technical claim above is sourced to primary protocol documentation rather than to personal authority — follow the sources and verify anything you intend to act on.

Not financial advice. Crypto assets are volatile and can lose value. This article describes how protocols work, not what you should buy.