Privacy for the Ethereum to Bitcoin direction
Where offered, Private Route is intended to reduce an obvious direct association between the Ethereum sending wallet and Bitcoin receiving wallet; it does not hide either blockchain. ETH is the native gas asset for Ethereum. 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.
Ethereum source-side visibility
Ethereum exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is the settlement-layer EVM network for this inventory. ERC-20 transfers can require a separate approval, base fee and priority fee affect source cost, and an L1 token contract does not establish an L2 representation. 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.
Ethereum deposit role versus Bitcoin receipt role
An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. 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 Ethereum 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. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. 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. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. A Bitcoin destination creates a UTXO at a supported Bitcoin address; later spending pays a BTC miner fee and begins new confirmation progress.
