Sasquatch Exchange
TRADE
OrdersSupportAffiliatePrivate Swap

Swap SOL on Base to USDT on Sui

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.
SOL / USD
Price
—
24h
—
High
—
Low
—
Vol
—

What you need to know

Base to Sui: object and account boundary

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

SOL input versus USDT 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. Confirm whether the output is ERC-20, TRC-20, SPL, or another USDT standard; a wallet supporting one standard may not credit another.

Receiving stablecoin USDT

USDT is issued through ERC-20, TRC-20, SPL, and other network-specific contracts. The ticker does not determine the token standard, contract, issuer controls, or destination address model. The destination wallet must support the exact Sui representation. The route converts a native-asset source into a stablecoin balance; the destination ticker alone is not a contract check.

Mistakes specific to SOL Base to USDT Sui

Route-specific mistakes include sending on a network other than Base; 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; selecting a stablecoin by ticker without checking its network contract. 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. 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 receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. Confirm whether the output is ERC-20, TRC-20, SPL, or another USDT standard; a wallet supporting one standard may not credit another.

SOL input identity and handling

Solana is classified as a native asset for this route. SOL uses a network-specific contract asset on Base. The recorded Base representation uses 9 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.

USDT output identity and receiving

Tether is classified as a stablecoin for this route. USDT uses a network-specific contract asset on Sui. The recorded Sui representation uses 6 decimal places. Confirm whether the output is ERC-20, TRC-20, SPL, or another USDT standard; a wallet supporting one standard may not credit another.

Private Route for SOL → USDT

Base wallet, token-transfer, contract, log, and gas activity remain public, and Sui account, object, transaction-effect, and fee activity remain public. For this SOL on Base to USDT 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 SOL deposit and USDT 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

No-KYC and verification rulesPrivate SOL to USDT route explainerPrivacy limits and live availabilitySwap USDT to SOLReverse routeSolana (SOL)Tether (USDT)Base networkSui networkBrowse supported swap routes

Swap SOL on Base to USDT on Sui 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 Base as SOL?

SOL is a contract representation on Base with 9 decimals at 0x311935Cd80B76769bF2ecC9D8Ab7635b2139cf82. ETH, not SOL, pays gas unless both symbols are the same. 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. 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 Sui as USDT?

USDT is a contract representation on Sui with 6 decimals at 0xc060006111016b8a020ad5b33834984a437aaa7d3c74c18e09a95d48aceab08c::coin::COIN. SUI, not USDT, 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. Confirm whether the output is ERC-20, TRC-20, SPL, or another USDT standard; a wallet supporting one standard may not credit another.

Why does the SOL to USDT 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, Confirm whether the output is ERC-20, TRC-20, SPL, or another USDT standard; a wallet supporting one standard may not credit another.

What changes between the source and destination asset roles?

SOL is the deposited native-asset input; USDT is the quoted stablecoin 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 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. Confirm whether the output is ERC-20, TRC-20, SPL, or another USDT standard; a wallet supporting one standard may not credit another.

Which stablecoin contract must this route match?

USDT must match the quoted Sui representation. A ticker or target price is not enough to identify a token contract.

Can I swap SOL on Base to USDT on Sui without KYC?

Requirements are checked for the live SOL Base to USDT 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 Help Center FAQs →