Networks, fees
and memo tags
The same USDT sent two different ways can cost pennies or many dollars. The coin is identical either way — what changes is the road it travels on, and that choice is yours to make.
Why one coin has several networks
A stablecoin is issued on top of other blockchains rather than having one of its own. USDT on Ethereum and USDT on Tron are the same claim on the same issuer, but they live on separate ledgers that do not talk to each other.
This has one consequence that matters more than everything else on this page: you must send on a network the receiving end supports. Coin sent on the wrong network does not bounce back. It arrives at an address that exists on a chain nobody is watching, and recovering it ranges from a slow support ticket to impossible.
What each network is like
Ethereum (ERC-20) is the original and the most expensive. Fees rise and fall with how busy the network is, and at busy moments a transfer can cost more than a small deposit is worth. Universally supported, which is its main virtue.
Tron (TRC-20) became the default for stablecoin transfers precisely because it is cheap and fast. Widely supported by casinos and exchanges alike.
Solana is very cheap and very fast, and support is now broad.
Bitcoin Lightning is near-instant and near-free for small amounts, but only for Bitcoin, and support is patchy.
Bitcoin on-chain is slow and priced by congestion. Fine for large, unhurried transfers. Poor for a Saturday-night deposit.
Fees are live numbers and change by the hour, so any table of them goes stale by the time you read it. Check the actual quote in your wallet at the moment you send — the ranking above is stable, the numbers are not.
Memo tags: the expensive mistake
A handful of networks — Toncoin, XRP and Hedera among them — route deposits differently from the rest. Instead of giving every user their own address, the exchange or casino uses one shared address and tells the deposits apart using a second field, variously called a memo, tag or comment.
Send on one of those networks without the memo and the coin arrives at the shared address with nothing to say who it belongs to. It is not lost in the blockchain sense — it is sitting there, unattributed. Getting it credited means a support ticket, proof of the transaction, and waiting.
Two rules cover it:
If a deposit screen shows a memo field, it is mandatory. Not optional, not advanced. Copy it exactly, with no added spaces.
Copy both fields separately. The common failure is copying the address, pasting, then hitting send out of habit — with the memo box still empty.
How to choose in practice
| Situation | Sensible choice |
|---|---|
| Small or routine deposit | Tron or Solana stablecoin |
| Large one-off transfer | Whatever both ends support best; fee is a small share |
| Already hold Bitcoin | Lightning if supported, on-chain if not |
| Destination lists one network only | Use that one. There is no clever alternative. |
Before you press send
Check the network selected in your wallet matches the one on the deposit screen. Check the memo field if there is one. Check the first and last four characters of the address — clipboard-hijacking malware swaps addresses, and those characters are what catches it. On a first send to a new address, send a small test amount and wait.
That is four checks and about twenty seconds, against the only mistake in this whole process that cannot be undone.
Then it is a normal deposit
Once the network is right, funds land in minutes and there is nothing else to do.
Play at Duel