Swap DAI on Solana to USDC 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. DAI is read from its Solana mint or native account, while USDC arrives at the quoted zkSync Era native or contract representation.

DAI 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. DAI leaves through its network-specific stablecoin contract and can require approval; the collateral design does not make a bridged DAI contract canonical. 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. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset. A Solana address cannot receive this EVM-side output.

DAI and USDC: two stablecoin ledgers

DAI is a crypto-backed dollar-oriented stablecoin whose canonical and bridged contracts vary by network. Its peg design does not make two network representations interchangeable. 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 DAI Solana to USDC 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; selecting a stablecoin by ticker without checking its network contract. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. DAI leaves through its network-specific stablecoin contract and can require approval; the collateral design does not make a bridged DAI contract canonical. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.

DAI input identity and handling

Dai is classified as a stablecoin for this route. DAI uses a network-specific contract asset on Solana. The recorded Solana representation uses 8 decimal places. DAI leaves through its network-specific stablecoin contract and can require approval; the collateral design does not make a bridged DAI contract canonical.

USDC output identity and receiving

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

Private Route for DAI → USDC

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

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

No. EVM 0x account address The USDC 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 USDC does not replace that gas balance unless it is the native asset.

What exactly leaves Solana as DAI?

DAI is a contract representation on Solana with 8 decimals at EjmyN6qEC1Tf1JxiG1ae7UTJhUxSwk1TCWNWqxWV4J6o. SOL, not DAI, 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. DAI leaves through its network-specific stablecoin contract and can require approval; the collateral design does not make a bridged DAI contract canonical.

What exactly arrives on 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 receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. 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 DAI to USDC direction matter?

DAI leaves through its network-specific stablecoin contract and can require approval; the collateral design does not make a bridged DAI contract canonical. 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?

DAI 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 DAI?

DAI leaves through its network-specific stablecoin contract and can require approval; the collateral design does not make a bridged DAI contract canonical. 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. 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 DAI on Solana to USDC on zkSync without KYC?

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