Swap TRX on Solana to WBTC on zkSync Era

FromSolana
TozkSync Era
ENTER AMOUNT
Squatch Guard
Before a deposit order moves forward, Squatch Guard checks the amount, asset, network, and active quote window against the order details.

What you need to know

Move from a Solana account into zkSync Era EVM

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 WBTC arrives at the quoted zkSync Era native or contract representation.

TRX mint and SOL fee checks

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.

zkSync Era contract and 0x receiving checks

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. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path. A Solana address cannot receive this EVM-side output.

WBTC wrapped-token output check

WBTC is a custodial tokenized Bitcoin representation on smart-contract networks. Its transfers use token contracts and approvals rather than native Bitcoin inputs and outputs. On this route WBTC is the destination token on zkSync Era. Its token balance, approvals, and contract transfer behavior are separate from the native coin used for network gas.

Mistakes specific to TRX Solana to WBTC zkSync Era

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; treating a wrapped token as the native gas asset. 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. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.

TRX input identity and handling

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.

WBTC output identity and receiving

Wrapped Bitcoin is classified as a wrapped asset for this route. WBTC uses a wrapped contract asset on zkSync Era. The recorded zkSync Era representation uses 8 decimal places. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.

Private Route for TRX → WBTC

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 WBTC 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.

  • Reduces the obvious link between the TRX deposit and WBTC receipt
  • Compare standard and Private Route options for Solana → zkSync Era
  • Shows what remains public on Solana and zkSync Era before you deposit
Check Private Route availability →

Related routes

Swap TRX on Solana to WBTC on zkSync Era FAQs

Can a Solana address be used for the zkSync Era output?

No. EVM 0x account address The WBTC output belongs to the quoted EVM representation.

What pays gas on each side of this Solana-to-EVM route?

SOL pays source fees on Solana. ETH pays later transactions on zkSync Era; the delivered WBTC does not replace that gas balance unless it is the native asset.

What exactly leaves Solana as TRX?

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.

What exactly arrives on zkSync Era as WBTC?

WBTC is a contract representation on zkSync Era with 8 decimals at 0xBBeB516fb02a01611cBBE0453Fe3c580D7281011. ETH, not WBTC, 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. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.

Why does the TRX to WBTC direction matter?

Native TRX can supply Tron bandwidth or energy resources and fees. Tokenized TRX outside Tron follows the source contract ledger. On receipt, WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.

What changes between the source and destination asset roles?

TRX is the deposited native-asset input; WBTC is the quoted wrapped-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.

What should be matched before sending TRX?

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. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.

Can I swap TRX on Solana to WBTC on zkSync without KYC?

Requirements are checked for the live TRX Solana to WBTC 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.

View all Help Center FAQs →