> For the complete documentation index, see [llms.txt](https://eosi-finance-1.gitbook.io/eosi-finance-documentations/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eosi-finance-1.gitbook.io/eosi-finance-documentations/eosi-finance/5.-architecture-of-the-eosi-finance-ecosystem/5.6-funding-pools-trader-access-and-protection-layers/5.6.1-liquidity-providers-supplying-capital.md).

# 5.6.1 Liquidity Providers – Supplying Capital

* **Deposits and Minting:** LPs deposit stablecoins into the Funding Pool smart contract. In exchange, the contract mints fTokens representing their proportional claim on the pool. This design mirrors the way DeFi protocols like Aave issue aTokens to depositors, which represent a pro‑rata share of the pool and accrue interest.
* **Redemption and Tranche Vaults:** LPs can redeem fTokens at any time (subject to pool conditions) to withdraw their principal plus earned yield. EOSI Finance offers Tranche Vaults so that LPs can select risk profiles: \
  the **Safe Vault** prioritises capital preservation with conservative allocations; \
  the **Growth Vault** pursues higher yields with more aggressive trader cohorts; and \
  the **Hybrid Vault** blends both approaches. \
  Diversification across multiple trader accounts reduces concentration risk.
* **KYC Flexibility:** By default, EOSI Finance’s vaults are permissionless and do not require KYC. This mirrors the seamless, non‑custodial nature of DeFi lending platforms, where users lend and borrow without identity checks. Optional whitelisted vaults can be introduced for institutional LPs who require regulatory compliance. Even in KYC‑enabled vaults, EOSI Finance does not custody user funds; third‑party providers handle verification and funds remain on‑chain.


---

# 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://eosi-finance-1.gitbook.io/eosi-finance-documentations/eosi-finance/5.-architecture-of-the-eosi-finance-ecosystem/5.6-funding-pools-trader-access-and-protection-layers/5.6.1-liquidity-providers-supplying-capital.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.