Sasquatch Exchange
TRADE
OrdersSupportAffiliatePrivate Swap

Bridge SOL from Polygon to Sui

FromPolygon
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

Polygon → Sui

Asset

SOL

Source gas

POL

Destination gas

SUI

How the Sasquatch deposit route works

1. Select the source

Choose the SOL asset and Polygon 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

Polygon to Sui: object and account boundary

A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. Polygon 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 SOL 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. 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.

SOL keeps its ticker while changing ledgers

Solana is classified as a native asset for this route. SOL uses a network-specific contract asset on Polygon. The recorded Polygon representation uses 9 decimal places. The Polygon side is contract-tracked rather than a native gas balance. Native SOL exists on one recorded origin network; other network forms require representation checks. 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. The Sui side is contract-tracked rather than a native gas balance. Native SOL exists on one recorded origin network; other network forms require representation checks. SOL leaves as a network-specific contract asset. SOL arrives as a network-specific contract asset.

Polygon to Sui bridge mistakes

Route-specific mistakes include sending on a network other than Polygon; using a destination that is not valid for Sui; running out of POL before the source transaction is submitted; assuming evm and other addresses are interchangeable. A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. 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. 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 SOL → SOL

Polygon 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 Polygon 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 SOL deposit and SOL receipt
  • ✓Compare standard and Private Route options for Polygon → Sui
  • ✓Shows what remains public on Polygon and Sui before you deposit
Check Private Route availability →

Related routes

Private SOL from Polygon 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 answerCan Solana signatures be tracked?FAQ answerCan bridge transactions be traced?Privacy researchPrivate bridge security checklistPrivacy researchHow cross-chain transactions are trackedPrivacy research

Polygon 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 SOL representation leaves Polygon?

SOL is a contract representation on Polygon with 9 decimals at 0xd93f7E271cB87c23AaA73edC008A79646d1F9912. POL, not SOL, pays gas unless both symbols are the same. A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. 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 SOL representation arrives on Sui?

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.

Does the same SOL ticker guarantee the same ledger form?

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

Which gas balances matter for this bridge?

A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. 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 Polygon address merely because a wallet displays both networks.

What wrong-direction mistake can prevent delivery?

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

Can I bridge SOL from Polygon to Sui without KYC?

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