Privacy considerations for BNB 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 BNB on Solana or ARB on Arbitrum activity anonymous or invisible. Solana exposes account keys, transaction signatures, token-account changes, program calls, amounts, fees, and timing. It uses an account-and-program execution model with transaction signatures rather than EVM hashes. SPL tokens use mint and token-account records, and a receiving wallet may need the correct associated token account plus SOL for later activity. 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. BNB pays gas on BNB Smart Chain and is native within the BNB ecosystem. A BEP-20 or externally bridged BNB representation must be distinguished from BNB used directly for BSC gas. 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 Solana
Solana exposes account keys, transaction signatures, token-account changes, program calls, amounts, fees, and timing. It uses an account-and-program execution model with transaction signatures rather than EVM hashes. SPL tokens use mint and token-account records, and a receiving wallet may need the correct associated token account plus SOL for later activity. SOL is the native gas asset for Solana. 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.
Solana source role versus Arbitrum destination role
A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. 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.
Solana source activity and EVM delivery remain inspectable
Solana exposes the source signature, accounts, mint or native balance changes, programs, and SOL fee. Arbitrum exposes the destination 0x account, token contract or native receipt, logs, and later gas funding.
BNB native and token representation evidence; ARB approval and governance-token evidence
BNB pays gas on BNB Smart Chain and is native within the BNB ecosystem. A BEP-20 or externally bridged BNB representation must be distinguished from BNB used directly for BSC gas. The exact deposit representation, amount, timing, and later wallet activity remain observable. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. 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 a direct association between the Solana source account and EVM receiver. The source signature, program and token-account changes, destination contract logs, gas, amounts, and timing remain public. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. 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
Provider policy is evaluated for the exact Solana mint or native asset, the other network representation, amount, and region. Cross-ecosystem wallet compatibility and no-KYC status are separate checks. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. 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.
