Sasquatch Exchange
TRADE
OrdersSupportAffiliatePrivate Swap

Swap SOL on Sui to WBTC on Ethereum

FromSui
ToEthereum
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 Ethereum: 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. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. Sui and Ethereum 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 Ethereum. Its token balance, approvals, and contract transfer behavior are separate from the native coin used for network gas.

Mistakes specific to SOL Sui to WBTC Ethereum

Route-specific mistakes include sending on a network other than Sui; using a destination that is not valid for Ethereum; 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. 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. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. 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 Sui. The recorded Sui representation uses 8 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 Ethereum. The Ethereum 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 SOL → WBTC

Sui account, object, transaction-effect, and fee activity remain public, and Ethereum wallet, token-transfer, contract, log, and gas activity remain public. For this SOL on Sui to WBTC on Ethereum 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 SOL deposit and WBTC receipt
  • ✓Compare standard and Private Route options for Sui → Ethereum
  • ✓Shows what remains public on Sui and Ethereum 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)Sui networkEthereum networkBrowse supported swap routes

Swap SOL on Sui to WBTC on Ethereum 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 Sui as SOL?

SOL is a contract representation on Sui with 8 decimals at 0xb7844e289a8410e50fb3ca48d69eb9cf29e27d223ef90353fe1bd8e27ff8f3f8::coin::COIN. SUI, not SOL, 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. 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 Ethereum as WBTC?

WBTC is a contract representation on Ethereum at 0x2260fac5e5542a773aa44fbcfedf7c193bc2c599. ETH, not WBTC, pays gas unless both symbols are the same. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. 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 Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. 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 Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract.

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

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