Solana to Tron: TRC-20 and SVM boundary
A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. A Tron receipt belongs to a T-address as native TRX or the quoted TRC-20 contract; later activity consumes Tron resources or TRX fees. Solana and Tron use different network identities, gas assets, wallet support, confirmation behavior, and destination conventions. Validate each side independently in the current route.
TRX resources and Tron address check
TRX is the native gas asset for Tron. Tron Base58Check address, commonly beginning with T A TRC-20 token transfer is not an ERC-20 transfer even when an asset ticker exists on both sides.
USDC to DAI representation change
The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. The receiving wallet must recognize the exact destination DAI contract. Peg intent does not guarantee that a bridged representation has the same liquidity or issuer path. Verify the exact TRC-20 contract and the Solana representation independently.
USDC and DAI: two stablecoin ledgers
USDC is an issued dollar-oriented stablecoin with canonical, native, and bridged variants across networks. Contract events and issuer controls differ from a network-native gas asset. DAI is a crypto-backed dollar-oriented stablecoin whose canonical and bridged contracts vary by network. Its peg design does not make two network representations interchangeable. The route changes both asset identity and network representation; dollar-oriented pricing does not remove issuer controls, liquidity spread, contract, or receiving-network checks.
Mistakes specific to USDC Solana to DAI Tron
Route-specific mistakes include sending on a network other than Solana; using a destination that is not valid for Tron; running out of SOL before the source transaction is submitted; assuming solana and other addresses are interchangeable; selecting a stablecoin by ticker without checking its network contract. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. A Tron receipt belongs to a T-address as native TRX or the quoted TRC-20 contract; later activity consumes Tron resources or TRX fees. The receiving wallet must recognize the exact destination DAI contract. Peg intent does not guarantee that a bridged representation has the same liquidity or issuer path.
USDC input identity and handling
USDC is classified as a stablecoin for this route. USDC uses a network-specific contract asset on Solana. The Solana side is contract-tracked rather than a native gas balance. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset.
DAI output identity and receiving
Dai is classified as a stablecoin for this route. DAI uses a network-specific contract asset on Tron. The recorded Tron representation uses 18 decimal places. The receiving wallet must recognize the exact destination DAI contract. Peg intent does not guarantee that a bridged representation has the same liquidity or issuer path.