Privacy considerations for SUI to ARB
Where offered, Private Route is designed to reduce an obvious direct association between the sending wallet and received assets; it does not make SUI on Sui or ARB on Arbitrum activity anonymous or invisible. 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. Arbitrum exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. Its Nitro optimistic-rollup design executes through a sequencer and posts compressed transaction data to Ethereum. L2 inclusion and Ethereum settlement are separate milestones, so a source receipt can advance before the rollup state is final on L1. SUI is the native coin used for gas in Sui’s object-centric Move model. A token carrying the SUI ticker outside that object model is not a native Sui coin object. ARB is a governance token and does not pay Arbitrum transaction gas; ETH remains the gas asset. A bridged ARB contract on another network is a separate representation from the Arbitrum token. Token contracts, approvals, wallet reuse, recognizable amounts, close timing, and later consolidation can create association signals. Private routing changes only part of that observable transaction context. Identity-verification requirements are separate and must be checked in the live flow.
What remains visible on Sui
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. SUI is the native gas asset for Sui. Reusing the sending address, approval pattern, or recognizable amount can preserve source-side context.
What remains visible on Arbitrum
Arbitrum exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. Its Nitro optimistic-rollup design executes through a sequencer and posts compressed transaction data to Ethereum. L2 inclusion and Ethereum settlement are separate milestones, so a source receipt can advance before the rollup state is final on L1. Receiving-address reuse, immediate consolidation, and later transfers can create destination-side associations.
Sui source role versus Arbitrum destination role
A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. Those source-side events remain visible. An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately. That receipt and later destination activity remain visible.
SUI coin-object evidence; ARB approval and governance-token evidence
SUI coin-object changes, ownership, gas, and later Move interactions remain public on Sui. Tokenized SUI on another ledger creates a different public record. Native SUI is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model. Those source events remain public. Token allowances, contract transfers, voting or utility interactions, source gas, and later wallet consolidation can remain visible for this receipt. A receiving wallet should show the exact ARB contract on the destination. Receipt does not fund ETH gas for later token movement. The receipt and later destination use remain public.
What Private Route changes—and what it does not
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. Native SUI is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model. An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately. A receiving wallet should show the exact ARB contract on the destination. Receipt does not fund ETH gas for later token movement.
Verification and provider policy for this exact route
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. Native SUI is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model. An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately. A receiving wallet should show the exact ARB contract on the destination. Receipt does not fund ETH gas for later token movement.
