01
Restake ETH or LSTs
Deposit ETH (via native restaking) or liquid staking tokens (stETH, rETH, cbETH) into EigenLayer smart contracts. Your stake is now eligible to be committed to secure AVS services on top of Ethereum.
- What is EigenLayer and what problem does restaking solve
- Actively Validated Services (AVS): what they are and examples
- LST restaking vs native restaking: key differences
- Operators: who they are, what they do, and how to choose
- EIGEN token: utility, intersubjective slashing, and staking
- EigenLayer rewards: how stakers and operators earn
- Slashing on EigenLayer: conditions, severity, and what's at risk
- How to restake on EigenLayer: step-by-step guide
- EigenLayer risks: slashing, smart-contract, and operator risk
- EigenLayer vs Symbiotic vs Karak: restaking protocol comparison
- Best practices for restakers and delegators
- Troubleshooting: missing rewards, withdrawal queues, delegation issues
- Authoritative sources & references
- FAQ
What Is EigenLayer and What Problem Does Restaking Solve?
Every new decentralised protocol — a data availability layer, a decentralised sequencer, an oracle network, a cross-chain bridge — needs cryptoeconomic security to be trustworthy. Traditionally, each protocol bootstraps its own validator set and token, forcing it to compete for security capital from scratch. This is expensive, slow, and results in fragmented, under-secured ecosystems.
EigenLayer solves this by allowing Ethereum validators and ETH stakers to restake — extending Ethereum's already-enormous security pool to new services without requiring those services to recruit and incentivise a new validator set. A new AVS can launch with billions of dollars of cryptoeconomic security on day one by simply integrating with EigenLayer.
For ETH stakers
Earn additional rewards on top of existing ETH staking yield by opting your stake into securing AVS services. No new capital required — the same ETH earns more.
Extra yieldSame ETHOpt-in
For AVS builders
Launch a new decentralised service with Ethereum-grade cryptoeconomic security immediately — without bootstrapping your own validator network or token from zero.
Instant securityNo bootstrappingETH-backed
Actively Validated Services (AVS): What They Are and Real-World Examples
An Actively Validated Service (AVS) is any decentralised system that requires a network of validators to perform tasks and wants those validators to put up cryptoeconomic stake as a commitment to honest behaviour. EigenLayer provides the infrastructure to recruit, coordinate, and slash those validators using restaked ETH.
| AVS category | What it does | Example protocols |
|---|---|---|
| Data availability layers | Store and serve rollup transaction data with availability guarantees | EigenDA (Eigen Labs' own AVS) |
| Decentralised sequencers | Order and finalise L2 transactions in a decentralised, censorship-resistant way | Various L2 sequencer projects |
| Oracle networks | Deliver off-chain price and data feeds on-chain with economic security | Multiple oracle AVS integrations |
| Cross-chain bridges | Verify cross-chain message passing with validator-backed security | Bridge protocols using EigenLayer security |
| Keeper networks | Automate on-chain actions (liquidations, rebalancing) with committed operators | Automation AVS protocols |
| Coprocessors / ZK provers | Outsource heavy computation off-chain with on-chain verification | ZK coprocessor AVS networks |
EigenDA — Eigen Labs' own AVS for data availability — is the largest and most mature
AVS on EigenLayer, already used by major L2s as a cheaper alternative to Ethereum calldata.
It is the clearest example of how AVS services are structured and what restaking enables.
LST Restaking vs Native Restaking: Key Differences and Trade-offs
EigenLayer supports two distinct ways to restake, with meaningfully different mechanics, requirements, and risk profiles.
| Dimension | LST Restaking | Native Restaking |
|---|---|---|
| What you deposit | Liquid staking tokens (stETH, rETH, cbETH, etc.) | 32 ETH directly via an EigenPod |
| Validator required? | No — any holder of LSTs can participate | Yes — you must run an Ethereum validator node |
| Minimum stake | No enforced minimum beyond gas | 32 ETH (Ethereum validator requirement) |
| Slashing layers | LST protocol slashing + EigenLayer slashing | Ethereum consensus slashing + EigenLayer slashing |
| Complexity | Low — deposit LST via app | High — requires validator infrastructure |
| Reward potential | AVS rewards on top of LST yield | AVS rewards on top of solo staking yield (higher base) |
For most users: LST restaking is the practical path. Native restaking is for
sophisticated operators who already run their own Ethereum validators and want to maximise
yield while retaining full control over the staking relationship.
EigenLayer Operators: Who They Are, What They Do, and How to Choose One
Operators are the entities that run the actual node software for each AVS. They register with EigenLayer, accept delegated stake from restakers, opt into AVS services, and run the required infrastructure in exchange for a share of AVS rewards.
What operators do
Register on EigenLayer, maintain validator software for each opted-in AVS, manage stake delegated by restakers, collect AVS rewards and distribute a share to delegators.
Node operationAVS softwareReward distribution
Choosing an operator safely
Evaluate operator uptime history, number and quality of AVS services opted into, commission rates, total delegated stake, and whether they have a public track record and transparent operations.
Uptime historyAVS diversityCommission rate
Critical risk: If your chosen operator misbehaves on an AVS — submits invalid data,
goes offline at a critical moment, or commits a slashable offence — your restaked ETH is at risk
of being slashed. Operator selection is the most important risk management decision for restakers.
EIGEN Token: Utility, Intersubjective Slashing, and Staking
EIGEN is EigenLayer's native token, designed to enable a new category of slashing called intersubjective slashing — for faults that cannot be proven on-chain but are objectively observable by the broader community.
Objective vs intersubjective faults
Objective faults (double signing, provable equivocation) can be slashed directly on Ethereum via smart contracts. Intersubjective faults — like an oracle network consistently reporting wrong prices — are real violations but cannot be proven mathematically on-chain. EIGEN enables community-driven slashing for these cases.
New fault categoryCommunity governed
EIGEN staking
EIGEN holders can stake their tokens to participate in intersubjective fault resolution and earn staking rewards from the protocol. Staked EIGEN also carries slashing risk if the staker validates incorrectly in a dispute resolution process.
Stake EIGENDispute resolutionSlashable
EIGEN airdrop: EigenLayer distributed EIGEN tokens to early restakers via a multi-season
airdrop. If you are researching whether you may have unclaimed EIGEN — check the official EigenLayer
app only. Post-airdrop phishing sites targeting EIGEN claims are prevalent.
EigenLayer Rewards: How Stakers and Operators Earn from Restaking
| Participant | Reward source | Paid in | Notes |
|---|---|---|---|
| Restakers (LST) | AVS reward allocations via operator | AVS tokens or ETH | After operator commission deduction |
| Native restakers | Consensus rewards + AVS rewards | ETH + AVS tokens | Higher base yield than LST restakers |
| Operators | Commission on delegated stake rewards | AVS tokens or ETH | Commission rate set by operator |
| EIGEN stakers | Protocol staking rewards | EIGEN | For participating in intersubjective security |
Reward variability: AVS rewards depend entirely on the AVS's reward budget and how
many restakers are securing it. As restaked ETH grows, the same reward pool is divided among more
participants. Early restakers in high-quality AVS services with fewer competitors capture more reward
per ETH than late entrants into crowded AVS pools.
Slashing on EigenLayer: What Gets Slashed, By How Much, and Under What Conditions
Slashing is EigenLayer's enforcement mechanism — the cost operators pay for dishonest or faulty behaviour. Understanding slashing conditions before restaking is essential, not optional.
| Slashing type | Triggered by | Who is affected | Severity |
|---|---|---|---|
| Objective AVS slashing | Provable on-chain fault by operator (e.g. double-signing, invalid block) | Operator + all delegated restakers | High — proportional penalty on stake |
| Intersubjective slashing | Community-observed fault resolved via EIGEN staking governance | Operator + restakers (EIGEN holders in dispute) | Medium — defined by AVS parameters |
| Ethereum consensus slashing | Ethereum validator equivocation (native restaking only) | Native restaker's ETH stake | Medium — Ethereum standard penalties |
| LST protocol slashing | Underlying LST's own slashing conditions (e.g. Lido validator error) | LST value (affects restaker indirectly) | Usually Low — LST protocols have insurance mechanisms |
Slashing flows to the restaker: When an operator is slashed on an AVS,
the penalty is deducted from the total stake they manage — including your delegated restaked ETH.
You are not insulated from your operator's slashing events. This is the fundamental risk
trade-off of restaking that every participant must internalise before committing capital.
How to Restake on EigenLayer: Step-by-Step Guide for LST Restakers
- Go to the official EigenLayer app — use a bookmarked URL only. Verify the domain before connecting your wallet. Phishing sites targeting EigenLayer users are common.
- Connect a non-custodial wallet — MetaMask, Rabby, or a hardware wallet for significant amounts.
- Choose LST restaking — select the liquid staking token you want to restake (stETH, rETH, cbETH, etc.) and approve the EigenLayer contract to interact with it.
- Deposit your LSTs — confirm the deposit transaction. Your tokens are now held in EigenLayer's strategy contracts and eligible for delegation.
- Research and select an operator — review operators by total delegated stake, AVS coverage, commission rate, and operational track record. This is the most important decision you make.
- Delegate to your chosen operator — confirm the delegation transaction. Your restaked ETH now backs that operator's AVS validation work.
- Monitor rewards and operator health — check the EigenLayer dashboard periodically for reward accrual and operator performance metrics.
- To exit: undelegate from the operator (subject to a withdrawal delay), then withdraw your LSTs from EigenLayer. Plan the exit around the undelegation queue timeline.
Withdrawal queue: EigenLayer has a withdrawal waiting period after undelegation.
This is intentional — it allows AVS services time to recognise that the stake is leaving
and adjust their security accordingly. Factor this illiquidity into your restaking strategy.
EigenLayer Risks: Slashing, Smart-Contract, Operator, and Systemic Risks
| Risk | Level | Mitigation |
|---|---|---|
| Operator slashing event | High if operator misbehaves | Carefully vet operators; diversify across multiple operators |
| Smart-contract exploit | Medium | Multiple audits; large bug bounty; significant battle-testing |
| AVS software bug causing slashing | Medium | Choose operators running mature, audited AVS services |
| Withdrawal queue delay | Medium | Plan exits in advance; do not restake capital needed on short notice |
| LST de-peg (LST restaking) | Low-Medium | Choose well-established LSTs with deep liquidity (stETH, rETH) |
| Cascading slash contagion | Low — theoretical systemic risk | Emerging risk as TVL grows; monitor protocol governance for mitigations |
| Phishing / fake EigenLayer UI | High (user-controlled) | Bookmark official URL; verify domain before every session |
EigenLayer vs Symbiotic vs Karak: Restaking Protocol Comparison
| Feature | EigenLayer | Symbiotic | Karak |
|---|---|---|---|
| Backing / origin | Eigen Labs (a16z backed) | Paradigm & cyberfund backed | Various backers |
| Supported assets | ETH, major LSTs | ETH, LSTs, ERC-20s broadly | ETH, LSTs, ERC-20s |
| Chain focus | Ethereum-centric | Chain-agnostic | Multi-chain |
| AVS ecosystem | Largest — most mature AVS set | Growing | Growing |
| Native token | EIGEN (intersubjective slashing) | TBD | TBD |
| TVL (as of 2026) | Largest | Significant | Smaller |
EigenLayer's moat: First-mover advantage, the largest AVS ecosystem,
and EIGEN's unique intersubjective slashing design give EigenLayer structural advantages.
Symbiotic's chain-agnostic and broader collateral model appeals to protocols outside Ethereum.
Competition benefits restakers through better rates and more AVS options over time.
Best Practices for EigenLayer Restakers and Delegators
- Treat operator selection as a security decision — not just a yield decision. A high-APR operator running buggy or unaudited AVS software is a slashing risk, not an opportunity.
- Diversify across multiple operators for significant positions — concentrating all restaked ETH with one operator means one slashing event can affect your entire position.
- Only restake ETH you don't need quickly — the withdrawal queue means restaked capital is illiquid for a defined period. Never restake emergency or short-term funds.
- Monitor operator AVS opt-ins over time — operators can opt into new AVS services after you delegate. New AVS services mean new slashing conditions you didn't originally accept. Review regularly.
- Bookmark the official EigenLayer app URL — phishing is the most common user-controlled risk. Verify the domain every session.
- Revoke approvals after exiting — EigenLayer strategy contracts require token approvals. Use Revoke.cash to clean up after withdrawal.
- Use a hardware wallet for material restaking positions — the combination of approval transactions, delegation, and withdrawal makes this a high-interaction protocol.
Troubleshooting EigenLayer: Missing Rewards, Withdrawal Queues, and Delegation Issues
"I'm not seeing any rewards after restaking"
- Rewards require full delegation to an operator who is actively opted into at least one live AVS. Simply depositing LSTs without delegating earns no AVS rewards.
- AVS rewards are distributed on a per-reward-period cadence — not continuously. Check the official EigenLayer app's rewards dashboard for your accrual status.
- Some AVS services have qualification criteria (minimum stake, minimum time delegated) before reward eligibility begins.
"My withdrawal is taking longer than expected"
- The withdrawal queue is protocol-enforced and intentional. Check the current queue duration in the official EigenLayer app — it is displayed when you initiate an undelegation.
- Ensure you have completed both steps: undelegating from the operator AND submitting the withdrawal transaction once the queue clears. Missing the second step is common.
"I delegated to an operator but they appear inactive"
- Verify the operator's status on the official EigenLayer operator dashboard — some operators may have reduced AVS opt-ins over time.
- If an operator is fully inactive, consider undelegating and re-delegating to an active operator. This restarts your withdrawal queue for the exit, so plan accordingly.
Always verify on-chain: The EigenLayer UI can lag behind contract state.
For withdrawal status, check the EigenLayer smart contract state via Etherscan if the UI is unclear.
Never share your seed phrase or private key with anyone claiming to be EigenLayer support.
EigenLayer: Authoritative References & External Sources
EigenLayer — Official Sources
- EigenLayer — Official Website
- EigenLayer — Official Documentation
- EigenLayer — Smart Contracts (GitHub)
- EigenLayer — Governance & Research Forum
Restaking Research & Data
- DeFiLlama — EigenLayer TVL & Protocol Data
- Dune Analytics — EigenLayer On-chain Dashboards
- Ethereum.org — Ethereum Staking Overview
Security & Risk Research
- OpenZeppelin — Smart Contract Security Audits
- Rekt.news — DeFi Exploit Post-Mortems
- Revoke.cash — Token Approval Manager
About: Prepared by Crypto Finance Experts as a practical, SEO-oriented knowledge base
for EigenLayer: restaking mechanics, AVS, operators, EIGEN token, slashing, rewards, and security.
EigenLayer: Frequently Asked Questions
EigenLayer is a protocol on Ethereum that allows ETH stakers and liquid staking token holders to "restake" — extending their staked ETH's cryptoeconomic security to additional decentralised services called AVS (Actively Validated Services). Restakers earn additional rewards beyond base ETH staking yield in exchange for accepting additional slashing conditions tied to the AVS services their chosen operator validates.
An Actively Validated Service (AVS) is any decentralised protocol — data availability layer, oracle, bridge, sequencer — that needs a network of validators with economic stake at risk to ensure honest behaviour. By using EigenLayer, an AVS can tap into Ethereum's existing staked ETH pool for security instead of bootstrapping its own validator set from scratch. This gives AVS services immediate, credible cryptoeconomic security on launch.
Yes — restaked ETH is subject to slashing if the operator you delegated to commits a slashable offence on an AVS. Slashing penalties are deducted from the total stake the operator manages, including your delegated portion. This is the fundamental risk trade-off of restaking. Carefully vetting your operator and diversifying across multiple operators are the primary risk mitigations available to restakers.
EIGEN is EigenLayer's native token designed to enable "intersubjective slashing" — penalising faults that are obvious to humans but cannot be proven on-chain algorithmically (like an oracle network consistently providing wrong data). Restaked ETH handles objective, provably on-chain faults. EIGEN handles the grey-area human-observable faults. The two systems work in parallel to cover different categories of validator misbehaviour.
LST restaking means depositing liquid staking tokens (stETH, rETH, cbETH) into EigenLayer — accessible to anyone without running a validator. Native restaking means restaking 32 ETH directly via an EigenPod while running your own Ethereum validator node — higher complexity, higher base yield, and maximum control. Most retail participants use LST restaking; native restaking is for sophisticated operators.
EigenLayer enforces a withdrawal queue after undelegation — the exact duration is protocol-defined and displayed in the app when you initiate an exit. This delay is intentional: it allows AVS services to recognise the departing stake and adjust security parameters. Plan exits in advance and never restake capital you may need on short notice.
To earn AVS rewards: deposit LSTs or ETH into EigenLayer, then delegate to an active operator who has opted into live AVS services. Rewards flow from the AVS to the operator, who distributes a share (minus their commission) to delegators. Simply depositing without delegating earns no AVS rewards. Reward rates vary by AVS and how many restakers are competing for each AVS's reward pool.
Regular ETH staking secures only Ethereum consensus and earns only Ethereum staking rewards. EigenLayer restaking additionally commits your stake to securing AVS services — earning extra rewards but accepting additional slashing risk from those AVS services. Regular staking has one slashing surface (Ethereum); restaking adds one or more additional slashing surfaces (each opted-in AVS). More reward = more risk.
EigenLayer's smart contracts have undergone multiple security audits and the protocol has processed billions in restaked ETH. However, the protocol's complexity — multiple interacting contracts, operator delegation mechanics, and diverse AVS integrations — means smart-contract risk is non-trivial. Phishing is the primary user-controlled risk. Always access EigenLayer via a bookmarked official URL and verify the domain before every wallet connection.