Restake with EigenLayer

How to restake ETH or LSTs into EigenLayer: AVS selection, operator delegation, and slashing risk.

What you'll need (prerequisites)

• Self-custodial wallet (MetaMask, Rabby, etc.)
• ETH or native gas token
• Tokens to restake with
• Familiarity with transaction approvals

Step-by-step

1. Step 1: Connect a self-custodial wallet

   Open EigenLayer's official site (verify the URL — phishing fakes are common). Click "Connect Wallet" and choose your wallet (MetaMask, Rabby, WalletConnect, hardware). Approve the signature request — this does not move funds.

2. Step 2: Select the correct network

   Confirm your wallet is on Ethereum mainnet, where EigenLayer's restaking contracts are deployed. Connecting on the wrong network is a common source of confusion.

3. Step 3: Acquire the input tokens

   Most EigenLayer actions require both a token and ETH (or the chain's native token) for gas. Hold a small buffer (~$10-20) for transaction fees.

4. Step 4: Approve token spend

   For ERC-20 tokens, the first interaction requires an "approve" transaction granting EigenLayer permission to move that token. Approve the exact amount (not unlimited) when possible to limit downside if EigenLayer is ever exploited.

5. Step 5: Execute the restake transaction

   Enter the amount to restake, review the transaction details, then click confirm and approve in your wallet. Wait for on-chain confirmation.

6. Step 6: Verify on-chain

   Open the transaction on Etherscan / Arbiscan / Basescan. Confirm the balance change matches expectations. Save the transaction hash for tax records.

Common errors and fixes

• Transaction reverted. Most reverts are slippage exceeded, allowance not set, or insufficient gas. Increase slippage marginally and retry, or check Tenderly for the revert reason.
• Stuck pending transaction. Speed up with a higher gas price (replace-by-fee) or cancel by sending a 0-value tx to yourself with the same nonce and higher gas.
• Approved a malicious contract. Immediately revoke at revoke.cash. Move remaining tokens to a fresh wallet if you suspect ongoing compromise.
• Wrong network. Switch chains in your wallet. If funds were sent cross-chain to a contract that doesn't exist on the destination, contact the bridge support.
• Slippage too high. For thin-liquidity tokens, split the swap into smaller chunks or route via an aggregator (1inch, CoW Swap, Matcha) which finds better paths.

Restaking is not staking — what you are actually agreeing to

Native Ethereum staking has one slashing authority: the Ethereum protocol, with rules fixed in the consensus specification. Restaking has many. On EigenLayer you deposit ETH or liquid-staking tokens, delegate to an operator, and that operator opts into operator sets defined by Actively Validated Services (AVSs). Each AVS writes its own slashing conditions and, once your stake is allocated to its operator set, holds the right to slash it. Your risk is therefore the union of every AVS your operator has allocated to — which is a fundamentally different thing from the single, well-understood risk of a beacon-chain validator.

Withdrawal escrow: 14 days, still slashable

Exiting is a two-step process. You call queueWithdrawal, wait out the escrow, then call completeQueuedWithdrawal. On mainnet MIN_WITHDRAWAL_DELAY_BLOCKS is 100,800 blocks — 14 days, a figure that was increased to this length with the slashing upgrade.

The detail that matters: shares sitting in the withdrawal queue remain slashable. The contracts record scaled shares against the operator's slashing history, and on completion recompute the operator's slashing factor and apply anything that happened during the wait before releasing assets. Queueing a withdrawal is not an escape from an in-flight incident. If you are restaking natively through an EigenPod, the beacon-chain exit queue and withdrawal sweep stack on top of the 14 days.

Allocation and deallocation delays

• ALLOCATION_CONFIGURATION_DELAY: 126,000 blocks (~17.5 days) on mainnet. When an operator allocates stake to a new AVS operator set, the change takes effect only after this delay — deliberately giving delegated stakers time to withdraw before their risk profile changes.
• DEALLOCATION_DELAY: 100,800 blocks (~14 days) on mainnet. Removing stake from an operator set does not remove slashability immediately; it stays slashable through the delay so an operator cannot deallocate its way out of a pending penalty.

Operators configure their own allocation delay and may set it to zero. An operator with a zero delay can change what your stake is exposed to with no warning window — check this field before delegating.

Slashing magnitude: up to 100%

EigenLayer slashing is proportional and AVS-triggered. When an AVS slashes, it specifies wadsToSlash between 0 and 1e18, where 1e18 represents 100% of the operator's allocated magnitude for that strategy. There is no protocol-level cap analogous to Ethereum's modest base penalty: the ceiling is whatever the AVS's contract permits, up to everything allocated. Before delegating, read the specific slashing conditions of the AVSs in your operator's sets, and how much magnitude is allocated to each.

Minimums and how to choose an operator

There is no protocol minimum for restaking liquid-staking tokens into a strategy — you can deposit small amounts, subject to gas economics. Native restaking is different: it requires a full 32 ETH beacon-chain validator whose withdrawal credentials point at your EigenPod, plus periodic checkpoint proofs to keep the pod's accounting in sync.

• Which operator sets is the operator registered to? This, not the operator's branding, defines your slashing surface.
• How much magnitude is allocated per AVS? Concentrated allocation to one aggressive AVS is a different bet than thin allocation across several.
• What allocation delay have they configured? Zero means no warning window.
• Operational track record. Uptime, incident history, key management, redundancy.
• Fee, and how rewards are passed through. AVS rewards may be paid in AVS tokens rather than ETH.

Liquid restaking tokens

If you do not want to pick operators and AVSs yourself, liquid restaking tokens do it for you: ether.fi (eETH/weETH), Renzo (ezETH), Kelp DAO (rsETH) and Puffer (pufETH) all issue a receipt token representing a restaked position that stays usable in DeFi. They give you an exit through a DEX rather than the 14-day escrow, and they add layers: the LRT contract itself, its operator selection, and the receipt token's market price, which can trade below fair value under stress. You are stacking Ethereum staking risk, EigenLayer slashing risk and LRT protocol risk to earn a yield that is largely variable and not contractually guaranteed.

Risks and troubleshooting

• Withdrawal completed for less than expected. Slashing that occurred during the escrow is applied at completion — this is by design.
• Risk profile changed without notice. Your operator configured a short or zero allocation delay. Undelegating still requires the 14-day escrow.
• Native restaking balance looks wrong. EigenPod accounting depends on checkpoint proofs; if they are stale, the pod's recorded balance lags the beacon chain.
• Yield lower than headline numbers. AVS rewards are variable, often paid in AVS tokens, and points programmes are not yield.
• Correlated exposure. An LRT, its underlying LST and EigenLayer itself can fail together. Do not treat a diversified-looking basket of LRTs as diversification.
• Stale approvals. Revoke unused token approvals after depositing.

FAQ

Sources

Every protocol parameter above is taken from official documentation or specifications. Staking parameters are changed by governance and protocol upgrades — verify against the live chain before committing size.

• eigenlayer-contracts — AllocationManager (allocation and slashing delays)
• eigenlayer-contracts — DelegationManager (withdrawal delay)
• EigenCloud docs — Safety delays reference
• EigenCloud docs — Native ETH restaking withdrawal delays