> 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/token-requirements.md).

# Token Requirements

#### General Token Requirements

* Tokens must be deployed on supported DLT networks: **Polygon PoS, Stellar Network, or Solana** (in preparation).
* Smart contracts must be audited or use widely audited code (e.g., OpenZeppelin).
* Tokens must not disrupt trading or settlement processes.

#### Technical Requirements by Network

* **Polygon PoS**: Tokens must adhere to the ERC-20 standard.
* **Stellar Network**: Tokens must implement the SEP-41 interface.
* Further EVM and non-EVM chains will be enabled soon. 

#### **FAQ**

<details>

<summary>Can a token listed on 21X be freely transferable?</summary>

Yes, but the issuer must ensure compliance with applicable laws and regulations.

</details>

<details>

<summary>Does the token require admin rights (e.g., clawback, burn &#x26; re-issue)?</summary>

No, from a technical standpoint, the minimum token requirements such as ERC-20 compatibility (Polygon PoS) or SEP-41 compatibility (Stellar Network) need to be met. The issuer must ensure compliance with applicable laws and regulations.

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