> For the complete documentation index, see [llms.txt](https://dexsport-3.gitbook.io/dexsport-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dexsport-3.gitbook.io/dexsport-docs/wallet-and-payments/networks-and-coins.md). # Supported networks and coins Dexsport supports deposits and withdrawals across **26 blockchain networks**, plus **Binance Pay** as a separate payment method. Many coins, USDT and USDC in particular, exist on several chains at once, which is why the number of coin and network combinations is far higher than the number of networks. ## The networks Bitcoin, BNB Chain, Tron, TON, Ethereum, Polygon, Arbitrum, Avalanche, Solana, Litecoin, Dash, Bitcoin Cash, Dogecoin, Base, OKC, Metis, Boba, Linea, Ripple (XRP), opBNB, Chiliz, HyperEVM, Optimism, Monero, Sui, and Robinhood. **Binance Pay** sits in the same selector but is not a blockchain network. You pay from your Binance account, the money arrives instantly, it works with USDT only, and the minimum is $1. The current list is always the one in the deposit window, because new networks appear there first. ## Which networks have the most coins The longest list is on **Chiliz Chain**, where the coins are football club fan tokens. Among regular tokens the richest networks are **Solana**, **BNB Chain**, and **Ethereum**: if you hold a token that exists in several places, one of these three will almost certainly carry it. Stablecoins are the easiest starting point. USDT and USDC are available on the most networks, so you can send them from almost any wallet or exchange. GRAM, the Telegram token, is a coin in the TON network and not a network of its own. It is handy if you came in through Telegram, since you can fund your account from the Telegram wallet without leaving the messenger. ## Picking the right one The network you send from has to match the network selected on the platform. A mismatch is the most common reason a deposit is delayed: it is not credited automatically, and returning it takes time and a request to support. Open the deposit window first, select your coin and network there, and only then start the transfer on the sending side. Some networks need an extra identifier along with the address, a memo or a tag, and there are two kinds of it. **XRP** issues a tag per deposit. Copy the exact value shown in the deposit window every time and do not reuse an old one. **TON** uses a permanent tag that belongs to your account. It does not change from one deposit to the next, but it still has to be sent with every transfer. A transfer that arrives without the tag, or with someone else's, is not credited automatically and has to be sorted out through support. Your bets are placed in the currency and network pool selected in the top right corner of the site. You can switch pools at any time in that same selector, and history in your profile shows all of them together. If you did send funds on the wrong network, contact support as early as possible with the transaction hash and your nickname. --- # 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://dexsport-3.gitbook.io/dexsport-docs/wallet-and-payments/networks-and-coins.md?ask=&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.