A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. 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. zkSync Era and Tron use different network identities, gas assets, wallet support, confirmation behavior, and destination conventions. Validate each side independently in the current route.
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.
The input must match the selected ERC-20, TRC-20, SPL, or other USDT representation; each standard has different address, approval, and fee behavior. Native TRX receipt belongs to a Tron address and can support network resources; tokenized TRX on another ledger cannot supply Tron bandwidth or energy. Verify the exact TRC-20 contract and the zkSync Era representation independently.
USDT is issued through ERC-20, TRC-20, SPL, and other network-specific contracts. The ticker does not determine the token standard, contract, issuer controls, or destination address model. The source is a stablecoin contract or recorded native representation, while TRX is classified as native-asset. Check the quoted output rather than assuming a one-dollar source unit fixes the destination amount.
Route-specific mistakes include sending on a network other than zkSync Era; using a destination that is not valid for Tron; running out of ETH before the source transaction is submitted; assuming evm and other addresses are interchangeable; selecting a stablecoin by ticker without checking its network contract. A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. The input must match the selected ERC-20, TRC-20, SPL, or other USDT representation; each standard has different address, approval, and fee behavior. 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. Native TRX receipt belongs to a Tron address and can support network resources; tokenized TRX on another ledger cannot supply Tron bandwidth or energy.
Tether is classified as a stablecoin for this route. USDT uses a network-specific contract asset on zkSync Era. The recorded zkSync Era representation uses 6 decimal places. The input must match the selected ERC-20, TRC-20, SPL, or other USDT representation; each standard has different address, approval, and fee behavior.
TRON is classified as a native asset for this route. TRX uses a native asset on Tron. Native TRX exists on one recorded origin network; other network forms require representation checks. Native TRX receipt belongs to a Tron address and can support network resources; tokenized TRX on another ledger cannot supply Tron bandwidth or energy.
zkSync Era wallet, token-transfer, contract, log, and gas activity remain public, and Tron address, token-transfer, contract, and resource activity remain public. For this USDT on zkSync Era to TRX on Tron path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side Tron Base58Check address, commonly beginning with T; it does not hide either chain's public records.
The Tron side must match the TRC-20 contract or native TRX label shown in the route. The zkSync Era side is a separate network representation.
USDT is a contract representation on zkSync Era with 6 decimals at 0x493257fD37EDB34451f62EDf8D2a0C418852bA4C. ETH, not USDT, pays gas unless both symbols are the same. A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. The input must match the selected ERC-20, TRC-20, SPL, or other USDT representation; each standard has different address, approval, and fee behavior.
TRX is listed as the native representation on Tron; TRX is used for network gas. 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. Native TRX receipt belongs to a Tron address and can support network resources; tokenized TRX on another ledger cannot supply Tron bandwidth or energy.
The input must match the selected ERC-20, TRC-20, SPL, or other USDT representation; each standard has different address, approval, and fee behavior. On receipt, Native TRX receipt belongs to a Tron address and can support network resources; tokenized TRX on another ledger cannot supply Tron bandwidth or energy.
USDT is the deposited stablecoin input; TRX is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
The input must match the selected ERC-20, TRC-20, SPL, or other USDT representation; each standard has different address, approval, and fee behavior. A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. 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. Native TRX receipt belongs to a Tron address and can support network resources; tokenized TRX on another ledger cannot supply Tron bandwidth or energy.
USDT must match its zkSync Era representation. A ticker or target price is not enough to identify a token contract.
Requirements are checked for the live USDT zkSync to TRX Tron 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.
