Bridging Operations
Bridging moves $USN or $sUSN from one chain to another. Noon uses Hyperlane and LeyerZero for cross-chain transfers. Follow this step-by-step guide.
Before you bridge
Confirm the origin chain (where your tokens are now) and the destination chain (where you want them).
Make sure you hold a small amount of the native gas token on both chains.
Verify the token contract on both chains against Contracts and Addresses.
Steps
Verify the destination token
Verify the destination token matches the canonical address on Contracts and addresses.
If a bridge gets stuck
Cross-chain transfers can take time to finalise. A transfer can occasionally appear pending longer than expected. See Troubleshooting for what to check and how to get help.
How bridging works
Noon runs two bridging stacks, each fitted to the chains it serves:
LayerZero (OFT) carries $USN and $sUSN between chains. Security on these routes comes from Decentralized Verifier Networks (DVNs): every cross-chain message must be independently verified by three separate DVNs, run by LayerZero Labs, Horizen, and Nansen / Frax and all three must agree (3-of-3) before a transfer is accepted. No single verifier, including LayerZero's own, can pass a message alone. Requiring all three DVNs to agree has a trade-off: if one DVN is unavailable, transfers on that route pause until it comes back online. The design fails safely, toward a delay, and not toward a forged transfer.
Hyperlane (lock-and-mint) carries tokens to the remaining chains, locking supply on the origin chain and minting the representation on the destination, which keeps total supply consistent across chains.
Last updated
Was this helpful?