Privacy for the Sui to Avalanche direction
Where offered, Private Route is intended to reduce an obvious direct association between the Sui sending wallet and Avalanche 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 AVAX is the native gas asset for Avalanche. 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.
Avalanche destination-side visibility
Avalanche exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. Its C-Chain is the EVM execution chain in the Avalanche primary network and uses Snowman consensus. C-Chain assets and addresses belong to that execution environment; X-Chain or P-Chain transfers are not substitutes for a C-Chain route. The destination delivery and later activity can remain observable even when the provider path reduces a direct association.
Sui deposit role versus Avalanche 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. An Avalanche destination must be a C-Chain-compatible account; native AVAX can fund later C-Chain gas, while token receipt uses the quoted C-Chain contract. The receipt and later activity remain public.
USDC issuer and contract context
USDC is an issued dollar-oriented stablecoin with canonical, native, and bridged variants across networks. Contract events and issuer controls differ from a network-native gas asset. Both bridge sides can expose contract events, amounts, receiving services, and later transfers; a stable target value does not make those records private or interchangeable.
USDC native, canonical, or bridged evidence; USDC native, canonical, or bridged evidence
The exact USDC representation determines the public contract or native record. Issuer controls, transfer events, receiving services, amount, timing, and later use remain outside any promise of invisibility. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. The source transfer remains public. The exact USDC representation determines the public contract or native record. Issuer controls, transfer events, receiving services, amount, timing, and later use remain outside any promise of invisibility. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset. The destination receipt and later use remain public even when direct wallet association is reduced.
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. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. An Avalanche destination must be a C-Chain-compatible account; native AVAX can fund later C-Chain gas, while token receipt uses the quoted C-Chain contract. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.
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. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. An Avalanche destination must be a C-Chain-compatible account; native AVAX can fund later C-Chain gas, while token receipt uses the quoted C-Chain contract. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.
