How it works
From a form to a sealed receipt in four stages, each with its assumptions stated and its status marked.
- 01
Quote
You fill in the token, your HyperEVM address and a first buy in SOL. MOAT asks Relay for a live SOL → HYPE quote with your wallet as sender, and shows what lands, the minimum out, the crossing cost and the HyperEVM gas the launch burns.
- 02
Cross
You sign one Solana transaction in your own wallet. Its destination action is a call to the MOAT factory on HyperEVM, so the solver that fills the HYPE also triggers the deploy. Below the minimum out, Relay refunds the SOL instead.
- 03
Deploy
The factory clones the token, opens its bonding curve and spends the HYPE on your first buy in one transaction, then sends the tokens and any leftover HYPE to your address. There's no gap between deploy and buy for a bot to use.
- 04
Seal
The server reads both legs back from chain: the Solana deposit and the HyperEVM deploy. The facts are written as canonical JSON, hashed with SHA-256 and signed with ML-DSA-65. Anyone can check the receipt in the Seal Verifier.
| Area | Live now | Not built |
|---|---|---|
| Crossing quotes | Live Relay quotes SOL → HYPE (HyperEVM), Hyperliquid mids, HyperEVM gas | — |
| Token launch | Form, EVM address from your wallet, live cost review | The HyperEVM factory contract (launch gate stays raised until it's deployed) |
| Receipts | SHA-256 digest, ML-DSA-65 seal, browser verifier | Two-chain attestation (ships with the factory) |
| Exposure scan | Live Solana, Ethereum-style and Bitcoin lookups | Off-chain signatures |
| Sources | Primary documents | A live feed |
The post-quantum boundary
read thisML-DSA protects the receipts, which are a separate proof layer. It does not replace the Ed25519 signatures Solana checks or the secp256k1 signatures HyperEVM checks, it doesn't remove custody risk from either wallet, and it says nothing about what a token is worth. Post-quantum signatures on either chain would have to come at the protocol level.