Solana uses Solana accounts and SOL for source fees, while zkSync Era uses an EVM 0x account and ETH for destination gas. Confirm the destination token contract and do not paste a Solana address into the EVM destination field. TRX is read from its Solana mint or native account, while LINK arrives at the quoted zkSync Era native or contract representation.
Base58-encoded Solana account address SOL is the native gas asset for Solana. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. Native TRX can supply Tron bandwidth or energy resources and fees. Tokenized TRX outside Tron follows the source contract ledger. The mint/account selected by the quote must match the source wallet balance.
EVM 0x account address ETH is the native gas asset for zkSync Era. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later. A Solana address cannot receive this EVM-side output.
Route-specific mistakes include sending on a network other than Solana; using a destination that is not valid for zkSync Era; running out of SOL before the source transaction is submitted; assuming solana and evm addresses are interchangeable. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. Native TRX can supply Tron bandwidth or energy resources and fees. Tokenized TRX outside Tron follows the source contract ledger. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
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. Native TRX can supply Tron bandwidth or energy resources and fees. Tokenized TRX outside Tron follows the source contract ledger.
Chainlink is classified as a governance or utility token for this route. LINK uses a network-specific contract asset on zkSync Era. The zkSync Era side is contract-tracked rather than a native gas balance. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
Solana account, token, program, signature, and fee activity remain public, and zkSync Era wallet, token-transfer, contract, log, and gas activity remain public. For this TRX on Solana to LINK on zkSync Era path, Private Route is intended to reduce the direct visible relationship between activity around the source-side Base58-encoded Solana account address and destination-side EVM 0x account address; it does not hide either chain's public records.
No. EVM 0x account address The LINK output belongs to the quoted EVM representation.
SOL pays source fees on Solana. ETH pays later transactions on zkSync Era; the delivered LINK does not replace that gas balance unless it is the native asset.
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 source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. Native TRX can supply Tron bandwidth or energy resources and fees. Tokenized TRX outside Tron follows the source contract ledger.
LINK is a contract representation on zkSync Era at 0x52869bae3e091e36b0915941577f2d47d8d8b534. ETH, not LINK, pays gas unless both symbols are the same. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
Native TRX can supply Tron bandwidth or energy resources and fees. Tokenized TRX outside Tron follows the source contract ledger. On receipt, LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
TRX is the deposited native-asset input; LINK is the quoted token output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
Native TRX can supply Tron bandwidth or energy resources and fees. Tokenized TRX outside Tron follows the source contract ledger. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
Requirements are checked for the live TRX Solana to LINK zkSync 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.
