# Withdrawals

The withdrawal feature allows users to claim underlying collateral in exchange for their ezETH. The withdrawal process is managed by a contract called WithdrawQueue. This contract has two main configurable parameters:

1. Buffer Capacity: The amount of collateral available for withdrawal at any given time.
2. Cooldown Period: The time it takes for the value to be released to the user after initiating a withdrawal.

The WithdrawQueue contract holds the value that users can claim. When a user initiates a withdrawal, the ezETH gets locked in the WithdrawQueue contract which then gets burned at the time of claim in exchange for the underlying collateral asset.

Withdrawing funds involves multiple time delays: 

* Beacon chain exit time is between 9-10 days (see [Sweep Delay](https://www.validatorqueue.com/))
  * This is a result of Ethereum network conditions
* EigenLayer’s minimum withdrawal delay is set to 14 days
  * This is to protect restakers from malicious actors attempting to front-run slashing events
* Renzo’s WithdrawQueue buffer delay is set to 3 days
  * This is based on security recommendations via our partners and auditors

If the WithdrawalQueue buffer has assets, the expected wait time is **7 days** and if empty, the expected wait time is between **10-15 days**

Safety around the withdrawal feature is critical and of the utmost importance, as it involves the movement of actual value out of the protocol. The Renzo team has been hard at work ensuring that the contracts are safe. View our audits here: [`https://docs.renzoprotocol.com/docs/security/audits`](https://docs.renzoprotocol.com/docs/security/audits)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.renzoprotocol.com/docs/services/withdrawals.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.