Direction
Ethereum → Solana
Asset
TRX
Source gas
ETH
Destination gas
SOL
Choose the TRX asset and Ethereum network you currently hold.
Check the estimated output, fees, timing, and Solana destination network.
Open the live route and follow the exact deposit instructions.
Use the receipt and status page until the destination funds arrive.
Ethereum uses EVM account addresses and ETH for source gas. Solana uses Solana accounts, transaction signatures, and SOL for destination activity. A 0x address is not a valid substitute for the Solana receiving address shown by the route. TRX uses TRX contract token on the source; TRX uses TRX contract token on Solana.
Base58-encoded Solana account address A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Native TRX receipt belongs to a Tron address and can support network resources; tokenized TRX on another ledger cannot supply Tron bandwidth or energy. A compatible wallet may create or use an associated token account, and SOL—not TRX unless it is SOL—pays later Solana fees.
ETH is the native gas asset for Ethereum. TRX is contract-tracked and can require an allowance before transfer. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit.
TRON is classified as a native asset for this route. TRX uses a network-specific contract asset on Ethereum. The recorded Ethereum representation uses 6 decimal places. The Ethereum side is contract-tracked rather than a native gas balance. Native TRX exists on one recorded origin network; other network forms require representation checks. TRON is classified as a native asset for this route. TRX uses a network-specific contract asset on Solana. The recorded Solana representation uses 6 decimal places. The Solana side is contract-tracked rather than a native gas balance. Native TRX exists on one recorded origin network; other network forms require representation checks. TRX leaves as a network-specific contract asset. TRX arrives as a network-specific contract asset.
Route-specific mistakes include sending on a network other than Ethereum; using a destination that is not valid for Solana; running out of ETH before the source transaction is submitted; assuming evm and solana addresses are interchangeable. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. Native TRX can supply Tron bandwidth or energy resources and fees. Tokenized TRX outside Tron follows the source contract ledger. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Native TRX receipt belongs to a Tron address and can support network resources; tokenized TRX on another ledger cannot supply Tron bandwidth or energy.
Ethereum wallet, token-transfer, contract, log, and gas activity remain public, and Solana account, token, program, signature, and fee activity remain public. For this TRX on Ethereum to TRX on Solana path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side Base58-encoded Solana account address; it does not hide either chain's public records.
No. Base58-encoded Solana account address ETH pays the EVM source transaction, while SOL is used for later Solana activity.
TRX is a contract representation on Ethereum with 6 decimals at 0x50327c6c5a14DCaDE707ABad2E27eB517df87AB5. ETH, not TRX, pays gas unless both symbols are the same. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. Native TRX can supply Tron bandwidth or energy resources and fees. Tokenized TRX outside Tron follows the source contract ledger.
TRX is a contract representation on Solana with 6 decimals at GbbesPbaYh5uiAZSYNXTc7w9jty1rpg3P9L4JeN4LkKc. SOL, not TRX, pays gas unless both symbols are the same. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Native TRX receipt belongs to a Tron address and can support network resources; tokenized TRX on another ledger cannot supply Tron bandwidth or energy.
No. This bridge keeps the asset intent while moving between a TRX contract token and a TRX contract token. Match the source and output details in the live quote.
An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. The bridge output does not automatically fund every later gas need.
Base58-encoded Solana account address Do not substitute a Ethereum address merely because a wallet displays both networks.
Sending on a network other than Ethereum, selecting a representation not listed by the quote, or entering an address invalid for Solana can prevent normal detection or receipt.
Requirements are checked for the live TRX Ethereum to Solana quote. Verification requirements can depend on the provider, amount, jurisdiction, and current route. Sasquatch does not verify this route as universally no-KYC; check the live flow before continuing.
