Bridge WBTC from Sui to Polygon

FromSui
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.

Direction

Sui → Polygon

Asset

WBTC

Source gas

SUI

Destination gas

POL

How the Sasquatch deposit route works

1. Select the source

Choose the WBTC asset and Sui network you currently hold.

2. Review the route

Check the estimated output, fees, timing, and Polygon 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

Sui to Polygon: object and account boundary

A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. A Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas. Sui and Polygon use different network identities, gas assets, wallet support, confirmation behavior, and destination conventions. Validate each side independently in the current route.

Sui coin-object and SUI gas requirements

SUI is the native gas asset for Sui. Sui hexadecimal account address with an object-based asset model Coin objects and Move types are not EVM token contracts.

WBTC input versus WBTC output representation

WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. 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.

WBTC keeps its ticker while changing ledgers

Wrapped Bitcoin is classified as a wrapped asset for this route. WBTC uses a wrapped contract asset on Sui. The recorded Sui representation uses 8 decimal places. The Sui side is contract-tracked rather than a native gas balance. 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. The Polygon side is contract-tracked rather than a native gas balance. WBTC leaves as a wrapped contract asset. WBTC arrives as a wrapped contract asset.

Sui to Polygon bridge mistakes

Route-specific mistakes include sending on a network other than Sui; using a destination that is not valid for Polygon; running out of SUI before the source transaction is submitted; assuming other and evm addresses are interchangeable; treating a wrapped token as the native gas asset. A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. 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. 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

Sui account, object, transaction-effect, and fee activity remain public, and Polygon wallet, token-transfer, contract, log, and gas activity remain public. For this WBTC on Sui to WBTC on Polygon path, Private Route is intended to reduce the direct visible relationship between activity around the source-side Sui hexadecimal account address with an object-based asset model 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 Sui → Polygon
  • Shows what remains public on Sui and Polygon before you deposit
Check Private Route availability →

Related routes

Sui to Polygon FAQs

Which side uses Sui coin objects and SUI gas?

Sui is the Sui side. Its Move coin types, address, objects, and SUI gas do not transfer as EVM contract metadata.

What WBTC representation leaves Sui?

WBTC is a contract representation on Sui with 8 decimals at 0x027792d9fed7f9844eb4839566001bb6f6cb4804f66aa2da6fe1ee242d896881::coin::COIN. SUI, not WBTC, pays gas unless both symbols are the same. A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. 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 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 receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas. 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 Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. A Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas. 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 Sui address merely because a wallet displays both networks.

What wrong-direction mistake can prevent delivery?

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

Can I bridge WBTC from Sui to Polygon without KYC?

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