> For the complete documentation index, see [llms.txt](https://whitepaper.ivault.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.ivault.io/ivaults-blockchain-ecosystem/architecture.md).

# Architecture

<div align="center"><figure><img src="https://content.gitbook.com/content/hjCvaxZdc84c681KZovd/blobs/T25aiEZrt12jB07QlYGB/Architecture2.png" alt="" width="563"><figcaption></figcaption></figure></div>

**Mobile app**: securely stores identities and wallets of users, so they can interact with the token and the blockchain.

**API resources**: data-centric off-chain storage for the ivault app’s features. Connected to the ivault chain and public networks.

**ivault chain API**: used primarily for all the utilities and features in the ivault app.

**Public networks API**: publicly available tokens on decentralized and centralized exchanges, to boost availability.&#x20;

**Blockchain service layer**: PKI and vault infrastructure for signing and broadcasting transactions. Used with an auto-signature module.

**Off-chain storage**: stores all relevant blockchain information and data needed for features in the app.

**Blockchain Infrastructure Components**: for reading and writing to blockchains.

**Smart contracts**: functional and logical components for the ivault Chain and public networks.

**Blockchain**: decentralized data and execution layer for the ivault Chain and public networks.


---

# 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://whitepaper.ivault.io/ivaults-blockchain-ecosystem/architecture.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.