> For the complete documentation index, see [llms.txt](https://know.rendernetwork.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://know.rendernetwork.com/general-render-network/rndr-to-render-what-you-need-to-know/central-exchanges-rndr-to-render-upgrades.md).

# Central Exchanges RNDR to RENDER Upgrades

Exchanges upgrading RNDR to RENDER for users.

With the ongoing upgrade from RNDR (ETH) to RENDER (SOL) as [voted by the community in RNP-002](https://github.com/rendernetwork/RNPs/blob/main/RNP-002.md), exchanges are announcing their plans to upgrade.&#x20;

All exchanges are announcing their plans. Here is the Kracken statement, which is succinctly put: \
\
*On July 29, 2024, Kraken will begin migrating RNDR from the Ethereum Blockchain to RENDER, on the Solana blockchain. Kraken will subsequently delist RNDR and list RENDER. RNDR tokens will be converted to RENDER tokens at a 1:1 ratio.*&#x20;

A list of exchanges and their plans:&#x20;

* [Coinbase announced support of RENDER](https://twitter.com/CoinbaseAssets/status/1758185744521154798), but did not upgrade users.
* [Binance is upgrading all users from RNDR to RENDER automatically](https://www.binance.com/en/support/announcement/binance-will-support-the-render-rndr-token-swap-and-rebranding-to-render-render-d1f2ae8d99b24439a7a900caa9bb6b3b?hl=en).
* [OKX is upgrading all users from RNDR to RENDER automatically](https://www.okx.com/help/okx-to-support-rndr-token-migration).
* [Kraken is upgrading all users from RNDR to RENDER automatically.](https://x.com/krakenpro/status/1811060916156285034?s=46\&t=f3sjT4xADOJ47qrgONI4aA)
* [HTX is upgrading all users from RNDR to RENDER automatically](https://www.htx.com.cm/support/74974397538634).
* [MEXC is upgrading all users from RNDR to RENDER automatically.](https://www.mexc.com/support/articles/17827791517241)
* [Crypto.com is upgrading all users from RNDR to RENDER automatically.](https://x.com/cryptocom/status/1811385295272825266?s=46\&t=f3sjT4xADOJ47qrgONI4aA)
* [Bitvavo is upgrading all users from RNDR to RENDER automatically.](https://bitvavo.com/nl/blog/rndr-render)
* [Bitget is upgrading all users from RNDR to RENDER automatically.](https://www.bitget.com/support/articles/12560603812822)
* [Kucoin is upgrading all users from RNDR to RENDER automatically.](https://x.com/kucoincom/status/1818632708941341135?s=46\&t=f3sjT4xADOJ47qrgONI4aA)
* [Bybit is upgrading all users from RNDR to RENDER automatically.](https://announcements.bybit.com/article/bybit-to-support-render-rndr-token-swap-and-rebranding-to-render-render--blt1fffcc692a611113/)
* [Phemex is upgrading all users from RNDR to RENDER automatically.](https://phemex.com/announcements/phemex-will-support-the-render-rndr-token-swap-and-rebranding-to-render-render-on-july-16-2024)
* [CoinDCX is upgrading all users from RNDR to RENDER automatically.](https://info.coindcx.com/announcement/render-rndr-token-swap-and-rebranding-to-render-render/)
* [Gate.io is upgrading all users from RNDR to RENDER automatically.](https://www.gate.io/announcements/article/37795)
* [IXFI is upgrading all users from RNDR to RENDER automatically.](https://x.com/ixfiexchange/status/1813937014820962621)
* [WhiteBit is upgrading all users from RNDR to RENDER automatically.](https://x.com/WhiteBit/status/1814307426469822515)


---

# 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://know.rendernetwork.com/general-render-network/rndr-to-render-what-you-need-to-know/central-exchanges-rndr-to-render-upgrades.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.
