Bridge WBTC from Polygon to Arbitrum

FromPolygon
ToArbitrum
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.

Direction

Polygon → Arbitrum

Asset

WBTC

Source gas

POL

Destination gas

ETH

How the Sasquatch deposit route works

1. Select the source

Choose the WBTC asset and Polygon network you currently hold.

2. Review the route

Check the estimated output, fees, timing, and Arbitrum destination network.

3. Create the order

Open the live route and follow the exact deposit instructions.

4. Track delivery

Use the receipt and status page until the destination funds arrive.

What you need to know

WBTC source representation

Wrapped Bitcoin is classified as a wrapped asset for this route. WBTC uses a wrapped contract asset on Polygon. The recorded Polygon 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.

From Polygon L1 into Arbitrum L2

Polygon source execution occurs on L1, while Arbitrum 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.

WBTC destination representation

Wrapped Bitcoin is classified as a wrapped asset for this route. WBTC uses a wrapped contract asset on Arbitrum. The recorded Arbitrum representation uses 8 decimal places. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.

Arbitrum receipt-side execution

Arbitrum is a L2 EVM network in the Ethereum ecosystem. ETH pays destination-side network gas on Arbitrum. EVM 0x account address An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately.

Polygon deposit-side 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.

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 Polygon. Its token balance, approvals, and contract transfer behavior are separate from the native coin used for network gas.

Polygon to Arbitrum bridge mistakes

Route-specific mistakes include sending on a network other than Polygon; using a destination that is not valid for Arbitrum; 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. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.

Private Route for WBTC → WBTC

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

Related routes

Polygon to Arbitrum FAQs

What WBTC representation leaves Polygon?

WBTC is a contract representation on Polygon with 8 decimals at 0x1BFD67037B42Cf73acF2047067bd4F2C47D9BfD6. POL, not WBTC, 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. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer.

What WBTC representation arrives on Arbitrum?

WBTC is a contract representation on Arbitrum with 8 decimals at 0x2f2a2543B76A4166549F7aaB2e75Bef0aefC5B0f. ETH, not WBTC, pays gas unless both symbols are the same. An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.

Does the same WBTC ticker guarantee the same ledger form?

No. This bridge keeps the asset intent while moving between a WBTC wrapped token and a WBTC wrapped token. Match the source and output details in the live quote.

Which gas balances matter for this bridge?

A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately. The bridge output does not automatically fund every later gas need.

What destination address should be used?

EVM 0x account address Do not substitute a Polygon address merely because a wallet displays both networks.

What wrong-direction mistake can prevent delivery?

Sending on a network other than Polygon, selecting a representation not listed by the quote, or entering an address invalid for Arbitrum can prevent normal detection or receipt.

Can I bridge WBTC from Polygon to Arbitrum without KYC?

Requirements are checked for the live WBTC Polygon to Arbitrum 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 bridge FAQs →