Restaking in 2025: The Complete EigenLayer and AVS Guide for Rewards, Slashing Risks, and LRTs
Restaking is one of the most powerful and misunderstood ideas in Ethereum security. It lets ETH or liquid staking tokens support additional networks beyond Ethereum, usually through EigenLayer and Actively Validated Services. The upside is extra yield, new security markets, and faster infrastructure bootstrapping. The downside is slashing, operator risk, LRT depeg risk, governance risk, and correlated failure across multiple services. This TokenToolHub guide explains restaking from first principles, how EigenLayer works, what AVSs are, where rewards come from, how slashing can happen, and how to approach liquid restaking tokens without turning extra APY into hidden leverage.
TL;DR
- Restaking lets staked ETH or liquid staking tokens help secure additional services beyond Ethereum’s base chain.
- EigenLayer is the best-known restaking framework. It connects restakers, operators, and Actively Validated Services.
- AVSs are networks or services that need validators with economic collateral, such as data availability, oracles, coprocessors, shared sequencing, bridges, and MEV-related systems.
- Restaking yield comes from base ETH staking rewards, AVS fees, operator incentives, protocol incentives, emissions, points, and possible future token rewards.
- Restaking is not free APY. You accept extra slashing, liquidity, smart-contract, governance, operator, and correlation risk.
- Liquid restaking tokens make access easier, but they add another layer of custody, DeFi liquidity, withdrawal queue, smart-contract, and policy risk.
- Beginners should start small, understand AVS exposure, avoid stacking too many LRT loops, and choose operators based on uptime, diversity, transparency, and risk controls.
Restaking adds new obligations to already-staked collateral. The extra yield exists because your ETH, LSTs, or LRTs are helping secure additional services. If an operator fails, an AVS policy is violated, a smart contract breaks, or liquidity disappears during stress, the extra APY can be wiped out by penalties, depegs, or exit delays.
Treat restaking like a security market. You are not only earning. You are underwriting risk.
Why restaking matters in 2025
Proof-of-Stake changed how blockchains secure themselves. Instead of relying on proof-of-work mining, PoS networks use economic collateral and validator behavior to protect consensus. Ethereum has one of the largest and most battle-tested PoS security budgets in crypto, which makes it attractive as a source of reusable security.
Restaking tries to reuse that Ethereum security for new networks and services. Instead of every new protocol creating its own validator set, its own token incentives, and its own economic security from scratch, it can connect to restaked ETH through a marketplace of operators. The pitch is simple: borrow Ethereum’s economic security and pay restakers and operators for the work.
This is powerful because bootstrapping security is one of the hardest parts of building crypto infrastructure. A new data availability layer, oracle network, bridge, shared sequencer, or coprocessor needs a set of validators with real money at stake. Without enough collateral, attacks can be cheap. With restaked ETH, the cost of corruption can become higher.
But the same design also creates new risk. If one pool of collateral secures many services at once, a fault in one service can affect restakers who thought they were only adding a small yield layer. Risk becomes multidimensional. Operator selection matters. AVS policy matters. Slashing terms matter. LRT liquidity matters. Governance matters.
What is restaking?
Restaking means pledging already-staked ETH, or tokens representing staked ETH, to secure additional services beyond Ethereum’s base chain. These additional services are commonly called Actively Validated Services, or AVSs.
An AVS can be anything that needs a set of validators with skin in the game. Examples include data availability services, oracle networks, shared sequencers, coprocessors, bridges, finality gadgets, MEV services, and other infrastructure modules that need active verification.
Instead of building a small validator set with weak economics, an AVS can use restaked ETH as collateral. The AVS can say: if you validate us incorrectly, fail required duties, equivocate, or violate our rules, some of the restaked collateral can be penalized. That penalty threat makes attacks more expensive.
As a restaker, you may earn additional rewards from AVSs in addition to base ETH staking yield. But the extra yield is not free. It exists because you are accepting additional service-level risk.
Two primary ways to restake
| Restaking path | How it works | Best for | Main risk |
|---|---|---|---|
| Native restaking | You run an Ethereum validator and opt into restaking modules directly with validator credentials. | Advanced validators, professional operators, and teams with infrastructure experience. | Operational mistakes, validator key management, slashing, and AVS-specific obligations. |
| Liquid restaking | You deposit ETH or liquid staking tokens into a restaking protocol and receive a liquid restaking token. | Regular users who want restaking exposure without running validators. | Smart-contract risk, LRT depeg risk, withdrawal queues, operator policy, and governance exposure. |
The EigenLayer stack: restakers, operators, and AVSs
EigenLayer is the flagship restaking framework on Ethereum. Its role is to connect restaked collateral to services that need economic security. It does this through a marketplace involving restakers, operators, and AVSs.
Restakers provide collateral. Operators run infrastructure. AVSs define the services, rules, rewards, and penalties. The system works only when all three layers are properly understood.
Restakers
Restakers are users or validators who commit ETH, LSTs, or restaked positions to secure additional services. They usually delegate their restaked power to an operator. In return, they may receive a share of AVS rewards after operator fees, protocol fees, and other costs.
Operators
Operators are the infrastructure providers that perform the work required by AVSs. They may run nodes, sign messages, verify data, perform off-chain computation, support liveness guarantees, monitor events, or execute AVS-specific tasks.
Operator quality matters because the restaker’s collateral can be affected by the operator’s behavior. Uptime, client diversity, cloud diversity, monitoring, key management, and incident response are not cosmetic details. They are part of your risk exposure.
AVSs
AVSs are the services that use restaked security. They publish their own rules, reward models, verification requirements, and slashing conditions. Some AVSs may begin with reputation or soft penalties. Others may introduce enforceable slashing that can affect restaked collateral.
The key point is that every AVS is different. You cannot evaluate restaking only by looking at the headline APY. You must evaluate what the AVS does, how it pays, what it can slash, and how its rules are enforced.
EigenLayer due diligence checklist
- Which asset are you restaking: native ETH, LST, or LRT?
- Which operator are you delegating to?
- Which AVSs does that operator support?
- What are the AVS slashing conditions?
- Are rewards paid in ETH, stablecoins, AVS tokens, points, or emissions?
- What fees are taken by the operator and restaking protocol?
- How long is the withdrawal or unbonding period?
- Can governance change risk rules after you deposit?
Actively Validated Services explained
An Actively Validated Service is any system that needs active verification by operators and economic consequences for bad behavior. The AVS receives security from restaked collateral, while restakers and operators receive rewards for providing that security.
In practice, AVSs are infrastructure services. They are not all equal. Some may be critical and revenue-generating. Others may be experimental. Some may use strong slashing policies. Others may rely more on reputation and incentives during early phases. The risk profile depends on the AVS design.
Common AVS categories
- Data availability: services that help prove data is published and retrievable.
- Shared sequencing: systems that order transactions for rollups or appchains.
- Oracles: networks that deliver external data with verification and economic accountability.
- Coprocessors: services that perform computation and return verifiable results.
- Bridges and finality gadgets: cross-chain message verification and security extensions.
- MEV and ordering markets: systems experimenting with block building, ordering fairness, and censorship resistance.
The most sustainable AVSs will likely be those with real demand and fee revenue. If rewards depend only on emissions or points, the yield may look attractive at first but become fragile when incentives slow down.
Rewards and yield math
Restaking yield is built in layers. The first layer is base ETH staking yield. The second layer is AVS rewards. The third layer may include points, incentives, emissions, or future token allocations. The final result depends on fees, liquidity, depeg risk, operator performance, and slashing probability.
Net Restaking APY ≈ Base ETH Staking APY
+ AVS Fees Paid to Restakers
+ Incentives, Points, or Token Rewards
- Operator Fees
- Protocol Fees
- Liquidity Costs
- LRT Depeg Risk
- Expected Slashing Cost
The cleaner the reward source, the easier it is to evaluate. Fees paid in ETH or stablecoins are easier to price than speculative points. Native AVS token rewards can be valuable, but they introduce price risk. Points can be attractive, but they are not guaranteed income unless the protocol later assigns value to them.
What changes your realized yield
- Operator fee: operators may take a cut of AVS rewards for running infrastructure.
- Protocol fee: liquid restaking protocols may charge management, performance, or protocol fees.
- Utilization: if AVS demand is limited, not all delegated stake may earn the headline return.
- Payment asset: rewards in volatile AVS tokens carry more uncertainty than ETH or stablecoins.
- Withdrawal queues: exit delays create opportunity cost, especially during stress.
- LRT liquidity: if the LRT trades below net asset value, exiting through secondary markets may crystallize a loss.
- Slashing risk: expected yield must be adjusted for the probability and size of penalties.
A fee-paying AVS with real usage is more durable than a points-only incentive loop. Points can become valuable, but they should not be treated as guaranteed income.
Slashing and correlated risk
Slashing is a penalty applied to restaked collateral when an operator or validator violates a rule. In Ethereum base staking, slashing has specific conditions related to validator behavior. In restaking, slashing can become more complex because AVSs define their own rules.
An AVS may slash for equivocation, incorrect signing, failure to fulfill a task, data withholding, downtime beyond a threshold, invalid computation, oracle manipulation, or other service-specific failures. The exact rules depend on the AVS.
The major concern is correlated risk. If one operator, client, cloud provider, software library, or AVS design flaw affects many restakers at once, losses can spread across a large portion of delegated collateral. This is why operator diversity and AVS exposure limits matter.
Key restaking risk concepts
- Correlation: the same infrastructure bug can affect many AVSs, operators, or delegated positions at once.
- Policy clarity: AVSs should clearly publish violation types, evidence standards, penalty sizes, and appeal mechanisms.
- Operator quality: uptime, client diversity, cloud diversity, monitoring, and incident response are part of your risk profile.
- Opt-in scope: narrower AVS exposure can reduce correlated slashing risk.
- LRT layering: liquid restaking stacks LST risk, LRT protocol risk, operator risk, AVS risk, and DeFi liquidity risk.
- Governance changes: protocol upgrades can change risk exposure after deposit.
Restaking should be treated as secured lending of trust. You are allowing your collateral to secure additional services. Price the extra yield against the exact slashing surface you are accepting.
Liquid Restaking Tokens: convenience versus complexity
Liquid Restaking Tokens, or LRTs, make restaking easier for regular users. Instead of running a validator or manually delegating native restaked ETH, users deposit ETH or eligible LSTs into a liquid restaking protocol. The protocol handles restaking, operator delegation, and reward accounting. In return, the user receives an LRT that represents the restaked position.
The convenience is obvious. You get fractional access, easier participation, possible auto-compounding, DeFi composability, and simpler operator management. But every layer adds risk.
An LRT can depeg. A withdrawal queue can lengthen. A protocol can change operator allocation. Governance can upgrade contracts. Smart contracts can fail. Rewards can be delayed. A slash can be socialized according to protocol rules. The user may not control the exact AVS exposure underneath the LRT.
| Dimension | What to check | Why it matters |
|---|---|---|
| Collateral and custody | Accepted assets, custody model, upgrade keys, admin timelocks, withdrawal rights. | Determines what backs the LRT and who can change the rules. |
| Operator set | Number of operators, uptime history, client diversity, cloud diversity, incident reports. | Reduces single-operator and correlated infrastructure risk. |
| AVS exposure | Supported AVSs, caps per AVS, slashing policy links, risk disclosures. | Defines the actual source of reward and risk. |
| Liquidity and exits | AMM depth, withdrawal queue, cooldowns, secondary market liquidity. | Determines how quickly you can reduce risk during stress. |
| Fees | Protocol fee, operator fee, performance fee, withdrawal fee. | Directly reduces net yield. |
| Audits and upgrades | Audit reports, bug bounty, proxy patterns, emergency controls, governance delay. | Controls smart-contract and governance risk. |
Operators and delegation
Operators do the work that restakers are economically backing. When you delegate to an operator, you are not simply choosing a name on a dashboard. You are selecting the infrastructure team that can influence your reward and penalty exposure.
Good operators should publish clear information about uptime, AVS exposure, fee schedules, infrastructure diversity, client diversity, monitoring practices, incident history, and emergency procedures. If an operator is vague, that is a risk signal.
Operator due diligence checklist
- Does the operator publish supported AVSs?
- Does it disclose fee schedules?
- Does it show uptime history?
- Does it use multiple clients, clouds, regions, or hardware setups?
- Does it publish incident reports?
- Does it cap exposure to experimental AVSs?
- Does it have clear emergency procedures?
- Does it explain key management and monitoring practices?
Step-by-step: how to restake more safely as a non-validator
Step 1: Decide your approach
Start by choosing between native restaking and liquid restaking. Native restaking is more operationally complex and better suited to validators. Liquid restaking is simpler but adds LRT, smart-contract, liquidity, and governance risk.
- Use native restaking only if you understand validator operations and key management.
- Use liquid restaking if you want simpler exposure but can accept protocol and liquidity risk.
- Define your maximum loss tolerance before chasing yield.
Step 2: Choose the restaking protocol or LRT
Review collateral policy, audits, fees, operator set, AVS exposure, governance permissions, and withdrawal mechanics. Prefer protocols that publish clear dashboards and risk frameworks.
Start with a small test deposit. Observe issuance, reward accounting, secondary market liquidity, and withdrawal mechanics before scaling.
Step 3: Review operator exposure
If you can choose the operator, evaluate uptime, incident history, supported AVSs, client diversity, infrastructure diversity, and fees. If an LRT protocol chooses operators on your behalf, review how that selection is governed.
Step 4: Read AVS terms
Every AVS has different slashing conditions and payment logic. Do not assume all AVSs have the same risk. Read what counts as a violation, how evidence is submitted, how penalties are applied, and what asset rewards are paid in.
Step 5: Monitor and manage
Restaking is not a set-and-forget strategy. Monitor operator health, AVS incidents, governance proposals, LRT liquidity, reward composition, withdrawal queues, and the LRT price relative to underlying value.
Restaking safety checklist
- Cap restaking as a percentage of your total ETH exposure.
- Use a separate wallet for active restaking and DeFi activity.
- Do not put long-term vault ETH into experimental LRT loops.
- Review operator and AVS exposure monthly.
- Avoid overexposure to one LRT, one operator, or one AVS.
- Track withdrawal queue times before you need to exit.
- Do not price points as guaranteed income.
- Practice a partial exit during calm conditions.
EigenLayer versus alternative restaking frameworks
EigenLayer is the canonical Ethereum restaking framework, but it is not the only approach to reusable security. Other frameworks may experiment with multi-asset restaking, modular security, appchain security, or restaking on different base chains.
The comparison should not be based only on headline APY. The right questions are: what collateral secures the system, how slashing is enforced, who operates the infrastructure, what services are being validated, and where rewards come from?
| Dimension | EigenLayer | Alternative restaking frameworks |
|---|---|---|
| Collateral base | ETH and supported liquid staking assets connected to Ethereum security. | May use multiple assets or different base-chain security assumptions. |
| Service scope | AVSs such as data availability, oracles, coprocessors, shared sequencing, and bridges. | Varies widely by ecosystem and design. |
| Slashing model | Policy-driven slashing tied to AVS rules and operator behavior. | May use soft penalties, token-based penalties, or different enforcement models. |
| Operator market | Delegation marketplace with operators competing on performance and policy. | May be permissioned, semi-permissioned, or more centralized. |
| Reward quality | Can include fees, incentives, points, and AVS-specific payments. | Often emissions-heavy early on, requiring extra caution. |
Wallet hygiene for restaking users
Restaking requires active interaction with smart contracts, delegation interfaces, LRT protocols, DeFi liquidity pools, and withdrawal queues. Wallet hygiene matters because one compromised approval or seed phrase can erase more than any yield strategy can recover.
Long-term ETH should not sit in the same wallet used for daily DeFi experiments. A safer setup separates cold storage, restaking activity, and high-risk DeFi activity.
| Wallet role | Use case | Risk control |
|---|---|---|
| Cold vault | Long-term ETH and assets not actively used. | Hardware wallet, minimal approvals, no experimental dApp use. |
| Restaking wallet | LRT deposits, delegation, withdrawals, reward tracking. | Limited balance, regular approval review, separate from main vault. |
| DeFi wallet | Liquidity pools, leverage, experimental protocols, new apps. | Small balances only, high caution, frequent permission cleanup. |
Protect the wallet before chasing restaking APY
Restaking increases smart-contract and delegation exposure. A hardware wallet is not a yield tool, but it is one of the cleanest ways to protect long-term ETH from daily DeFi mistakes.
Security and operations checklist
Restaking should be treated as an active risk position. If you cannot explain the operator, AVS, LRT, withdrawal path, and reward source, the position is probably too complex.
Print this before restaking
- Position sizing: cap restaking exposure as a percentage of total ETH holdings.
- Operator diversification: avoid relying on one operator for all exposure.
- AVS diversification: avoid excessive exposure to one experimental AVS.
- Wallet separation: keep long-term ETH away from high-risk DeFi wallets.
- Policy documentation: bookmark operator pages, AVS slashing docs, and governance forums.
- Alerting: monitor operator health, governance proposals, LRT liquidity, and withdrawal queues.
- Exit drill: practice a partial unwind before market stress begins.
- Reward audit: separate real fees from points, emissions, and speculative airdrop assumptions.
Final verdict
Restaking is one of the most important Ethereum security experiments because it turns ETH economic security into a reusable marketplace. It can help new services bootstrap faster, reduce the need for weak validator sets, and reward ETH holders for securing more than the base chain.
But restaking also changes the risk profile of staked ETH. Once collateral secures multiple services, the restaker must understand more than base staking APY. Operator quality, AVS rules, slashing conditions, LRT liquidity, governance changes, and reward sustainability all matter.
EigenLayer is the main venue for Ethereum-aligned restaking, but users should not treat every AVS, operator, or LRT as equal. The safest approach is to start small, read the rules, diversify carefully, avoid excessive LRT stacking, and treat points as speculative until proven otherwise.
The core rule is simple: if the extra yield is not large enough to justify the slashing, liquidity, governance, and smart-contract risk, do not restake that capital. Restaking can be useful, but only when the risk is understood before the APY is chased.
Restake with a risk budget, not with FOMO
The best restaking strategy is not the highest advertised APY. It is the strategy where you understand the collateral, operator, AVS exposure, slashing path, and exit route before depositing.
Frequently Asked Questions
Is restaking the same as double staking?
No. You do not earn the base staking reward twice. You keep your base ETH staking exposure and may earn extra AVS rewards for taking on additional obligations and risk.
Can I get slashed if I use an LRT?
Yes. LRTs simplify access, but they do not remove risk. If an operator violates an AVS policy and a valid slash is applied, the LRT may absorb loss according to the protocol’s rules.
Are restaking points guaranteed income?
No. Points are speculative unless the protocol clearly converts them into a defined reward. Treat points as upside, not as guaranteed APY.
What pays better: ETH fees, AVS tokens, or points?
ETH or stablecoin fees are easier to value. AVS tokens can be valuable but carry price risk. Points are the most speculative because their final value is uncertain.
Do I need to run my own hardware to restake?
No. Liquid restaking lets regular users participate without running validators. Native restaking is more suitable for validators and advanced operators.
How big should my first restaking position be?
Small enough that a depeg, delayed withdrawal, or 10% to 20% impairment does not damage your portfolio. Start with a test deposit and scale only after understanding accounting and exits.
What is the biggest risk in restaking?
The biggest risk is not one single thing. It is the combination of slashing, operator failure, LRT depeg, smart-contract risk, governance changes, and correlated exposure across multiple AVSs.
Is EigenLayer the only restaking protocol?
No. EigenLayer is the main Ethereum-aligned restaking framework, but other restaking and shared-security models exist. Always compare collateral quality, slashing enforcement, operator decentralization, and reward sustainability.
Docs and further reading
Useful official and educational resources:
- EigenLayer Official Website
- EigenLayer Documentation
- Ethereum Staking Overview
- Ethereum Proof-of-Stake Documentation
- Ethereum Improvement Proposals
- TokenToolHub Blockchain Technology Guides
- TokenToolHub Advanced Blockchain Guides
- TokenToolHub Token Safety Checker
This article is for education only and is not financial advice. Restaking introduces real slashing, liquidity, smart-contract, operator, and governance risks. Always verify current documentation for any protocol, AVS, LRT, or operator before committing funds.
