> For the complete documentation index, see [llms.txt](https://taraxa.gitbook.io/taraxa-network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://taraxa.gitbook.io/taraxa-network/native-token-conversion/conversion-status.md).

# Conversion Status

## Where we are in the conversion process

Here's a simple checklist of what has been completed, and what's still pending,&#x20;

* [x] Perform the conversion - completed on April 3, 2023
* [x] Timeframe from exchanges - April 3, 2023, 8AM UTC
* [x] [Security audit report](https://github.com/HalbornSecurity/PublicReports/blob/master/L1%20Audits/Taraxa_Node_EVM_L1_Security_Audit_Report_Halborn_Final.pdf) from Halborn&#x20;
* [x] Stable [Taraxa network](https://explorer.mainnet.taraxa.io/)
* [x] [Exchange integration documentation](/taraxa-network/faq/exchange-integration.md)

## Exchanges supporting the conversion

The following exchanges have either publicly supported or is in the process of getting ready to support Taraxa's native token conversion. If your tokens are on an exchange that has not explicitly supported the conversion then it's best to relocate your tokens into your wallet or a supporting exchange, prior to the conversion.&#x20;

* [x] Kucoin: <https://www.kucoin.com/news/en-kucoin-will-support-the-migration-for-erc20-tara-to-mainnet-tara-tokens-230317>
* [x] Gate: <https://www.gate.io/article/29950>&#x20;
* [x] MEXC: <https://support.mexc.com/hc/en-001/articles/16936276210457>&#x20;
* [ ] AscendEx - received confirmation but no public announcement as of April 26, 2023.&#x20;

The development team will keep reaching out to all exchanges that lists the TARA token to ensure we have maximum participation for the token conversion.&#x20;


---

# 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://taraxa.gitbook.io/taraxa-network/native-token-conversion/conversion-status.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.
