> For the complete documentation index, see [llms.txt](https://docs.ledgity.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ledgity.finance/vaults/how-vaults-are-listed-future-vaults.md).

# How Vaults Are Listed / Future Vaults

Ledgity is designed to support multiple yield strategies over time.\
While the protocol currently offers **lyUSDC** and **lyEURC**, additional vaults may be listed when they provide:

* **Clear and predictable yield**
* **Regulated or verifiable asset backing**
* **Proper liquidity management**
* **Alignment with the protocol and DAO**

New vaults are not added casually.\
They must strengthen the ecosystem — not dilute it.

***

#### **Vault Listing Requirements**

To list a new vault on Ledgity, three criteria must be met:

| Requirement                    | Description                                                                                      |
| ------------------------------ | ------------------------------------------------------------------------------------------------ |
| **Transparency**               | The underlying strategy must have clear performance, liquidity schedules, and risk documentation |
| **Operational Reliability**    | The asset manager must demonstrate operational maturity and reporting capability                 |
| **Alignment with Ledgity DAO** | Value must flow back into the ecosystem through LDY incentives or strategic participation        |

This ensures vaults are **sustainable**, **auditable**, and **not dependent on speculative yield**.

***

#### **Integration Models**

There are **two ways** for partners to launch vaults on Ledgity:

**Model A — Fixed Setup + Performance Alignment**

For teams, funds, and asset managers who want direct onboarding:

| Component                 | Amount                   |
| ------------------------- | ------------------------ |
| **Setup Fee**             | 50k $                    |
| **Performance Fee Share** | **0.5% of TVL annually** |

This model is best suited for **institutional partners** and **RWA-native managers**.

***

**Model B — Strategic Alignment Through LDY Participation**

Instead of paying setup fees, partners may **participate in protocol alignment** by:

| Commitment                                               | Mechanism                                                     |
| -------------------------------------------------------- | ------------------------------------------------------------- |
| **Holding / Staking LDY**                                | Demonstrates long-term interest and ensures shared incentives |
| **Providing part of vault liquidity in lyUSDC / lyEURC** | Strengthens protocol liquidity and risk-sharing               |
| **Maintaining a minimum TVL threshold**                  | Ensures meaningful contribution to the ecosystem              |

This model is best suited for:

* DAOs
* Crypto funds
* On-chain asset managers
* Ecosystem partners

> The goal is **win–win alignment**, not extraction.

***

#### **Why Alignment Matters**

Each vault added to Ledgity:

* **Attracts new users**
* **Deepens protocol liquidity**
* **Strengthens LDY value capture**
* **Expands RWA access for the whole ecosystem**

Therefore, **vault listings must benefit all stakeholders**, not just the vault originatorl

***


---

# 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://docs.ledgity.finance/vaults/how-vaults-are-listed-future-vaults.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.