Privacy for the Scroll to Bitcoin direction
Where offered, Private Route is intended to reduce an obvious direct association between the Scroll sending wallet and Bitcoin receiving wallet; it does not hide either blockchain. ETH is the native gas asset for Scroll. 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.
Scroll source-side visibility
Scroll exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is a bytecode-compatible zero-knowledge EVM rollup that proves batches to Ethereum. Scroll inclusion and Ethereum proof settlement are distinct, and its token contracts must be verified independently from L1. 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.
Scroll deposit role versus Bitcoin receipt role
A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. 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 Scroll 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 Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. 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 Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. A Bitcoin destination creates a UTXO at a supported Bitcoin address; later spending pays a BTC miner fee and begins new confirmation progress.
