Privacy for the Avalanche to Scroll direction
Where offered, Private Route is intended to reduce an obvious direct association between the Avalanche sending wallet and Scroll receiving wallet; it does not hide either blockchain. AVAX is the native gas asset for Avalanche. EVM 0x account address ETH is the native gas asset for Scroll. EVM 0x account address Similar amounts, timing, address reuse, and later consolidation can still add association signals. Identity requirements must be checked separately.
Avalanche source-side visibility
Avalanche exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. Its C-Chain is the EVM execution chain in the Avalanche primary network and uses Snowman consensus. C-Chain assets and addresses belong to that execution environment; X-Chain or P-Chain transfers are not substitutes for a C-Chain route. The source deposit, gas funding, asset representation, confirmations, and sending-address history remain outside any promise of invisibility.
Scroll destination-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 destination delivery and later activity can remain observable even when the provider path reduces a direct association.
Avalanche deposit role versus Scroll receipt role
An Avalanche source route uses C-Chain Snowman execution and AVAX gas; X-Chain or P-Chain balances are not valid C-Chain deposits. Those deposit-side events remain public. A Scroll receipt is an L2 native or contract balance whose proof settlement to Ethereum is a separate milestone; later activity uses ETH on Scroll. The receipt and later activity remain public.
Two EVM histories can still be compared
Avalanche and Scroll use separate chain identifiers, balances, contracts, transaction hashes, and gas records even when address syntax matches. Sequencer inclusion and settlement timing can add further observable milestones.
USDC issuer and contract context
USDC is an issued dollar-oriented stablecoin with canonical, native, and bridged variants across networks. Contract events and issuer controls differ from a network-native gas asset. Both bridge sides can expose contract events, amounts, receiving services, and later transfers; a stable target value does not make those records private or interchangeable.
USDC native, canonical, or bridged evidence; USDC native, canonical, or bridged evidence
The exact USDC representation determines the public contract or native record. Issuer controls, transfer events, receiving services, amount, timing, and later use remain outside any promise of invisibility. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. The source transfer remains public. The exact USDC representation determines the public contract or native record. Issuer controls, transfer events, receiving services, amount, timing, and later use remain outside any promise of invisibility. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset. The destination receipt and later use remain public even when direct wallet association is reduced.
Cross-chain linkability limits
Private routing can reduce direct wallet association, but stablecoin contract events, issuer context, provider observations, source gas, destination receipt, amounts, timing, and later transfers remain visible. An Avalanche source route uses C-Chain Snowman execution and AVAX gas; X-Chain or P-Chain balances are not valid C-Chain deposits. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. A Scroll receipt is an L2 native or contract balance whose proof settlement to Ethereum is a separate milestone; later activity uses ETH on Scroll. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.
Verification status is separate from privacy status
The live provider evaluates the exact stablecoin contract or native label, counter-asset, amount, region, and current policy. Issuer controls and provider identity checks are separate, and neither is waived by Private Route. An Avalanche source route uses C-Chain Snowman execution and AVAX gas; X-Chain or P-Chain balances are not valid C-Chain deposits. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. A Scroll receipt is an L2 native or contract balance whose proof settlement to Ethereum is a separate milestone; later activity uses ETH on Scroll. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.
