Swap WBTC on Scroll to SOL on Polygon

FromScroll
ToPolygon
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.
SOL / USD
Price
24h
High
Low
Vol

What you need to know

WBTC input identity and handling

Wrapped Bitcoin is classified as a wrapped asset for this route. WBTC uses a wrapped contract asset on Scroll. The recorded Scroll representation uses 8 decimal places. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer.

Leaving Scroll L2 for Polygon L1

Scroll inclusion and its ethereum settlement are distinct from final receipt on Polygon. The live route, rather than a generic rollup withdrawal assumption, determines the provider path and timing for this direction.

WBTC unwrap or exchange input 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 source token on Scroll. Its token balance, approvals, and contract transfer behavior are separate from the native coin used for network gas.

Polygon destination execution

Polygon is a L1 EVM network in the Polygon ecosystem. POL pays destination-side network gas on Polygon. EVM 0x account address A Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas.

SOL output identity and receiving

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 receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.

Scroll source execution

Scroll is a L2 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on Scroll. EVM 0x account address A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently.

EVM-to-EVM execution boundary

Scroll and Polygon 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 WBTC Scroll to SOL Polygon

Route-specific mistakes include sending on a network other than Scroll; using a destination that is not valid for Polygon; running out of ETH before the source transaction is submitted; treating a wrapped token as the native gas asset. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. A Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.

Private Route for WBTC → SOL

Scroll wallet, token-transfer, contract, log, and gas activity remain public, and Polygon wallet, token-transfer, contract, log, and gas activity remain public. For this WBTC on Scroll to SOL on Polygon 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 WBTC deposit and SOL receipt
  • Compare standard and Private Route options for Scroll → Polygon
  • Shows what remains public on Scroll and Polygon before you deposit
Check Private Route availability →

Related routes

Swap WBTC on Scroll to SOL on Polygon FAQs

What exactly leaves Scroll as WBTC?

WBTC is a contract representation on Scroll with 8 decimals at 0x3C1BCa5a656e69edCD0D4E36BEbb3FcDAcA60Cf1. ETH, not WBTC, pays gas unless both symbols are the same. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer.

What exactly arrives on 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 receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.

Why does the WBTC to SOL direction matter?

WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. On receipt, Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.

What changes between the source and destination asset roles?

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

What should be matched before sending WBTC?

WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. A Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.

Can the wrapped asset pay native network gas?

No. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. A Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas.

What funds the Scroll source transaction?

ETH is the native gas asset for Scroll. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. WBTC is token-tracked and can need approval before transfer.

Can I swap WBTC on Scroll to SOL on Polygon without KYC?

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