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 Base as LINK?
LINK is a contract representation on Base at 0x88fb150bdc53a65fe94dea0c9ba0a6daf8c6e196. ETH, not LINK, pays gas unless both symbols are the same. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
Why does the SOL to LINK 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, LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
What changes between the source and destination asset roles?
SOL is the deposited native-asset input; LINK is the quoted token 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. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
What funds the Sui source transaction?
SUI is the native gas asset for Sui. A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. SOL is token-tracked and can need approval before transfer.
Can I swap SOL on Sui to LINK on Base without KYC?
Requirements are checked for the live SOL Sui to LINK Base 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.