> 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/admissible-instruments.md).

# Admissible instruments

#### Shares

* **Eligibility**: Shares with a market capitalization (or tentative market capitalization) of less than EUR 500 million.
* **Legal Qualification**: Must represent equity ownership, be transferable, and tradable on capital markets in accordance with MiFID II.
* **Additional Requirements**: Defined in Rulebook section 3.4.

#### Funds

* **Eligibility**: Fund shares classified as UCITS (Undertakings for Collective Investment in Transferable Securities) under Directive 2009/65/EC.
* **Classification**: Deemed as fund units according to Art. 3(1) c) DLTR.
* **AuM Requirement**: Must be below EUR 500 million at the point of admission to trading.

#### Bonds and Other Securitized Debt

* **Eligibility**: Bonds, securitized debt, and money market instruments with an issue size of less than EUR 1 billion.
* **Exclusions**: Instruments that embed a derivative or have complex structures that make it difficult to understand the risk.
* **Additional Requirements**: Defined in Rulebook section 3.5.

#### FAQ

<details>

<summary>Can I list natively tokenized stocks?</summary>

Yes, 21X can list natively tokenized shares (dematerialized shares) as well as digital twins. Digital twins are usually classified as debt instruments (see section 1.3).

</details>

<details>

<summary>Can I list tokenized stocks of blue-chip companies?</summary>

Yes, however, these need to be structured as debt instruments (e.g., exchange-traded notes) and would classify under the listing requirements of bonds and other securitized debt (see section 1.3), thus not falling under the market capitalization restriction for tokenized shares.

</details>

<details>

<summary>What assets are considered shares in the context of these listing requirements?</summary>

Art. 3(1) a) DLTR does not explicitly exclude specific types of shares. The respective national securities laws under which the financial instruments are governed determine if the product is classified as a share or not.

</details>

<details>

<summary>Can the AuM of the Sub-fund grow over EUR 500 million after admission to trading?</summary>

Yes, the AuM of the respective Sub-fund is only relevant at the point of admission.

</details>

<details>

<summary>Can I list ETFs on 21X?</summary>

Yes, 21X can list exchange-traded funds (ETFs) that comply with the framework of UCITS-Regulation. Exchange-traded products (ETPs) classified as notes (ETNs) need to fulfill the requirements of section 1.3 under securitized debt.

</details>

<details>

<summary>Does 21X provide end-to-end services for tokenized funds?</summary>

Yes, asset managers can sub-advise UCITS funds, natively tokenized, distributed, and listed on 21X where 21X will coordinate with partners where necessary.

</details>

<details>

<summary>Does 21X provide end-to-end services for tokenized debt instruments?</summary>

Yes, 21X can set up, distribute, and list tokenized debt instruments in the form of structured notes or ETNs and will coordinate with partners where necessary.

</details>

<details>

<summary>What constitutes a debt that that embed a derivative or have complex structures that make it difficult to understand the risk?</summary>

For the admissibility of complex debt instruments please ask your customer success representative or listing sponsor.

</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/admissible-instruments.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.