An eigen layer withdrawal stays pending through a protocol escrow delay, then needs a separate completion transaction to reach your wallet. The eigen layer queue does not release funds automatically; EigenLayer permits completion only after the delay. Native ETH also requires a Beacon Chain exit and proof to the EigenPod before it can be paid out.
What Does an eigen layer Withdrawal Status Tell You?
The status tells you which action is possible. Queueing removes shares from your active stake balance and records a withdrawal with a starting block. Because an app may call every unclaimed withdrawal “pending,” use its detail view or block-based countdown to separate these stages:
- Queued: The queue transaction has confirmed, but escrow is still running. The countdown has blocks left, and a completion attempt would be too early. Wait.
- Completable: The required blocks have passed. The withdrawal remains in the queue, but the app can offer a Complete or Withdraw action. For an LST withdrawal, submit the completion transaction with the wallet that queued it.
- Completed: The completion transaction has confirmed and removed the queue entry. If you chose to receive tokens, the LST or ETH transfer should now be visible on-chain.
A successful queue transaction proves the request was recorded, not that a payout was sent. If the app's label looks stale, the queue transaction's starting block and the completion transaction history provide stronger evidence than the label.
Why Has the Countdown Ended Without a Wallet Transfer?
The countdown ending makes a withdrawal eligible; it does not claim it. Imagine queueing an LST withdrawal, seeing “zero blocks remaining,” and leaving the tab open for another week. No completion transaction was sent, so the assets stay in the queue. Once Complete is available, submit it, confirm it in your wallet, and wait for its on-chain confirmation.
The protocol measures its escrow delay as a fixed number of Ethereum blocks from the queue transaction. Apps may express those blocks as days, but the calendar estimate can shift with block production. The delay lets slashing of an operator securing Actively Validated Services be accounted for before funds leave. Queued shares stop earning restaking rewards, yet remain slashable during escrow; the amount received can therefore be lower than the amount shown when you queued.
If a completion attempt reverts or you reject it in your wallet, the withdrawal remains uncompleted. Resolve the displayed error and try again when its conditions are met; merely waiting after the countdown has ended will not transfer the assets.
What Changes for Native ETH?
Native ETH needs available ETH in the EigenPod as well as an elapsed protocol delay. A native restaker's validator holds ETH on the Beacon Chain, while the EigenPod is the contract named in that validator's withdrawal credentials. If the validator has not fully exited, the pod may have no ETH to send even after the withdrawal countdown reaches zero.
A full validator exit enters the Beacon Chain exit queue, whose length varies with network demand. The Beacon Chain then pays the ETH to the EigenPod. A checkpoint proof updates the pod's accounted balance so ETH becomes withdrawable. Thus the elapsed escrow countdown answers only the protocol timing question; it does not show whether the exit and pod accounting are finished. The total wait can include the fixed protocol delay and the variable Beacon Chain exit, which need not begin together.
If the pod lacks proven, withdrawable ETH, wait for the exit to land and complete its EigenPod checkpoint before trying to receive ETH. This boundary does not apply to an LST withdrawal: that path returns the liquid staking token without a validator exit through your EigenPod.
What Should You Do Next?
Match the pending entry to the wallet that queued it, its asset, and its remaining blocks. For an LST entry with blocks left, wait. With no blocks left, use the app's completion action, choose to receive the token, and sign the separate transaction. If your wallet interface does not display the LST after confirmation, inspect the token transfer on-chain before queueing anything else.
For native ETH, also inspect the validator's exit status and the EigenPod's proven, withdrawable balance. If the exit or proof is outstanding, finish that step before expecting ETH in your wallet. If both are ready, complete the queued withdrawal. The practical rule for EigenLayer is to wait while escrow or the native exit is unfinished, act when the withdrawal is completable and funded, and call it completed only after the completion transaction confirms.
Top comments (0)