Choose the exact direction
Identify the source chain, destination chain, asset, amount, and receiving address. The reverse direction can use different providers, gas assets, confirmations, token representations, and privacy availability.
Check supported bridge directions, live privacy availability, two-chain public records, asset representations, gas, and address requirements.
Identify the source chain, destination chain, asset, amount, and receiving address. The reverse direction can use different providers, gas assets, confirmations, token representations, and privacy availability.
Choose the source network, destination network, and exact asset before reviewing privacy options. Private Route availability is checked separately in the live flow.
Private Route status can change with the exact asset, amount, source, destination, provider conditions, and capacity. The live flow is the final source for current availability.
A cross-chain route can create a source deposit transaction and a separate destination delivery transaction. Each can have its own hash, explorer, timestamp, confirmations, fees, and address details.
Check source gas, destination gas, token contracts or native labels, address format, memo or tag requirements, provider, fees, output, minimum received, and quote window.
Where offered, the route can reduce an obvious direct source-wallet to destination-wallet association. Amounts, timing, address reuse, later transfers, provider observations, and other data can still provide association signals.
No. Both blockchain records can remain public.
Provider support, assets, gas, address requirements, and privacy availability can differ when the direction is reversed.
They can provide association signals, especially alongside address reuse, later consolidation, or other context.