Tether is one token with one price and at least a dozen different sets of rails underneath it. The two that matter most in daily use are ERC-20, which is USDT issued on Ethereum, and TRC-20, which is USDT issued on Tron. They are worth the same dollar. They are not the same asset in any technical sense, and a transfer that ignores the difference does not politely bounce back.
What the standard actually is
ERC-20 and TRC-20 are token specifications: a short list of functions that a contract must expose so that wallets and exchanges know how to move balances. Tether deploys a contract on each chain and issues supply against it.
The consequence is that your USDT balance is a row in a specific contract on a specific blockchain. There is no global Tether ledger that reconciles across chains. Moving between them means going through Tether itself or through a bridge, not through a normal send.
The fee difference, and why it flips
Ethereum charges gas in ETH, priced by network demand. A USDT transfer might cost under a dollar during a quiet weekend and considerably more during a busy period. You also need ETH in the wallet to pay the crypto, which surprises people who hold only USDT and then discover they cannot move it.
Tron uses a bandwidth-and-energy model. In practice, a TRC-20 transfer is usually a fraction of the Ethereum cost. Besides, Tron has become the default rail for smaller transfers largely for that reason.
This inverts on small amounts in a way worth spelling out. On a 5,000 dollar transfer, a few dollars of gas are rounding. With a $40 deposit, the same fee is 10% before anything happens. The right network depends on the size of what you are sending, not on a fixed preference.
The three ways this goes wrong, in order of severity
The harmless one. You try to send TRC-20 USDT to an Ethereum address. Tron addresses start with T, and Ethereum addresses start with 0x, so the address formats do not match, and any competent wallet refuses the transaction outright. You lose thirty seconds and learn something.
The recoverable one. You send USDT on one EVM chain to an address that expects it on another. Ethereum, BNB Chain, Polygon, Arbitrum, and the rest share an address format, so the send succeeds and the tokens land at the same address on the wrong chain. If whoever controls that address controls the private key across chains, the funds exist and can usually be retrieved with a support ticket. If it is a contract address or a custodial deposit address generated for a single chain, retrieval can be slow or impossible.
The expensive one. You send to an exchange or service deposit address on a network that the service does not credit. As the transaction confirms, your money reaches at an address the recipient controls. However, their system was never told to watch that chain. This is the case that turns into a two-week support thread, and it is entirely preventable.
The habit that prevents all three
Read the network selector, not the coin name. Every deposit screen shows a network, and it is almost always a dropdown that defaults to something. The failure mode is not misreading the network. It is not reading it at all, because the coin logo was correct, and the eye moved on.
Then, on any first transfer to a new destination, send a small test amount. Pay the fee twice on purpose. It is the cheapest insurance available in crypto, and roughly nobody does it.
Finally, check the fee at the moment you send rather than assuming last week’s number. Ethereum gas is not stable, and a transfer that was trivial on Sunday can be uncomfortable on Wednesday.
Choosing a network on purpose
A short heuristic that covers most situations. For transfers under a few hundred dollars where both ends support it, TRC-20 is usually the cheaper rail. For larger amounts, or where the destination is a DeFi protocol or anything that needs to interact with Ethereum contracts, ERC-20 is the one that composes with everything else. If you are repeatedly moving between the same two places, standardize on one network and stop thinking about it.
Services that accept multiple networks generally show the supported set on the deposit screen itself, which is the only authoritative list. If you deposit USDT at Jacks Club or anywhere similar, the address you are given is generated for a specific chain, and the page names which one before it shows you the QR code. That naming is the thing to read.
If it has already gone wrong
Do not send a second transaction. Open a block explorer for the network you actually used, find the transaction hash, and confirm what happened on the chain. Then take that hash to the recipient’s support. The hash is the only useful piece of information in that conversation, and having it in the first message rather than the fifth saves days.
The underlying lesson is smaller than it feels. Stablecoins made value transfer feel like sending a message, and the one piece of the old system they did not remove is that the route matters. Read the route.
Be the first to comment