Sasquatch Exchange
TRADE
OrdersSupportAffiliatePrivate Swap

Swap SOL on Polygon to WBTC on Sui

FromPolygon
ToSui
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

Polygon to Sui: object and account boundary

A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. Polygon and Sui 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.

SOL input versus WBTC output representation

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

Mistakes specific to SOL Polygon to WBTC Sui

Route-specific mistakes include sending on a network other than Polygon; using a destination that is not valid for Sui; running out of POL before the source transaction is submitted; assuming evm and other addresses are interchangeable; 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 Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. 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.

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.

WBTC output identity and receiving

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. 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 SOL → WBTC

Polygon wallet, token-transfer, contract, log, and gas activity remain public, and Sui account, object, transaction-effect, and fee activity remain public. For this SOL on Polygon to WBTC on Sui path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side Sui hexadecimal account address with an object-based asset model; it does not hide either chain's public records.

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

Related routes

No-KYC and verification rulesPrivate SOL to WBTC route explainerPrivacy limits and live availabilitySwap WBTC to SOLReverse routeSolana (SOL)Wrapped Bitcoin (WBTC)Polygon networkSui networkBrowse supported swap routes

Swap SOL on Polygon to WBTC on Sui FAQs

How does the Sui coin-object side differ from the other network?

Sui uses Move coin types and objects with SUI gas. The other side follows EVM execution, so addresses and token identifiers are not interchangeable.

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 Sui as WBTC?

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 receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. 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.

Why does the SOL to WBTC 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, 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.

What changes between the source and destination asset roles?

SOL is the deposited native-asset input; WBTC is the quoted wrapped-asset 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 Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. 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.

Can the wrapped asset pay native network gas?

No. 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. A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance.

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

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