Receive USDT on TRON
Select TRC20 when the receiving service provides a TRON (TRC20) USDT address. Check the address and network together before creating the swap.
Swap Ethena USDe for Tether (USDT) and choose the USDT network that fits the receiving wallet. The page starts with network compatibility because the source USDe and the destination version of Tether must both match the transaction details.
USDe is a synthetic dollar issued within the Ethena ecosystem, while USDT is available across multiple blockchains. That makes the payout network a central decision for this direction.
Confirm where the USDe is actually held before selecting the payout. Ethena's production USDe contract is on Ethereum mainnet, so that blockchain is an important source context for the token.
If the form shows Ethereum as the source, send USDe through that exact network using the generated deposit address. Do not substitute sUSDe or another token even if it is held in the same wallet.
If another supported USDe source appears in the form, treat it as a separate route. The blockchain shown for the source must match the asset you transfer.
Tether can be received on different blockchains, and the destination should be chosen from what the wallet or platform actually accepts. The form can offer routes to TRON (TRC20), Solana or another supported payout when those combinations are available.
Select TRC20 when the receiving service provides a TRON (TRC20) USDT address. Check the address and network together before creating the swap.
Choose the matching ERC-20 payout when the destination expects that version of Tether. This can create a same-network path when the selected source and destination share a blockchain.
Use the alternative payout only when the receiving wallet explicitly supports that version of USDT. Do not reuse an address from another network simply because the same service supports multiple versions of Tether.
The route changes depending on how the USDe enters the service and where the USDT must leave it. Compare the path by destination requirement, not by ticker alone.
| Source | Destination | Typical reason |
|---|---|---|
| USDe on the selected source | USDT on the same blockchain | Keep both sides on one supported network |
| USDe on the selected source | TRC20 USDT | Receive Tether for a TRC20 wallet or service |
| USDe on the selected source | Alternative USDT network | Deliver Tether to another supported destination |
| Other source shown in form | Available USDT network | Use only the explicitly supported combination |
A network that exists for USDT does not automatically mean it is reachable from every USDe source. The route shown in the form is the one that should be used for the current transaction.
The rate block answers the main price question without turning the page into a market-data dashboard. Use the current quote to see how much USDT the selected USDe amount is expected to produce.
Enter the amount of USDe you plan to send and review the USDT estimate. The value can be close to one dollar per token without being permanently fixed at exactly one USDT.
A reference price describes the market relationship between the assets. The transaction quote also reflects the selected amount and route, so it is the more relevant number before sending funds.
Changing the payout network can change the route conditions. Recheck the quote whenever the destination network changes.
The most important check is that the source token is actually USDe and the destination wallet expects USDT on the selected blockchain. Similar tickers and multiple network versions make this pair easy to misconfigure if the transaction details are not reviewed.
USDe and sUSDe are separate assets. Send only USDe when the deposit instructions specify USDe.
The USDT address must belong to the blockchain selected for the destination. Use the deposit instructions from the receiving wallet or exchange rather than copying an address from a different network.
After sending USDe, save the blockchain transaction hash. It is the main reference if the deposit needs to be traced before the USDT payout is completed.
The conversion turns an onchain USDe balance into Tether on the network you choose. Set the payout network first if the receiving platform accepts only one version of USDT.
Do not reuse transaction details after changing the source or destination network. Create or recalculate the swap so the deposit instructions match the new path.
The service focuses on the practical route from USDe to an external USDT wallet. It avoids adding trading screens or yield information that are not required to complete the conversion.
Choose the Tether network before sending USDe. This is useful when the final wallet requires TRC20, ERC-20 or another specific supported version.
Tether is sent to the address entered for the transaction after processing. The result does not remain in an internal exchange account.
The page keeps USDe separate from sUSDe and other dollar assets. That makes the deposit requirement clearer before funds are transferred.
You can review the expected USDT amount before sending USDe. Recalculate whenever the amount or payout network changes.
Use the reverse pair when you need USDe instead of Tether. For questions about how Ethena's synthetic dollar works, use the informational guides rather than extending the commercial flow.
Choose the USDe source and the USDT network required by the receiving wallet. Review the quote, then return to the form above to create the swap.
Enter the USDe amount in the form to see the current USDT estimate for the selected route. The quote can change with the amount, network path and market conditions.
Yes, if TRON (TRC20) is offered as the USDT destination from the selected USDe source. Use a receiving address that explicitly supports Tether on TRON.
Yes, when the required payout network is shown as available. If Solana is selected, the destination must be a wallet or platform that accepts USDT on Solana.
No, the two tokens are different assets. Send only USDe when the deposit instructions specify USDe; using sUSDe can prevent normal processing.
Check the transaction status and keep the deposit hash available. If the payout remains incomplete, contact support with the swap details and blockchain transaction hash.
It can, because each destination can use a different route and blockchain cost structure. Recalculate the transaction after changing the payout network.