Renzo Protocol
  • Overview
  • Restaking Platforms
    • Understanding EigenLayer
      • Ecosystem
      • Operators
      • Actively Validated Services
    • Understanding Symbiotic
    • Understanding Jito
  • Renzo
    • Understanding Liquid Restaking
    • $ezETH
      • $ezETH FAQs
    • $pzETH
      • $pzETH FAQs
    • $ezSOL
    • $bzSOL
    • $ezJTO
    • $REZ
      • Season 1
      • Season 2
      • Season 3 (Amore)
      • Season 4
      • Post Season 4
      • REZ Tokenomics
      • $REZ FAQs
    • $ezREZ
    • $ezEIGEN
  • Product
    • Restake
    • Withdrawals
      • Withdrawal Flow
      • Withdrawal Queue
      • Instant Withdrawals
      • Tutorial
      • Withdrawals FAQs
    • Renzo ezPoints
      • Season 4 Claims
    • How We Do It
    • Renzo FAQs
      • Layer 2
      • DEX
      • Dev
      • APY Calculations
  • Governance
    • Governance
      • Discussion
      • Voting
  • Integrations
    • DeFi
    • L2 Native Restaking
  • Bridge
  • Contracts
    • Ethereum Mainnet
    • Layer 2s
      • Arbitrum
      • Base
      • Blast
      • BNB Chain
      • Mode
      • Linea
      • Fraxtal
      • Taiko
      • Zircuit L2
      • Swellchain
      • Berachain
      • Unichain
    • Solana Mainnet
    • Sei Mainnet
    • Source Code
  • Legal
    • Terms of Service
    • Disclaimer
    • Terms of Service REZ Claim
    • Terms of Service EIGEN Claim
    • Privacy Policy
  • Security
    • Audits
    • Bug Bounty
  • Resources
    • Brand Kit
Powered by GitBook
On this page
  1. Product
  2. Withdrawals

Withdrawal Queue

PreviousWithdrawal FlowNextInstant Withdrawals

Last updated 5 months ago

If the current buffer capacity is not large enough to accommodate a user’s balance, they can request to be added to the withdrawal queue. Once a request is added to the withdrawal queue, Renzo Protocol unstakes funds from both EigenLayer and the Ethereum beacon chain to make available for the user.

The withdrawal queue works on a first come first serve basis - requests are fulfilled in the order in which they were received. E.g. if one user requests 100 ETH, and the next user requests 50 ETH, the user who requested 100 ETH will receive their collateral first. Queued withdrawal requests receive priority over refilling the buffer capacity, so any incoming deposits, rewards, and unstaked collateral will be allocated to the withdrawal queue.

In extreme cases, it may take up to 10 days after queuing a withdrawal before a user receives their collateral to begin the cooldown period. This is determined by the time to exit the Ethereum Beacon Chain and EigenLayer (see below).

  1. Exiting the Ethereum Beacon Chain - Can vary from a day to 8.9 days or more as of this writing (Exit Queue + Sweep Delay).

  2. Exiting EigenLayer - All funds unstaked from EigenLayer are required to go through a 7 day escrow period before being eligible to be fully withdrawn.

The implementation of the withdrawal queue feature does not change the operation detailed in the document. The withdrawal queue is an additional feature that is used only when the amount that a user requests to withdraw is greater than the current balance available in the buffer capacity.

https://www.validatorqueue.com/
https://docs.eigenlayer.xyz/eigenlayer/restaking-guides/restaking-user-guide/liquid-restaking/withdraw-from-eigenlayer
Withdrawal Flow