Swap WBTC on Sui to SUI on Sui

FromSui
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.
SUI / 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 Sui. The recorded Sui 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.

SUI output identity and receiving

Sui is classified as a native asset for this route. SUI uses a native asset on Sui. The Sui side is contract-tracked rather than a native gas balance. Native SUI receipt creates Sui coin objects that can fund later gas. A smart-contract token outside Sui does not become a native object.

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

Sui source execution

Sui is a L1 Move VM network in the Sui ecosystem. SUI pays source-side network gas on Sui. Sui hexadecimal account address with an object-based asset model A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution.

Mistakes specific to WBTC Sui to SUI Sui

Route-specific mistakes include sending on a network other than Sui; using a destination that is not valid for Sui; running out of SUI before the source transaction is submitted; 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 Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. Native SUI receipt creates Sui coin objects that can fund later gas. A smart-contract token outside Sui does not become a native object.

Private Route for WBTC → SUI

Sui account, object, transaction-effect, and fee activity remain public. For this WBTC on Sui to SUI on Sui 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 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 WBTC deposit and SUI receipt
  • Compare standard and Private Route options for Sui → Sui
  • Shows what remains public on Sui and Sui before you deposit
Check Private Route availability →

Related routes

Swap WBTC on Sui to SUI 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 Move VM execution, so addresses and token identifiers are not interchangeable.

What exactly leaves 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 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 exactly arrives on Sui as SUI?

SUI is listed as the native representation on Sui; SUI is used for network gas. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. Native SUI receipt creates Sui coin objects that can fund later gas. A smart-contract token outside Sui does not become a native object.

Why does the WBTC to SUI 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 SUI receipt creates Sui coin objects that can fund later gas. A smart-contract token outside Sui does not become a native object.

What changes between the source and destination asset roles?

WBTC is the deposited wrapped-asset input; SUI 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 Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. Native SUI receipt creates Sui coin objects that can fund later gas. A smart-contract token outside Sui does not become a native object.

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 Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. 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 WBTC on Sui to SUI on Sui without KYC?

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