Private Sui to Polygon Bridge

FromSui
ToPolygon
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 Sui to Polygon direction

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

Sui source-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 source deposit, gas funding, asset representation, confirmations, and sending-address history remain outside any promise of invisibility.

Polygon destination-side visibility

Polygon exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. Polygon PoS uses an EVM sidechain architecture with its own validator checkpoints and gas balance. Its token representations and bridge behavior are separate from Ethereum L1 even when wallets use the same 0x account. The destination delivery and later activity can remain observable even when the provider path reduces a direct association.

Sui deposit role versus Polygon receipt role

A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. Those deposit-side events remain public. A Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas. 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 Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. A Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas.

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 Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. A Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas.

Private Route for USDC → USDC

Sui account, object, transaction-effect, and fee activity remain public, and Polygon wallet, token-transfer, contract, log, and gas activity remain public. For this USDC on Sui to USDC on Polygon path, Private Route is intended to reduce the direct visible relationship between activity around the source-side Sui hexadecimal account address with an object-based asset model and destination-side EVM 0x account address; 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 Sui → Polygon
  • Shows what remains public on Sui and Polygon before you deposit
Check Private Route availability →

Related routes

Private Sui to Polygon Bridge FAQs

What must be verified for a private Sui to Polygon 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 Sui bridge records remain public?

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 deposit, gas funding, representation, confirmations, amount, and sending-address history remain observable.

Which Polygon records remain public after receipt?

Polygon exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. Polygon PoS uses an EVM sidechain architecture with its own validator checkpoints and gas balance. Its token representations and bridge behavior are separate from Ethereum L1 even when wallets use the same 0x account. Delivery and later activity remain observable even if the provider path reduces direct wallet association.

Does private Sui to Polygon 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 Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. A Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas.

View all Help Center FAQs →