> For the complete documentation index, see [llms.txt](https://help.coinpocket.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.coinpocket.io/transfer-tutorial/copy-of-keyboard-shortcuts/why-cant-transfer-tokens-between-different-chains.md).

# Why can't transfer tokens between different chains?

With the development of public chains, exchanges are also launching their own public chains, such as the Binance Smart Chain (BSC) launched by Binance, the Huobi Eco Chain (HECO) launched by Huobi, and OKExChain launched by OKEx.

The same asset will appear on different public chains due to the increasing demand for cross-chain. For example, USDT can be circulated in ETH, TRX, BSC, HECO, etc., but they are not completely consistent and cannot be transferred directly to each other. Moreover, the address formats of ETH, BSC, HECO, and OKExChain are all the same, which often leads to errors in user transfers or withdrawals.


---

# 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://help.coinpocket.io/transfer-tutorial/copy-of-keyboard-shortcuts/why-cant-transfer-tokens-between-different-chains.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.
