Privacy for the Bitcoin to zkSync Era direction
Where offered, Private Route is intended to reduce an obvious direct association between the Bitcoin sending wallet and zkSync Era 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 zkSync Era. 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.
zkSync Era destination-side visibility
zkSync Era exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is a zero-knowledge rollup using EraVM and native account-abstraction features while settling proofs to Ethereum. Execution, fee estimation, and contract compatibility can differ from a byte-for-byte Ethereum assumption. The destination delivery and later activity can remain observable even when the provider path reduces a direct association.
Bitcoin deposit role versus zkSync Era 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. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. 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 zkSync Era 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. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery.
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. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery.
