> For the complete documentation index, see [llms.txt](https://future-ai-1.gitbook.io/future-ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://future-ai-1.gitbook.io/future-ai/overview-future-ai/staking/parcels.md).

# Parcels

*The pools are divided into tranches, each with its own unique properties. There are three user-facing tier for LPs to add liquidity and two back-end tier that exist only at the smart contract level to provide LPs with additional optionality when adding liquidity. The risky, high-interest tier (tier A) earns interest according to its principal contribution multiplied by the tier tier's interest multiplier.*

> The *tier*  interest multiplier is standardized to 10.

*As a result, LPs in tier A earn 10 times more interest than they would without the future-AI, similarly LPs in tier AA earn 1/10th of the interest they would normally earn.*

<mark style="color:blue;">TIER AA-></mark> *LPs that add liquidity to tier AA earn less interest, but are covered in the event of a loss of platform risk. This covered capital comes from the principal and interest of the LPs in tier A. LPs in tier AA are awarded 80% of the FUTURE-AI token generation.*

<mark style="color:blue;">TIER A-></mark> *LPs who add liquidity to tier A earn more interest, but lose principal and interest in the event of loss of platform risk. tier A LPs earn 10% of the FUTURE-AI tokens generated per season. FUTURE-AI gains are not included in the first loss coverage for tier AA LPs.*

<mark style="color:blue;">TIER S -></mark> *tier S earns 10% of the FUTURE-AI generated per season. The system uses the S tier to balance the A and AA tier so that they are always in perfect balance with each other, so that the tier interest multiplier is maintained at its exact value. For example, with a tier interest multiplier of 10, the AA:A ratio in a portfolio is always 10:1.*


---

# 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, and the optional `goal` query parameter:

```
GET https://future-ai-1.gitbook.io/future-ai/overview-future-ai/staking/parcels.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.