Swap USDC on zkSync Era to DOGE 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.
DOGE / USD
Price
24h
High
Low
Vol

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

Solana token-account check for DOGE

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. Native DOGE receipt creates a Dogecoin UTXO at a compatible address; tokenized DOGE instead appears under a destination contract. A compatible wallet may create or use an associated token account, and SOL—not DOGE 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. USDC 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.

Converting stablecoin USDC into DOGE

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 source is a stablecoin contract or recorded native representation, while DOGE is classified as token. Check the quoted output rather than assuming a one-dollar source unit fixes the destination amount.

Mistakes specific to USDC zkSync Era to DOGE 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 source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Native DOGE receipt creates a Dogecoin UTXO at a compatible address; tokenized DOGE instead appears under a destination contract.

USDC input identity and handling

USDC is classified as a stablecoin for this route. USDC uses a network-specific contract asset on zkSync Era. The zkSync Era side is contract-tracked rather than a native gas balance. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset.

DOGE output identity and receiving

Dogecoin is classified as a UTXO-native asset for this route. DOGE uses a network-specific contract asset on Solana. The recorded Solana representation uses 8 decimal places. Native DOGE receipt creates a Dogecoin UTXO at a compatible address; tokenized DOGE instead appears under a destination contract.

Private Route for USDC → DOGE

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 USDC on zkSync Era to DOGE 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 USDC deposit and DOGE 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 USDC on zkSync Era to DOGE on Solana FAQs

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

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

Does receiving DOGE 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 USDC?

USDC is a contract representation on zkSync Era at 0x1d17cbcf0d6d143135ae902365d2e5e2a16538d4. ETH, not USDC, 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 source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset.

What exactly arrives on Solana as DOGE?

DOGE is a contract representation on Solana with 8 decimals at KQijDbNJ6rPCqhtXrfH6gKa5cH3a39At8vHq34nnPbF. SOL, not DOGE, 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. Native DOGE receipt creates a Dogecoin UTXO at a compatible address; tokenized DOGE instead appears under a destination contract.

Why does the USDC to DOGE direction matter?

The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. On receipt, Native DOGE receipt creates a Dogecoin UTXO at a compatible address; tokenized DOGE instead appears under a destination contract.

What changes between the source and destination asset roles?

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

What should be matched before sending USDC?

The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. 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. Native DOGE receipt creates a Dogecoin UTXO at a compatible address; tokenized DOGE instead appears under a destination contract.

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

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