Privacy for the Base to Bitcoin direction
Where offered, Private Route is intended to reduce an obvious direct association between the Base sending wallet and Bitcoin receiving wallet; it does not hide either blockchain. ETH is the native gas asset for Base. EVM 0x account address BTC is the native gas asset for Bitcoin. Native Bitcoin address supported by the route, including network-specific bech32 or legacy formats Similar amounts, timing, address reuse, and later consolidation can still add association signals. Identity requirements must be checked separately.
Base source-side visibility
Base exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is an OP Stack optimistic rollup that batches L2 execution and settles to Ethereum. The same 0x wallet can display different balances on Base and Ethereum, and a token contract on one chain does not identify the representation on the other. The source deposit, gas funding, asset representation, confirmations, and sending-address history remain outside any promise of invisibility.
Bitcoin destination-side visibility
Bitcoin exposes a UTXO graph in which inputs, outputs, change, confirmations, and later consolidation can be analyzed. It spends discrete UTXOs rather than debiting an account balance. Input selection creates outputs and often change, confirmation depth matters to the provider, and a native receiving address must match the Bitcoin address types accepted by the active route. The destination delivery and later activity can remain observable even when the provider path reduces a direct association.
Base deposit role versus Bitcoin receipt role
A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. Those deposit-side events remain public. A Bitcoin destination creates a UTXO at a supported Bitcoin address; later spending pays a BTC miner fee and begins new confirmation progress. The receipt and later activity remain public.
UTXO and account-chain evidence around the bridge
The Bitcoin side exposes inputs, outputs, change, confirmation depth, and later spends. The Base side exposes its own account or token history. Comparable amounts and timing can remain correlation signals across those two transaction models.
Cross-chain linkability limits
Private routing can alter the provider-side path between a Bitcoin UTXO record and the other ledger. It cannot erase inputs, outputs, change, confirmations, account receipts, provider observations, or later consolidation. A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. A Bitcoin destination creates a UTXO at a supported Bitcoin address; later spending pays a BTC miner fee and begins new confirmation progress.
Verification status is separate from privacy status
The selected provider can evaluate the exact Bitcoin deposit or delivery, amount, confirmation state, region, and current risk policy. UTXO routing does not itself prove no-KYC status; check any identity request before sending. A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. A Bitcoin destination creates a UTXO at a supported Bitcoin address; later spending pays a BTC miner fee and begins new confirmation progress.
