BNB is classified as a native asset for this route. BNB uses a network-specific contract asset on zkSync Era. The recorded zkSync Era representation uses 18 decimal places. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling.
This route crosses two L2 execution environments. zkSync Era settles to ethereum, while Optimism settles to ethereum; each side keeps its own gas balance, token contracts, transaction hash, and settlement progress.
Optimism is a L2 EVM network in the Ethereum ecosystem. ETH pays destination-side network gas on Optimism. EVM 0x account address An OP Mainnet receipt belongs to the OP Stack L2 and needs ETH on that network for later activity; it is not an Ethereum L1 balance.
TRON is classified as a native asset for this route. TRX uses a network-specific contract asset on Optimism. The recorded Optimism representation uses 6 decimal places. 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 is a L2 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on zkSync Era. EVM 0x account address A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum.
zkSync Era and Optimism can use the same 0x address syntax, but they are separate networks with different chain identifiers, gas balances, token contracts, and transaction histories. The recorded settlement context includes ethereum, so L1 and L2 confirmation behavior should not be assumed identical.
Route-specific mistakes include sending on a network other than zkSync Era; using a destination that is not valid for Optimism; running out of ETH before the source transaction is submitted. A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. An OP Mainnet receipt belongs to the OP Stack L2 and needs ETH on that network for later activity; it is not an Ethereum L1 balance. 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 Optimism wallet, token-transfer, contract, log, and gas activity remain public. For this BNB on zkSync Era to TRX on Optimism path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side EVM 0x account address; it does not hide either chain's public records.
BNB is a contract representation on zkSync Era with 18 decimals at 0x7400793aAd94C8CA801aa036357d10F5Fd0ce08f. ETH, not BNB, 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. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling.
TRX is a contract representation on Optimism with 6 decimals at 0xb1aE0a34DC3976d98C1741C92b798dAF8E0e1e11. ETH, not TRX, pays gas unless both symbols are the same. An OP Mainnet receipt belongs to the OP Stack L2 and needs ETH on that network for later activity; it is not an Ethereum L1 balance. Native TRX receipt belongs to a Tron address and can support network resources; tokenized TRX on another ledger cannot supply Tron bandwidth or energy.
Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. 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.
BNB is the deposited native-asset input; TRX is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. An OP Mainnet receipt belongs to the OP Stack L2 and needs ETH on that network for later activity; it is not an Ethereum L1 balance. Native TRX receipt belongs to a Tron address and can support network resources; tokenized TRX on another ledger cannot supply Tron bandwidth or energy.
ETH is the native gas asset for zkSync Era. A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. BNB is token-tracked and can need approval before transfer.
Sending BNB on a network other than zkSync Era, or using an address that is not valid for Optimism, can prevent detection or delivery. Match both network labels and representations to the active route.
Requirements are checked for the live BNB zkSync to TRX OP Mainnet 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.
