Swap USDC on Sui to WBTC on Solana

FromSui
ToSolana
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 to Solana: 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 Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Sui and Solana 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.

USDC input versus WBTC output representation

The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. 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.

Converting stablecoin USDC into WBTC

USDC is an issued dollar-oriented stablecoin with canonical, native, and bridged variants across networks. Contract events and issuer controls differ from a network-native gas asset. The source is a stablecoin contract or recorded native representation, while WBTC is classified as wrapped-asset. Check the quoted output rather than assuming a one-dollar source unit fixes the destination amount.

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

Mistakes specific to USDC Sui to WBTC Solana

Route-specific mistakes include sending on a network other than Sui; using a destination that is not valid for Solana; running out of SUI before the source transaction is submitted; assuming other and solana addresses are interchangeable; selecting a stablecoin by ticker without checking its network contract; 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. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. 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.

USDC input identity and handling

USDC is classified as a stablecoin for this route. USDC uses a network-specific contract asset on Sui. The Sui side is contract-tracked rather than a native gas balance. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset.

WBTC output identity and receiving

Wrapped Bitcoin is classified as a wrapped asset for this route. WBTC uses a wrapped contract asset on Solana. The Solana side is contract-tracked rather than a native gas balance. 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 USDC → WBTC

Sui account, object, transaction-effect, and fee activity remain public, and Solana account, token, program, signature, and fee activity remain public. For this USDC on Sui to WBTC on Solana 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 Base58-encoded Solana account address; it does not hide either chain's public records.

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

Related routes

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

What exactly leaves Sui as USDC?

USDC is a contract representation on Sui at 0xdba34672e30cb065b1f93e3ab55318768fd6fef66c15942c9f7cb846e2f900e7::usdc::USDC. SUI, not USDC, 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. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset.

What exactly arrives on Solana as WBTC?

WBTC is a contract representation on Solana at 5XZw2LKTyrfvfiskJ78AMpackRjPcyCif1WhUsPDuVqQ. SOL, not WBTC, pays gas unless both symbols are the same. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. 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 USDC to WBTC direction matter?

The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. 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?

USDC is the deposited stablecoin 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 USDC?

The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s 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. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. 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.

Which stablecoin contract must this route match?

USDC must match its Sui representation. A ticker or target price is not enough to identify a token contract.

Can I swap USDC on Sui to WBTC on Solana without KYC?

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