> For the complete documentation index, see [llms.txt](https://docs.brix.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brix.money/itry/proof-of-reserves.md).

# Proof of reserves

Building trust is critical for any financial system, and especially for onchain asset-backed tokens.

Proof of Reserves exists to provide clear assurance that issued tokens are fully backed. It confirms the existence and authenticity of underlying assets by verifying that the amount of cryptocurrency held matches the amount claimed by the issuer.

To support this, iTRY has partnered with [Accountable Capital](https://www.accountable.capital/) for Proof of Reserves verification. Accountable operates a Data Verification Network (DVN) that enables institutions to share real-time proofs of assets and liabilities without exposing sensitive operational or counterparty data.

Through this setup, Accountable has read-only access to relevant custody locations and can independently verify the status of underlying reserve assets. Using this data, Accountable publishes a public reserves dashboard that allows anyone to review onchain reserve balances and verify the collateralization ratio, ensuring that issued supply remains fully backed.

{% hint style="info" %}
Proof of reserves dashboard will be live on day 1 of official launch.
{% endhint %}


---

# 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.brix.money/itry/proof-of-reserves.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.