Across networks.
Not away from the terms.
A leg can move beyond its home network. Its structure, accounting and settlement still deserve a complete view.
Explore the transfer flow
Three stages.
No missing middle.
Follow an outbound leg or trace its return. This walkthrough describes the published mechanism; it does not verify current route availability.
Start with the original position.
An eligible leg is locked on its home chain. The source receipt is the beginning of a transfer, not proof of arrival.
Same underlying.
A different location.
Where a token appears and where its collateral settles are different questions. Keep both visible, from the first quote to the final receipt.
Read the architecture- Home-chain collateral
- Original note escrow and settlement
- Destination representation
- A mirror of the eligible leg
- Cross-chain messaging
- Published LayerZero-based mechanism
- Before you move
- Verify peers, fees, permissions and current message state
Know what moves.
And what does not.
Does moving a leg move its underlying collateral?
The protocol keeps the original collateral on the home chain. A destination mirror represents the leg; it does not relocate the underlying note escrow.
Can I transfer from this page?
No. Transfers are made in the app’s Omni workspace: a connected wallet selects the leg, the route is validated and reviewed, and the message is signed there.
What should I check before a real transfer?
Read current route peers, verifier settings, fees, leg eligibility, recipient and finality conditions. Cross-chain and smart-contract risk remain even when a route is available.
Mechanics as published in the documentation. Live terms, quotes and balances are read from the contracts in the app, where every transaction is signed by your own wallet.
Open in the appLIVE ON ROBINHOOD CHAIN TESTNET