> 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/technical/collateral-management.md).

# Collateral Management

iTRY uses a combination of an onchain vault and a regulated custody provider to manage collateral.

The majority of collateral is secured by [Zodia Custody](http://zodia-custody.com/), a licensed 3rd party custodian, where it benefits from institutional security controls, operational safeguards, and established risk-management practices. A limited portion is held onchain in the Fast Access Vault smart contract to support instant redemptions.

This hybrid custody model is designed to balance usability and security. The Fast Access Vault facilitates instant redemption and ensures a portion of collateral remains available in the rare event of custodial downtime, while regulated custody supports controlled settlement for larger redemptions and provides institutional-grade operational rigor.

This design allows routine redemptions to settle instantly while ensuring that higher-value redemptions remain fully supported by regulated custody infrastructure.


---

# 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/technical/collateral-management.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.