Swap SOL on Polygon to WETH on zkSync Era

FromPolygon
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

SOL input identity and handling

Solana is classified as a native asset for this route. SOL uses a network-specific contract asset on Polygon. The recorded Polygon representation uses 9 decimal places. Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract instead.

From Polygon L1 into zkSync Era L2

Polygon source execution occurs on L1, while zkSync Era delivery occurs on a separate L2 ledger that settles to ethereum. POL pays source gas and ETH is the destination gas asset; identical-looking wallet addresses do not merge the balances or transaction histories.

WETH wrapped-token output check

WETH is a contract wrapper for ETH. It can be transferred as a token but cannot replace the native gas balance required by the network. On this route WETH 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.

zkSync Era destination execution

zkSync Era is a L2 EVM network in the Ethereum ecosystem. ETH pays destination-side network gas on zkSync Era. EVM 0x account address A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery.

WETH output identity and receiving

WETH is classified as a wrapped asset for this route. WETH uses a wrapped contract asset on zkSync Era. The recorded zkSync Era representation uses 18 decimal places. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.

Polygon source execution

Polygon is a L1 EVM network in the Polygon ecosystem. POL pays source-side network gas on Polygon. EVM 0x account address A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1.

EVM-to-EVM execution boundary

Polygon and zkSync Era can use the same 0x address syntax, but they are separate networks with different chain identifiers, gas balances, token contracts, and transaction histories. The recorded settlement context includes ethereum, so L1 and L2 confirmation behavior should not be assumed identical.

Mistakes specific to SOL Polygon to WETH zkSync Era

Route-specific mistakes include sending on a network other than Polygon; using a destination that is not valid for zkSync Era; running out of POL before the source transaction is submitted; treating a wrapped token as the native gas asset. A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract instead. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.

Private Route for SOL → WETH

Polygon wallet, token-transfer, contract, log, and gas activity remain public, and zkSync Era wallet, token-transfer, contract, log, and gas activity remain public. For this SOL on Polygon to WETH on zkSync Era path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side EVM 0x account address; it does not hide either chain's public records.

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

Related routes

Swap SOL on Polygon to WETH on zkSync Era FAQs

What exactly leaves Polygon as SOL?

SOL is a contract representation on Polygon with 9 decimals at 0xd93f7E271cB87c23AaA73edC008A79646d1F9912. POL, not SOL, pays gas unless both symbols are the same. A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract instead.

What exactly arrives on zkSync Era as WETH?

WETH is a contract representation on zkSync Era with 18 decimals at 0x5AEa5775959fBC2557Cc8789bC1bf90A239D9a91. ETH, not WETH, 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. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.

Why does the SOL to WETH direction matter?

Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract instead. On receipt, WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.

What changes between the source and destination asset roles?

SOL is the deposited native-asset input; WETH 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 SOL?

Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract instead. A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.

Can the wrapped asset pay native network gas?

No. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas. A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery.

What funds the Polygon source transaction?

POL is the native gas asset for Polygon. A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. SOL is token-tracked and can need approval before transfer.

Can I swap SOL on Polygon to WETH on zkSync without KYC?

Requirements are checked for the live SOL Polygon to WETH 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 →