# Technical Guide: Liquidity Pool Earnings (TVL)
### Liquidity Pool Overview
The Liquidity Pool (TVL - Total Value Locked) is a fundamental mechanism of the network protocol designed to ensure market depth, absorb volatility, and maintain operational efficiency. Users who contribute their own volume to the pool participate directly in the economic results generated by the real economic activity of the system, not through passive capital entry.
### Pool Functions
The liquidity pool serves four essential functions within the ecosystem:
**Market Depth Guarantee**: Ensures sufficient liquidity is available for transactions, preventing slippage and maintaining stable pricing across the network.
**Volatility Absorption**: Acts as a buffer against market fluctuations, protecting the stability of the protocol and user positions.
**Operational Efficiency**: Enables smooth execution of transactions and network operations without interruption or delay.
**Economic Result Participation**: Pool contributors receive a direct share of the economic results generated by the system's real operational activity.
### Return Structure and Distribution
Liquidity pool returns are directly linked to the real economic activity of the system, not to passive capital contribution. The platform distributes earnings automatically every 5 days directly to user wallets, ensuring consistent and transparent compensation.
The return structure varies based on the holding period, with higher returns for longer commitment periods. This incentivizes sustained participation in the pool and aligns user interests with network stability.
### Return Schedule by Period
| Period | Monthly Return | Daily Average |
| -------- | -------------- | ------------- |
| 1 day | 0.1% | 0.1% |
| 5 days | 1% | 0.2% |
| 30 days | 9% | 0.3% |
| 90 days | 15% | 0.5% |
| 180 days | 18% | 0.6% |
| 360 days | 24% | 0.8% |
### Automatic Distribution Mechanism
Earnings enter user wallets automatically every 5 days without requiring manual claims or additional actions. This automated distribution ensures that returns compound efficiently and users maintain continuous access to their earned capital. The system processes distributions in batches, crediting all eligible participants simultaneously.
### Return Calculation Examples
**Example 1 - 90-Day Period:**
A user deposits 1,000 USDT into the liquidity pool for a 90-day period. Based on the return structure of 15% per month, they will receive approximately 150 USDT per month. Earnings are distributed automatically every 5 days directly to the user's wallet, totaling approximately 25 USDT per distribution cycle (15% ÷ 6 cycles of 5 days = approximately 2.5% per cycle). At the end of 90 days (3 months), the total accumulated return will be 450 USDT, representing a 45% return on the initial capital.
**Example 2 - 360-Day Period:**
A user maintains 1,000 USDT in the liquidity pool for a 360-day period. Based on the return structure of 24% per month, they will receive approximately 240 USDT per month. Earnings are distributed automatically every 5 days directly to the user's wallet, totaling approximately 40 USDT per distribution cycle (24% ÷ 6 cycles of 5 days = approximately 4% per cycle). At the end of 360 days (12 months), the total accumulated return will be 2,880 USDT, representing a 288% return on the initial capital.
### Transparency and Tracking
Users can monitor their pool contributions and earnings in real-time through the dashboard. Each wallet displays:
* Current volume locked in the pool
* Accumulated earnings to date
* Next distribution date
* Projected total returns based on the selected period
* Historical distribution records
---
# 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://cryptocast.gitbook.io/cryptocast-docs/technical-guide-liquidity-pool-earnings-tvl.md?ask=
```
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.