> For the complete documentation index, see [llms.txt](https://docs.zirodelta.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zirodelta.com/trust/commitments.md). # Commitments Rules Zirodelta holds itself to, and how each one can be checked. ## 1. ZDLT supply can never grow Mint and freeze authority are revoked on-chain. **Check:** `mintAuthority` and `freezeAuthority` are empty on [Solscan](https://solscan.io/token/4PX31xRA1BaAyb2Js45ZKYp92VGWGp47yWeVs5CGVKbf). ## 2. No customer funds until proven, audited and reviewed The Yield Engine proves itself on the project's own capital first, on a public address. It accepts customer funds only after an independent security audit and a legal review. **Check:** the [Status](/start-here/status.md) page and the transparency page. Today, no customer funds are pooled. ## 3. Risk sits with the project first The first-loss buffer in the Yield Engine's pool is the project's capital, and it absorbs losses before the main pool. **Check:** published on the transparency page when the pool opens. ## 4. The treasury stays locked until US$11 million The 30,000,000 ZDLT treasury stays locked until ZDLT's fully diluted market value reaches US$11 million. Any outflow before then would require a public post-mortem. **Check:** the treasury wallet on [Solscan](https://solscan.io/account/EaJ4aEKCSJKiLvJMBUMXZcmJp4GFqR5w1B94Xgv17PoW). ## 5. No guaranteed returns Zirodelta does not publish guaranteed rates or fixed returns. Income from any strategy is variable and can be zero or negative. ## 6. We publish the losses When a strategy loses money, the loss is published with receipts before anyone has to find it. ## 7. Honest status Nothing is called live until it is, on the site and in the docs. ## 8. On-chain upgrades are audited before they are switched on New on-chain programs, such as staking or reward accounting, are audited before activation and switched on only after a waiting period announced in advance. Holders are never moved into a new program without their own action. --- # 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.zirodelta.com/trust/commitments.md?ask=&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.