Exit Liquidity & Unbonding Delays

Entering a restaking protocol takes seconds, but exiting requires passing through multiple sequential queues designed to prove no rules were broken.

1. Mandatory unbonding delays

When you request a native withdrawal, capital is locked in an escrow delay. This waiting window gives services time to catch and penalize any slashable offenses that happened prior to your withdrawal request.

In a layered system, a withdrawal must clear three sequential stages:

2. Total withdrawal timeline

There is a floor but no ceiling. Stage 1 alone is about fourteen days, because EigenLayer's WITHDRAWAL_DELAY is a single global parameter of 100,800 blocks set by governance, not a per-strategy setting. Stage 2 adds the pooling protocol's own processing on top. Stage 3 adds the validator exit queue, which is rate-limited and whose depth varies continuously, so a total cannot be stated as a range without describing market conditions we deliberately do not track.

EigenLayer's own rationale for fourteen days is worth reading, because it explains where the seven-day figure often quoted for this stage comes from: seven days is the period in which services were said to be able to sync to EigenLayer's view of stake, and the remaining week covers a fraud proof plus the window to cancel an incorrect one. The escrow is not a settlement delay. It is the time a service needs in order to still be able to slash you.

Before redemption is enabled at all, the consequence is sharper than a wait. A receipt with no redemption path has no redeemable value to quote, so the only price anything can read — including the oracles of lending markets holding it as collateral — is whatever its trading pools say. The April 2024 ezETH cascade is the documented case: the thinness of those pools, not the value of the underlying stake, decided who was liquidated.

Sources

1. ELIP-002: Slashing via Unique Stake and Operator Sets — Eigen Foundation. Source for WITHDRAWAL_DELAY at 100,800 blocks, for it being one global parameter set by governance rather than per strategy, for the stake remaining slashable throughout the window, and for the fourteen-day rationale. The protocol's own specification; the parameter table states these are the values used on mainnet.
2. ezETH FAQs — Renzo Protocol documentation. Cited as one pooling protocol's own published figure for a complete withdrawal, which it attributes primarily to the EigenLayer requirement above. One protocol's number, not a general one.