Swap SUI to WBTC

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

SUI input identity and handling

Sui is classified as a native asset for this route. SUI uses a quote-selected representation. Native SUI exists on one recorded origin network; other network forms require representation checks. Native SUI is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model.

WBTC output identity and receiving

Wrapped Bitcoin is classified as a wrapped asset for this route. WBTC uses a quote-selected representation. 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. Its token balance, approvals, and contract transfer behavior are separate from the native coin used for network gas.

Mistakes specific to SUI to WBTC

Verify both asset identities, the selected network, current deposit instructions, and the receiving representation.

SUI source handling versus WBTC receipt

Native SUI is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model. 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 SUI → WBTC

Sui account, object, transaction-effect, and fee activity remain public, and the selected destination network addresses, transfers, amounts, fees, and timing remain public. For this SUI on Sui to WBTC on the selected destination network 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 the selected destination network address; it does not hide either chain's public records.

  • Reduces the obvious link between the SUI deposit and WBTC receipt
  • Compare standard and Private Route options for Sui → the selected destination network
  • Shows what remains public on Sui and the selected destination network before you deposit
Check Private Route availability →

Related routes

Swap SUI to WBTC FAQs

Why does the SUI to WBTC direction matter?

Native SUI is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model. 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?

SUI 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 SUI?

Native SUI is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model. Match the source network shown by the quote. Confirm the destination network in the quote. 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.

Can I swap SUI on Sui to WBTC on Wrapped Bitcoin without KYC?

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