Direction
ZKsync Era → Solana
Asset
ETH
Source gas
ETH
Destination gas
SOL
Choose the ETH asset and ZKsync Era 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.
zkSync Era 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. ETH uses native ETH on the source; ETH uses ETH 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. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees. A compatible wallet may create or use an associated token account, and SOL—not ETH unless it is SOL—pays later Solana fees.
ETH is the native gas asset for zkSync Era. ETH is a native source balance. A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum.
Ethereum is classified as a native asset for this route. ETH uses a native asset on zkSync Era. The recorded zkSync Era representation uses 18 decimal places. Native ETH exists on multiple recorded origin networks; other network forms require representation checks. Ethereum is classified as a native asset for this route. ETH uses a network-specific contract asset on Solana. The recorded Solana representation uses 8 decimal places. The Solana side is contract-tracked rather than a native gas balance. Native ETH exists on multiple recorded origin networks; other network forms require representation checks. ETH leaves as a native asset. ETH arrives as a network-specific contract asset. The ticker remains the same while the ledger representation changes across the route.
Route-specific mistakes include sending on a network other than zkSync Era; 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. A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. Native ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
ZKsync Era wallet, token-transfer, contract, log, and gas activity remain public, and Solana account, token, program, signature, and fee activity remain public. For this ETH on ZKsync Era to ETH 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.
ETH is listed as the native representation on zkSync Era; ETH is used for network gas. A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. Native ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ.
ETH is a contract representation on Solana with 8 decimals at 7vfCXTUXx5WJV5JADk17DUJ4ksgau7utNKj4b963voxs. SOL, not ETH, 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. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
No. This bridge keeps the asset intent while moving between a native ETH and a ETH contract token. Match the source and output details in the live quote.
A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. 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 zkSync Era address merely because a wallet displays both networks.
Sending on a network other than zkSync Era, 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 ETH ZKsync Era 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.
