Privacy considerations for WBTC to SOL
Where offered, Private Route is designed to reduce an obvious direct association between the sending wallet and received assets; it does not make WBTC on Arbitrum or SOL on Solana activity anonymous or invisible. 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. 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. WBTC is a custodial tokenized Bitcoin representation on smart-contract networks. Its transfers use token contracts and approvals rather than native Bitcoin inputs and outputs. Native SOL pays Solana fees and participates in the Solana account model. Wrapped SOL is an SPL token account representation and tokenized SOL on another network is not native SOL. Wrapped assets depend on a token contract and a separate underlying asset model. Wrapper interactions, approvals, unwrap activity, and the destination representation can remain public and may create additional association points. Identity-verification requirements are separate and must be checked in the live flow.
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. ETH is the native gas asset for Arbitrum. Reusing the sending address, approval pattern, or recognizable amount can preserve source-side context.
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. Receiving-address reuse, immediate consolidation, and later transfers can create destination-side associations.
Arbitrum source role versus Solana destination role
On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. Those source-side events remain visible. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. That receipt and later destination activity remain visible.
EVM deposit and Solana receipt create different public records
Arbitrum records the 0x source account, gas, approvals, and token transfer. Solana records the destination account keys, token-account changes, programs, fees, and signature. Private routing can change the direct provider path without making either ecosystem invisible.
Wrapper activity can add another association point
Wrapped-token approvals, transfers, and later unwrap activity are public contract events. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.
WBTC custody-wrapper evidence; SOL fee-payer and account evidence
WBTC approvals, wrapper-contract transfers, custodian-linked mint or burn context, and later unwrap activity remain public. No native Bitcoin UTXO is hidden by a WBTC token transfer. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. Those source events remain public. Native SOL balance changes, fee-payer accounts, signatures, and later token-account activity remain visible on Solana. Tokenized SOL elsewhere follows a separate contract ledger. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native. 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 EVM deposit account and Solana receiving account. The 0x transaction, approval, gas, Solana signature, token-account changes, amounts, and timing remain public evidence. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.
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. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.
