Wallet signs
Authorised locally with your key — nothing custodial, nothing off-device.
Assets move across chains along verified LayerZero routes — self-custody for the omnichain default, with no bridge to hand your funds to.
You sign once on your desktop. LayerZero carries that message from the source chain to the destination — verified end to end, with no wrapped detour through a bridge you have to trust.
Authorised locally with your key — nothing custodial, nothing off-device.
The signed intent is committed on the chain you're sending from.
The message travels the protocol path, verified before anything lands.
Value settles on the target chain. The route is finished, not half-open.
Your assets already live across many networks. One wallet reads them all and routes between them — no new account per chain, no juggling.
Self-custody means the wallet shows you exactly what you're signing — the destination chain, the path, the message, and where it is in flight. Clarity over promises: you decide, and you can watch it settle.
Chain, asset, amount and recipient sit in one plain view.
The path is shown as a LayerZero message, not a vague bridge action.
Source, verification and destination finality stay legible.
A native build for the machine you keep your keys on. Verify the checksum, run it offline, hold your own custody.
builds are signed · verify before you run · keys never leave the device
Short, honest answers about custody and routing. If something isn't here, the release notes and security page carry the longer version.
Yes. Keys are generated and stored on your device. No server holds your funds and no account we can freeze.
No. Transfers travel as verified LayerZero messages, so you're not handing assets to a separate bridge contract to hold in escrow.
The chains shown route pairwise — send from any to any. New networks are added as they're supported end to end.
Every route shows its status from sign to delivery, including finality on the destination chain. Nothing settles silently.
Your recovery phrase restores the wallet on a new machine. Keep it offline — it's the only thing that controls the keys.
The client is open and the builds are reproducible, so you can check that what you run matches the published source and checksum.