Swap USDT on zkSync Era to USDC on Solana

FromzkSync Era
ToSolana
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

Convert the zkSync Era 0x input into a Solana-account receipt

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. USDT uses USDT contract token on the source; USDC uses USDC contract token on Solana.

Solana token-account check for USDC

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. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset. A compatible wallet may create or use an associated token account, and SOL—not USDC unless it is SOL—pays later Solana fees.

zkSync Era approval and gas before the handoff

ETH is the native gas asset for zkSync Era. USDT is contract-tracked and can require an allowance before transfer. A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum.

USDT and USDC: two stablecoin ledgers

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. USDC is an issued dollar-oriented stablecoin with canonical, native, and bridged variants across networks. Contract events and issuer controls differ from a network-native gas asset. The route changes both asset identity and network representation; dollar-oriented pricing does not remove issuer controls, liquidity spread, contract, or receiving-network checks.

Mistakes specific to USDT zkSync Era to USDC Solana

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; 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 Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.

USDT input identity and handling

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.

USDC output identity and receiving

USDC is classified as a stablecoin for this route. USDC uses a network-specific contract asset on Solana. The Solana side is contract-tracked rather than a native gas balance. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.

Private Route for USDT → USDC

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 USDT on zkSync Era to USDC 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.

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

Related routes

Swap USDT on zkSync Era to USDC on Solana FAQs

Can a zkSync Era 0x address receive USDC on Solana?

No. The destination must be a Solana-compatible address. Base58-encoded Solana account address

Does receiving USDC create a Solana token account?

An SPL-token receipt uses the relevant mint and token account; the wallet or route may create an associated token account when needed. SOL is used for later Solana activity.

What exactly leaves zkSync Era as USDT?

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.

What exactly arrives on Solana as USDC?

USDC is a contract representation on Solana at EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v. SOL, not USDC, 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. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.

Why does the USDT to USDC direction matter?

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, The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.

What changes between the source and destination asset roles?

USDT is the deposited stablecoin input; USDC is the quoted stablecoin output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.

What should be matched before sending USDT?

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 Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.

Can I swap USDT on zkSync to USDC on Solana without KYC?

Requirements are checked for the live USDT zkSync to USDC 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.

View all Help Center FAQs →