Privacy for the BNB Chain to Arbitrum direction
Where offered, Private Route is intended to reduce an obvious direct association between the BNB Chain sending wallet and Arbitrum receiving wallet; it does not hide either blockchain. BNB is the native gas asset for BNB Chain. EVM 0x account address ETH is the native gas asset for Arbitrum. EVM 0x account address Similar amounts, timing, address reuse, and later consolidation can still add association signals. Identity requirements must be checked separately.
BNB Chain source-side visibility
BNB Chain exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. BNB Smart Chain uses EVM execution with BEP-20 token contracts and BNB for gas. A BEP-20 deposit is not an ERC-20 deposit even when the ticker and 0x address syntax look familiar. The source deposit, gas funding, asset representation, confirmations, and sending-address history remain outside any promise of invisibility.
Arbitrum destination-side visibility
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. The destination delivery and later activity can remain observable even when the provider path reduces a direct association.
BNB Chain deposit role versus Arbitrum receipt role
A BNB Smart Chain source uses BNB gas and BEP-20 contracts; a familiar 0x account does not turn a BEP-20 deposit into ERC-20. Those deposit-side events remain public. 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. The receipt and later activity remain public.
Two EVM histories can still be compared
BNB Chain and Arbitrum use separate chain identifiers, balances, contracts, transaction hashes, and gas records even when address syntax matches. Sequencer inclusion and settlement timing can add further observable milestones.
ARB approval and governance-token evidence; ARB approval and governance-token evidence
Token allowances, contract transfers, voting or utility interactions, source gas, and later wallet consolidation can remain visible for this deposit. Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum. The source transfer remains 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 destination receipt and later use remain public even when direct wallet association is reduced.
Cross-chain linkability limits
Private routing can reduce an obvious link between two EVM accounts, but source approvals, gas, logs, destination contract or native receipt, and later activity remain on separate chain histories. Sequencer and settlement timing can add correlation evidence. A BNB Smart Chain source uses BNB gas and BEP-20 contracts; a familiar 0x account does not turn a BEP-20 deposit into ERC-20. Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum. 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 status is separate from privacy status
The provider must support the exact L2 direction, asset contracts, amount, and region. Rollup support and privacy routing do not imply that identity verification, account, or custody requirements are absent. A BNB Smart Chain source uses BNB gas and BEP-20 contracts; a familiar 0x account does not turn a BEP-20 deposit into ERC-20. Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum. 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.
