> For the complete documentation index, see [llms.txt](https://docs.21x.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.21x.eu/participant-docs/listing-requirements/stablecoin-requirements.md).

# Stablecoin Requirements

Guidelines for e-money tokens used as settlement currencies on 21X, including compliance, technical specifications, and supported networks.

#### General Stablecoin Requirements

* Stablecoins must comply with Regulation (EU) 2023/1114 (MiCA).
* Must include a whitelist/blacklist system to block sanctioned entities.
* Must be deployed on supported DLT networks: **Polygon PoS, Stellar Network, or Solana** (in preparation).

#### Technical Requirements by Network

* **Polygon PoS**: Must adhere to the ERC-20 standard and support 6 decimal places.
* **Stellar Network**: Must implement the SEP-41 interface.
* Further EVM and non-EVM chains will be enabled soon.

#### **FAQ**

<details>

<summary>Can a stablecoin/e-money token listed on 21X be freely transferable?</summary>

Yes, free transferability is recommended, with a blacklist function preferred for compliance.

</details>

<details>

<summary>What protocols does 21X support?</summary>

21X currently supports Polygon PoS and Stellar Network. Further network support is in preparation.

</details>


---

# 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.21x.eu/participant-docs/listing-requirements/stablecoin-requirements.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.
