> For the complete documentation index, see [llms.txt](https://docs.squads.so/main/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.squads.so/main/additional-resources/sending-assets-to-from-centralized-exchange-cexs.md).

# Sending assets to/from centralized exchange (CEXs)

Each Squads address represents a special account on the Solana blockchain referred to as "PDA". As a result, some exchanges may have limitations in fully supporting asset transfers to or from Squads multisigs, with these restrictions varying by region.

Please refer to the following list if you plan to use Squads frequently with centralized exchanges:

<table><thead><tr><th>Exchange</th><th data-type="checkbox">Receive (from Squads multisig)</th><th data-type="checkbox">Deposit (into Squads multisig)</th></tr></thead><tbody><tr><td>Coinbase </td><td>true</td><td>true</td></tr><tr><td>Binance</td><td>true</td><td>true</td></tr><tr><td>Kraken</td><td>true</td><td>true</td></tr><tr><td>Backpack</td><td>true</td><td>true</td></tr><tr><td>OKX</td><td>true</td><td>true</td></tr><tr><td>Swissborg</td><td>true</td><td>true</td></tr><tr><td>Bybit</td><td>true</td><td>false</td></tr><tr><td>Bitget</td><td>true</td><td>false</td></tr></tbody></table>

{% hint style="warning" %}
Please proceed with caution and test with small amounts whenever you're sending assets to/from a CEX. If you have any questions, please reach out to us on [Discord](https://discord.com/invite/YPXz64TrKs).
{% endhint %}


---

# 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://docs.squads.so/main/additional-resources/sending-assets-to-from-centralized-exchange-cexs.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.