> For the complete documentation index, see [llms.txt](https://remittix-organization.gitbook.io/remittix-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://remittix-organization.gitbook.io/remittix-whitepaper/10.1-digital-assets.md).

# 10.1 Digital Assets

The Remittix PayFi model is not dependent on a single cryptocurrency.

Different users hold different forms of digital value, and the platform is intended to accommodate a range of supported assets over time.

These can include major cryptocurrencies, stablecoins, and other blockchain-based assets that meet the technical, liquidity, and compliance requirements of the payment infrastructure.

Stablecoins are particularly well suited to payments because their value is designed to remain relatively stable against a fiat currency. Assets such as USDT and USDC can therefore provide a useful bridge between blockchain liquidity and conventional payment settlement.

Other assets such as BTC and ETH can also be used as a source of value where the required conversion infrastructure is available.

The role of Remittix is not to require users to hold one specific payment asset.

The broader objective is to allow users to begin with the digital asset they already hold and complete the payment in the fiat currency required by the recipient.


---

# 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://remittix-organization.gitbook.io/remittix-whitepaper/10.1-digital-assets.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.