> 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/verify-us.md).

# Verify us

Financial systems deserve evidence. Anything Zirodelta says about supply, reserves or status should be checkable by you.

## What you can check today

* **ZDLT supply, mint authority and freeze authority** on [Solscan](https://solscan.io/token/4PX31xRA1BaAyb2Js45ZKYp92VGWGp47yWeVs5CGVKbf).
* **The ZDLT treasury wallet** on [Solscan](https://solscan.io/account/EaJ4aEKCSJKiLvJMBUMXZcmJp4GFqR5w1B94Xgv17PoW).
* **Module status** on the [Status](/start-here/status.md) page and on zirodelta.com.

## The transparency page

[zirodelta.com/transparency](https://zirodelta.com/transparency) publishes the engine's proof of reserves: the public addresses, the attested net asset value and the supply checks. Today it shows that no data is live yet, because no part of the engine is live.

As each part goes live, its addresses are published there so you can check every figure against the chain. The page is published by Zirodelta. It is not an audit or attestation by an independent accountant.

## How to check a figure

1. Open the address from the transparency page in the explorer it links to.
2. Compare the balance or position there with the figure on the page.
3. If they do not match, tell us on Discord. We will explain or correct it in public.


---

# 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/verify-us.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.