Source deposit
The route begins with an asset on a source network. The deposit transaction can remain public with its sender, amount, asset, timestamp, gas, approvals, and contract interactions.
How Private Cross-Chain Routing Works
Learn how source deposits, destination delivery, route availability, public records, and wallet-linking limits interact across chains.
What you need to know
How the route executes
The active route can use liquidity, bridging, exchange, or destination execution steps depending on the current quote.
Privacy-focused route structure
Where offered, Private Route is intended to reduce an obvious direct association between the source wallet and destination wallet. The implementation and availability depend on the exact route.
Destination delivery
A separate destination transaction can deliver the output. Its receiving address, amount, asset representation, timestamp, fees, and later activity may remain public.
Why chains require separate checks
Networks use different address models, gas assets, token contracts, confirmation rules, explorers, memo requirements, and finality behavior. The reverse direction can also differ.
Association and claim limits
Amounts, timing, address reuse, later consolidation, provider observations, and external context can still connect activity. Private cross-chain routing cannot promise anonymity or untraceability.
Related routes
How Private Cross-Chain Routing Works FAQs
Why are there usually two transaction hashes?
The source deposit and destination delivery occur on different networks and are separate blockchain transactions.
Is every bridge direction equivalent?
No. Provider support, assets, gas, confirmations, address rules, output, and privacy availability can change by direction.
Does Private Route erase the destination record?
No. Destination delivery can remain public.