> For the complete documentation index, see [llms.txt](https://docs.hiyield.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hiyield.xyz/components/offchain-infrastructure.md).

# Offchain infrastructure

Our offchain infrastructure has 4 key components:

* **Stablecoin offboarding**: This is used to convert between fiat <> stablecoins.
* **Banking:** This is used to receive the fiat currency from the stablecoin offboarding provider
* **Custodian**: This is where all offchain assets are stored, including unspent fiat currency
* **Broker Dealer:** This is how we procure all offchain assets, such as equity and fixed-income products

The flow of funds typically works as follows:

1. HiYield borrows stablecoins from an onchain pool and sends to the stabelcoin offboarding partner
2. The offboarding partner wires fiat currency to our banking partner
3. Our banking partner wires fiat currency with additional instructions to a specific trust at the custodian
4. We contact the broker dealer to execute a trade
5. The trade is settled between the broker dealer and the custodian


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hiyield.xyz/components/offchain-infrastructure.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
