Privacy for the Bitcoin to Ethereum direction
Where offered, Private Route is intended to reduce an obvious direct association between the Bitcoin sending wallet and Ethereum receiving wallet; it does not hide either blockchain. BTC is the native gas asset for Bitcoin. Native Bitcoin address supported by the route, including network-specific bech32 or legacy formats ETH is the native gas asset for Ethereum. EVM 0x account address Similar amounts, timing, address reuse, and later consolidation can still add association signals. Identity requirements must be checked separately.
Bitcoin source-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 source deposit, gas funding, asset representation, confirmations, and sending-address history remain outside any promise of invisibility.
Ethereum destination-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 destination delivery and later activity can remain observable even when the provider path reduces a direct association.
Bitcoin deposit role versus Ethereum receipt role
A Bitcoin source spends UTXOs, creates a fee-bearing transaction and possible change, and waits for the route provider’s confirmation depth. Those deposit-side events remain public. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. 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. A Bitcoin source spends UTXOs, creates a fee-bearing transaction and possible change, and waits for the route provider’s confirmation depth. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract.
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 Bitcoin source spends UTXOs, creates a fee-bearing transaction and possible change, and waits for the route provider’s confirmation depth. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract.
