> For the complete documentation index, see [llms.txt](https://asterialabs-1.gitbook.io/asteriafi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://asterialabs-1.gitbook.io/asteriafi/genesis/withdrawal-system.md).

# Withdrawal System

## Withdrawal System & Policy

### 1. Withdrawal Mechanism

AsteriaFi processes withdrawals via a weekly batch schedule to secure stable protocol liquidity and mitigate bank-run risks. To ensure absolute data integrity and prevent issues arising from network latency, a **30-minute Safety Buffer** is strictly enforced between each state transition.

### 2. Weekly Operational Timeline

*All times are standardized in UTC.*

* **Monday 12:00 PM | Payout Initiation (`Claimable`)**
  * The Admin Bot injects liquidity into the contract and updates the state of the completed batch to `Claimable`. Users from the processed batch can now claim their funds.
* **Monday 12:00 PM – 12:30 PM | Stability Window (30-Min Buffer)**
  * A dedicated buffer period to await block confirmations and ensure that the contract state updates are fully broadcasted and synchronized across the network.
* **Monday 12:30 PM | New Queue Opening (`Requesting`)**
  * The contract officially re-opens the withdrawal request window for the next subsequent batch.
* **Thursday 12:05 PM | Submission Deadline & Processing (`Cutoff`)**
  * The withdrawal request window for the current batch closes. New withdrawal requests are strictly prohibited from this cutoff time until the opening of the next queue on Monday at 12:30 PM (creating an intentional lock period for processing safety). The protocol enters the `Processing` state to unwind strategies and prepare the requested liquidity.

### 3. Liquidity Buffer & Rollover Policy

* **TVL Protection Cap:** To safeguard the stability of the protocol and protect remaining depositors, a maximum cap of **20% of the total Total Value Locked (TVL)** is available for withdrawals per batch cycle.
* **Excess Request Handling (FIFO):** If total withdrawal requests within a specific cycle exceed this 20% threshold, a **First-In-First-Out (FIFO)** mechanism is strictly enforced based on the request timestamp. Any excess requests that cannot be accommodated within the current cycle's cap will automatically roll over to the next weekly batch.

### 4. Yield & Cancellation Policy

* **Yield Cessation:** To ensure structural and mathematical safety within the smart contract, **yield generation on the requested asset ceases immediately** upon the user completing their withdrawal request. No interest is accumulated while waiting in the queue or during the processing phase.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://asterialabs-1.gitbook.io/asteriafi/genesis/withdrawal-system.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.