Sasquatch Exchange
TRADE
OrdersSupportAffiliatePrivate Swap

Swap LINK on Scroll to SOL on 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.
SOL / USD
Price
—
24h
—
High
—
Low
—
Vol
—

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.

LINK input versus SOL output representation

LINK is a contract-token input, so the source wallet needs the network’s native gas asset and may need to approve the exact LINK contract. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.

Mistakes specific to LINK Scroll to SOL Sui

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. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. LINK is a contract-token input, so the source wallet needs the network’s native gas asset and may need to approve the exact LINK contract. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.

LINK input identity and handling

Chainlink is classified as a governance or utility token for this route. LINK uses a network-specific contract asset on Scroll. The Scroll side is contract-tracked rather than a native gas balance. LINK is a contract-token input, so the source wallet needs the network’s native gas asset and may need to approve the exact LINK contract.

SOL output identity and receiving

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 receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.

Private Route for LINK → SOL

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

No-KYC and verification rulesPrivate LINK to SOL route explainerPrivacy limits and live availabilitySwap SOL to LINKReverse routeChainlink (LINK)Solana (SOL)Scroll networkSui networkBrowse supported swap routes

Swap LINK on Scroll to SOL 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 Scroll as LINK?

LINK is a contract representation on Scroll at 0x548c6944cba02b9d1c0570102c89de64d258d3ac. ETH, not LINK, 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. LINK is a contract-token input, so the source wallet needs the network’s native gas asset and may need to approve the exact LINK contract.

What exactly arrives on 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 receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.

Why does the LINK to SOL direction matter?

LINK is a contract-token input, so the source wallet needs the network’s native gas asset and may need to approve the exact LINK contract. On receipt, Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.

What changes between the source and destination asset roles?

LINK is the deposited token input; SOL is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.

What should be matched before sending LINK?

LINK is a contract-token input, so the source wallet needs the network’s native gas asset and may need to approve the exact LINK contract. 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. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.

What funds the Scroll source transaction?

ETH is the native gas asset for Scroll. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. LINK is token-tracked and can need approval before transfer.

Can I swap LINK on Scroll to SOL on Sui without KYC?

Requirements are checked for the live LINK Scroll to SOL 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 →