USDT Networks: TRC20 vs ERC20 vs BEP20
The same USDT travels on several blockchains, and sending it on the wrong one loses it. Compare TRC20, ERC20 and BEP20 on fees, speed and compatibility.
This is the guide worth reading before you send anything. USDT exists as a separate token on several different blockchains, and transferring it means choosing one. Choose a network the receiving address does not support and the transfer is usually unrecoverable — not delayed, not refundable, gone.
The good news is that getting it right is simple once you understand what you are choosing.
Why the same token has several versions
A blockchain is a separate ledger. Tether issues USDT on many of them, and each issuance is its own token that happens to be redeemable for the same dollar. An address is a location on one specific ledger. There is no bridge in the middle of a transfer that notices you picked the wrong one and corrects it.
So "send 100 USDT" is an incomplete instruction. The complete instruction is "send 100 USDT on TRON to this TRON address".
The three you will meet most
TRC20 — TRON
The most common choice for moving USDT between platforms, because fees are very low (often
well under a dollar) and confirmation takes seconds to a minute. Addresses begin with
T. If a platform offers TRC20 and you have no reason to prefer anything else,
this is usually the sensible default.
ERC20 — Ethereum
The original and most widely supported, accepted essentially everywhere. The cost is the
problem: fees are paid in ETH and vary with network demand, ranging from a couple of dollars
to considerably more at busy times. Addresses begin with 0x. Worth it for large
transfers where a fixed fee is negligible, or where the receiving side only supports ERC20.
BEP20 — BNB Smart Chain
A middle ground: low fees, fast confirmation, widely supported by exchanges. Addresses also
begin with 0x, and this is where the most dangerous confusion lives — an ERC20
address and a BEP20 address look identical. Only the network label tells them apart.
The trap with 0x addresses
Because Ethereum, BNB Smart Chain and several other chains use the same address format, you cannot tell from the address which network it is for. Copying a BEP20 address and sending ERC20 USDT to it will broadcast successfully and show as confirmed. The tokens will sit at that address on the wrong chain, where the receiving platform is not looking for them.
Sometimes these are recoverable, if whoever controls the address can import the private key into a wallet configured for the other chain. On a custodial platform, usually they cannot. Assume unrecoverable and act accordingly.
Comparing them
| Network | Typical fee | Speed | Address starts |
|---|---|---|---|
| TRC20 (TRON) | Under $1 | Seconds | T |
| ERC20 (Ethereum) | $2–$30+ | 1–5 minutes | 0x |
| BEP20 (BNB Chain) | Cents | Seconds | 0x |
| Polygon / Solana | Cents | Seconds | Varies |
Fees move with network conditions, so treat these as orders of magnitude rather than quotes.
A checklist that prevents the mistake
- Start from the receiving address, not the sending wallet. Note which network it was issued for, then select that network when you send.
- Never reuse an address across networks. An address issued for BEP20 is for BEP20 only, even though the format would work elsewhere.
- Send a small test first for any transfer large enough that losing it would hurt. The extra fee is cheap insurance.
- Check the first and last six characters after pasting. Clipboard-hijacking malware substitutes addresses silently; this catches it.
- Confirm the memo requirement. A few networks require a memo or tag. If the receiving side asks for one, omitting it can lose the transfer even on the right chain.
How this works on Bullish UK
Deposit addresses are issued per network and the network is shown beside the address in your dashboard. Use the address you were given, on the network it is labelled with, and submit the transaction hash so the transfer can be confirmed. If the network you prefer is not listed, contact support before sending rather than improvising.
Next: protecting your account covers the other half of keeping transfers safe.