Sasquatch Exchange
TRADE
OrdersSupportAffiliatePrivate Swap

Private Base to Sui Bridge

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

What you need to know

Privacy for the Base to Sui direction

Where offered, Private Route is intended to reduce an obvious direct association between the Base sending wallet and Sui receiving wallet; it does not hide either blockchain. ETH is the native gas asset for Base. EVM 0x account address SUI is the native gas asset for Sui. Sui hexadecimal account address with an object-based asset model Similar amounts, timing, address reuse, and later consolidation can still add association signals. Identity requirements must be checked separately.

Base source-side visibility

Base exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is an OP Stack optimistic rollup that batches L2 execution and settles to Ethereum. The same 0x wallet can display different balances on Base and Ethereum, and a token contract on one chain does not identify the representation on the other. The source deposit, gas funding, asset representation, confirmations, and sending-address history remain outside any promise of invisibility.

Sui destination-side visibility

Sui can expose addresses or accounts, transfers, amounts, fees, and timing according to its other transaction model. It uses an object-centric Move execution model in which owned and shared objects participate in transactions. Sui addresses and coin objects are not EVM token contracts, and SUI is required for gas and storage-related execution. The destination delivery and later activity can remain observable even when the provider path reduces a direct association.

Base deposit role versus Sui receipt role

A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. Those deposit-side events remain public. 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 receipt and later activity remain public.

Cross-chain linkability limits

Private routing can reduce direct association across Sui objects and the other ledger account. Move object changes, gas, the other-network receipt, amounts, timing, and later transfers remain public. A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance.

Verification status is separate from privacy status

Support for the exact Sui coin type or object-side asset, other network representation, amount, and region is evaluated by the live provider. Privacy intent does not establish no-KYC status. A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance.

Private Route for USDC → USDC

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

Related routes

Base to Sui standard bridgeStandard routePrivate Sui to Base optionsReverse privacy-intent routePrivate Base bridge routesPrivate Sui bridge routesPrivate bridge directoryHow private cross-chain routing worksBridge Sui to BaseReverse routeBridge Arbitrum to SuiRelated network route

Private Base to Sui Bridge FAQs

What must be verified for a private Base to Sui bridge?

Check the exact source and destination asset representations, live privacy status, provider, amount, region, source gas, destination address, fees, and any verification request. Standard bridge support is not proof of private availability.

Which Base bridge records remain public?

Base exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is an OP Stack optimistic rollup that batches L2 execution and settles to Ethereum. The same 0x wallet can display different balances on Base and Ethereum, and a token contract on one chain does not identify the representation on the other. The deposit, gas funding, representation, confirmations, amount, and sending-address history remain observable.

Which Sui records remain public after receipt?

Sui can expose addresses or accounts, transfers, amounts, fees, and timing according to its other transaction model. It uses an object-centric Move execution model in which owned and shared objects participate in transactions. Sui addresses and coin objects are not EVM token contracts, and SUI is required for gas and storage-related execution. Delivery and later activity remain observable even if the provider path reduces direct wallet association.

Does private Base to Sui bridging guarantee no KYC?

Support for the exact Sui coin type or object-side asset, other network representation, amount, and region is evaluated by the live provider. Privacy intent does not establish no-KYC status. A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance.

View all Help Center FAQs →