Sasquatch Exchange
TRADE
OrdersSupportAffiliatePrivate Swap

Bridge WBTC from Scroll to Sui

FromScroll
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.

Direction

Scroll → Sui

Asset

WBTC

Source gas

ETH

Destination gas

SUI

How the Sasquatch deposit route works

1. Select the source

Choose the WBTC asset and Scroll network you currently hold.

2. Review the route

Check the estimated output, fees, timing, and Sui destination network.

3. Create the order

Open the live route and follow the exact deposit instructions.

4. Track delivery

Use the receipt and status page until the destination funds arrive.

What you need to know

Scroll to Sui: object and account boundary

A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. Scroll 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.

WBTC input versus WBTC output representation

WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. 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 keeps its ticker while changing ledgers

Wrapped Bitcoin is classified as a wrapped asset for this route. WBTC uses a wrapped contract asset on Scroll. The recorded Scroll representation uses 8 decimal places. The Scroll side is contract-tracked rather than a native gas balance. 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. The Sui side is contract-tracked rather than a native gas balance. WBTC leaves as a wrapped contract asset. WBTC arrives as a wrapped contract asset.

Scroll to Sui bridge mistakes

Route-specific mistakes include sending on a network other than Scroll; using a destination that is not valid for Sui; running out of ETH before the source transaction is submitted; assuming evm and other addresses are interchangeable; treating a wrapped token as the native gas asset. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. 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. 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 WBTC → WBTC

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

Related routes

Private WBTC from Scroll to Sui route explainerPrivacy limits and live availabilityNo-KYC and verification rulesProvider and region requirementsCan a bridge link source and destination wallets?FAQ answerWhat is cross-chain privacy?FAQ answerWhat is a private crypto swap?FAQ answerCan bridge transactions be traced?Privacy researchPrivate bridge security checklistPrivacy researchHow cross-chain transactions are trackedPrivacy research

Scroll to Sui FAQs

Which side uses Sui coin objects and SUI gas?

Sui is the Sui side. Its Move coin types, address, objects, and SUI gas do not transfer as EVM contract metadata.

What WBTC representation leaves Scroll?

WBTC is a contract representation on Scroll with 8 decimals at 0x3C1BCa5a656e69edCD0D4E36BEbb3FcDAcA60Cf1. ETH, not WBTC, pays gas unless both symbols are the same. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer.

What WBTC representation arrives on Sui?

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.

Does the same WBTC ticker guarantee the same ledger form?

No. This bridge keeps the asset intent while moving between a WBTC wrapped token and a WBTC wrapped token. Match the source and output details in the live quote.

Which gas balances matter for this bridge?

A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. The bridge output does not automatically fund every later gas need.

What destination address should be used?

Sui hexadecimal account address with an object-based asset model Do not substitute a Scroll address merely because a wallet displays both networks.

What wrong-direction mistake can prevent delivery?

Sending on a network other than Scroll, selecting a representation not listed by the quote, or entering an address invalid for Sui can prevent normal detection or receipt.

Can I bridge WBTC from Scroll to Sui without KYC?

Requirements are checked for the live WBTC Scroll to 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 bridge FAQs →