> 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/governance-council/protocol-fees/listing-fees.md).

# Listing fees

Ledgity allows DAOs, funds, protocols, and asset managers to **list their own yield vaults** on the platform, benefiting from:

* On-chain infrastructure (vault factory, accounting, withdrawals buffer, etc.)
* Institutional-grade reporting and risk monitoring
* Integrated DeFi routing (DEX LP, staking boosts, aggregator indexing)
* Distribution to Ledgity’s community, partners, and whitelist

To ensure **seriousness, sustainability, and security**, vault listing requires a **listing commitment**.

***

### **Why Listing Fees Exist**

Listing a vault requires:

* Legal & regulatory verification
* Risk and compliance review
* On-chain & off-chain integration work
* Liquidity planning + operational monitoring
* UI/UX implementation + distribution support

This ensures that **every vault listed** on Ledgity is:

✔ Compliant\
✔ Audited or reviewable\
✔ Aligned with long-term sustainability\
✔ Meaningful in scale and reputation

***

### **Vault Listing Models**

Projects can choose between two listing models:

| Model                   | Requirement                                                                         | Suitable For                        | Key Benefits                                               |
| ----------------------- | ----------------------------------------------------------------------------------- | ----------------------------------- | ---------------------------------------------------------- |
| **Flat Listing Fee**    | **€XX XXX** setup fee                                                               | Institutions, funds, asset managers | Fast integration, branded vault, regulatory support        |
| **LDY-Aligned Listing** | Commit a portion of vault liquidity in **lyUSDC / LDY** (minimum threshold applies) | DAOs, protocols, DeFi teams         | Shared incentives + boosted visibility + zero upfront cost |

Both models ensure **reciprocal alignment** between the vault operator and the protocol.

***

### **Value Provided to Listing Partners**

| Benefit                         | Description                                                                |
| ------------------------------- | -------------------------------------------------------------------------- |
| On-Chain Vault Factory          | Your strategy deployed via audited production infrastructure               |
| Liquidity Buffer Integration    | Instant withdrawals for your users                                         |
| Dune + Reporting Tools          | Institutional-grade reporting dashboards                                   |
| White-Label & Multi-Language UI | Optional branded frontends                                                 |
| Institutional Onboarding Suite  | KYC/KYB support for corporate clients                                      |
| DeFi Distribution               | Exposure through Base, Arbitrum, Sonic, Ethereum, Linea, Hedera ecosystems |

Ledgity acts as an **infrastructure layer**, not as a strategy originator — your vault remains **your vault**.

***

### **Alignment Mechanism**

To be listed, a vault **must benefit the broader ecosystem**, meaning:

* It must **not create systemic liquidity risk**
* It must be **transparent and auditable**
* It must contribute to **protocol growth & token value capture**

In short:\
**If the vault helps everyone win — it qualifies.**


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ledgity.finance/governance-council/protocol-fees/listing-fees.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.