Restaking lets you reuse the security of staked ETH or liquid staking tokens to secure new networks and middleware. Instead of idle stake, your assets back multiple Actively Validated Services (AVSs) while you keep exposure to Ethereum.

EigenLayer is the leading marketplace for shared security. In 2025, it has become a hub where capital (restakers), operators, and AVSs meet, aligning incentives around performance and safety. This EigenLayer restaking guide explains how it works, how to restake safely, and how to manage rewards and risk across a fast‑moving ecosystem.

If you’re new to staking, review background on proof‑of‑stake and Ethereum staking first. Then come back to extend your security to AVSs with a structured, risk‑aware plan.

• Assets: Restake ETH natively or via LSTs like stETH, rETH, and cbETH; some Liquid Restaking Tokens (LRTs) are also supported.
• Operators: You delegate to node operators who run AVS software. They earn rewards and can be slashed for misbehavior.
• Rewards: Base staking yield + AVS rewards + potential points/airdrop incentives. Terms vary by AVS and operator.
• Risks: Smart‑contract risk, AVS slashing, operator performance, deposit caps and liquidity limits, and tracking/tax complexity.
• Process: Connect wallet → choose asset → approve → restake → delegate to operators → monitor rewards and risk.

Start small, diversify across operators/AVSs, and maintain clear records from day one.

EigenLayer enables shared security: capital from Ethereum’s staking base is pooled and allocated to AVSs, such as data availability layers, oracles, and middleware. AVSs opt in to this security rather than bootstrapping from scratch.

Operators run the software that enforces AVS rules. Restakers delegate stake to operators, giving them economic weight and responsibility. If an operator fails or acts maliciously, restaked collateral may be slashed according to AVS policies.

This market design aligns incentives: AVSs get robust security, operators earn fees/rewards, and restakers monetize idle security. For background on slashing concepts, see Ethereum PoS slashing and smart contracts.

Native restaking uses your validator’s ETH directly, typically via an EigenPod configuration. It offers tight control and fewer token layers, but operational steps and validator management are required.

Liquid Staking Tokens (LSTs) like stETH, rETH, and cbETH represent staked ETH with on‑chain liquidity. Restaking LSTs is simple and keeps assets liquid, but adds smart‑contract and depeg risk from the LST protocol.

Liquid Restaking Tokens (LRTs) issue a token against restaked positions, enabling composability in DeFi. LRTs can boost flexibility but introduce extra protocol layers, custody assumptions, and pricing complexity.

• Choose native for reduced dependency on token wrappers.
• Choose LST for convenience and liquidity.
• Choose LRT if you need composability and understand stacked risks.

1. Prepare wallet: Use a fresh, well‑secured wallet (hardware recommended). Confirm you’re on Ethereum mainnet and verify the official interface URL.
2. Select asset: Pick ETH, an LST (e.g., stETH/rETH/cbETH), or an eligible LRT. Check current deposit caps or windows—popular pools may fill fast.
3. Approve token: If using tokens, submit an ERC‑20 approval with a conservative spend limit. Consider revoking unused approvals later.
4. Restake: Enter amount and confirm the transaction. Wait for finality; verify your new restaked balance in the dashboard.
5. Delegate to operators: Filter by fees, AVS coverage, track record, and uptime. Delegate and confirm. You can diversify across multiple operators as caps allow.
6. Monitor: Track rewards, points, and any slashing/alerts. Use Etherscan and your portfolio tracker to reconcile balances.

For general wallet safety tips, review wallet basics and Ethereum security guidance.

Rewards generally come from three sources: base ETH staking yield (via your validator or LST), AVS rewards/fees for providing security, and periodic points or incentive programs. Actual return depends on your operator and AVS selection.

Risks include smart‑contract bugs, oracle or AVS logic failures, slashing for downtime or equivocation, liquidity constraints from caps, and strategy complexity. Understand each AVS’s slashing rules before delegating.

• Smart‑contract risk: Review audits, bug bounties, and time in production. See smart contracts (Wikipedia).
• Slashing: Read AVS documentation and operator terms; reference PoS slashing.
• Liquidity/caps: Caps can delay deposits and withdrawals; plan buffer liquidity.

Aim for a blended return that compensates for these risks rather than chasing points alone.

Choosing the right operator is as important as choosing assets. Evaluate uptime, incident history, infrastructure redundancy, and security practices. Confirm which AVSs they support, fee schedules, and communication channels for alerts.

• Diversify: Spread restake across multiple operators and AVSs to reduce correlated slashing or downtime risk.
• Set limits: Cap exposure per operator and per AVS; avoid single points of failure.
• Monitor: Use dashboards, on‑chain alerts, and block explorers to track health, rewards, and any slashing events.
• Review regularly: Reassess delegation after upgrades, incidents, or fee changes; document your rationale.

Institutional‑style discipline—position sizing, alerting, and post‑mortems—can materially improve outcomes.

Restaking creates detailed transaction trails: approvals, deposits, delegations, reward claims, and withdrawals. Keep meticulous records to maintain accurate cost basis and to categorize income vs. capital gains.

• Label every step: Export CSVs from your wallet tracker and Etherscan; tag approvals, deposits, claims, and fees.
• Points/airdrops: Treat them per your jurisdiction’s guidance; they may be taxable upon receipt. See the IRS digital asset page.
• Methodology: Consistently apply FIFO/LIFO or specific identification where permitted.
• Documentation: Save operator/AVS terms and snapshots that determine reward eligibility.

This guide is educational and not tax advice. Consult a qualified professional for your region.

Sustainable restaking favors risk‑adjusted returns over hype. Start with a clear plan: define allocation, operator diversification, and liquidity buffers. Add AVSs gradually as you understand their economics and slashing rules.

Automate monitoring, record everything, and revisit decisions quarterly. With disciplined execution, an EigenLayer restaking guide like this becomes a living playbook for compounding yield while protecting principal.

Your edge is consistency: small, reversible decisions made with high information quality.

• Who is eligible to restake? Anyone with supported assets and a compatible wallet. Some AVSs or operators may have allowlists, caps, or KYC requirements.
• How do unbonding and withdrawals work? Expect a waiting period. LST/LRT withdrawals may depend on protocol queues; native ETH uses Ethereum exit/withdrawal mechanics. Timelines vary.
• What are deposit caps and why do they matter? Caps throttle inflows to manage risk and demand. When a pool is full, you must wait for capacity to open.
• Can I change operators later? In most cases, yes, but there may be cooldowns or windows. Check operator and AVS terms before switching.
• Are rewards guaranteed? No. Rewards depend on network conditions, AVS performance, operator uptime, and program terms.
• Regional considerations? Rules differ by country. Review local regulations and taxes; see general resources like Forbes on Ethereum and your government’s tax guidance.
• Is restaking safe? It adds layers of risk. Mitigate with audits, diversification, conservative sizing, and ongoing monitoring.

When in doubt, start small and expand as you gain confidence and data.