Pay in SOL.
Land on Hyperliquid.
MOAT is the drawbridge. Sign once in your Solana wallet: Relay carries the SOL across as HYPE in seconds, and your coin goes live on HyperEVM with its first buy already in. No second wallet, no bridge tab, no gas to find. Every crossing gets a receipt sealed with ML-DSA-65.
One signature on Solana. A live coin on HyperEVM.
This is the real route, quoted live: what you send, what lands, what the crossing costs and how long it takes. Pick an amount. Nothing here asks for a wallet.
Five chores on the far bank, or one on yours.
Launching on Hyperliquid from Solana today means leaving your wallet behind. MOAT keeps you on the side you already hold.
- 01Buy HYPE somewhereA CEX account, or a swap you then have to bridge out
- 02Bridge to HyperEVMPick a bridge, pick a route, wait, hope it's the right chain
- 03Fund an EVM walletInstall one, keep gas in it, guard a second seed phrase
- 04Find a launchpadLearn a new UI and a new set of fees
- 05Deploy and buyTwo more signatures, and a bot sees you between them
Three rings, each one you can check.
A moat is the water no one crosses without the bridge. MOAT maps its tools onto the fort's rings, and every one of them runs on public data you can inspect.
See what is exposed
The open ground in front of the walls. The Exposure Scanner reads Solana, Ethereum-style (HyperEVM) and Bitcoin addresses live and tells you whether the public key is already out there.
Exposure ScannerCross on a live quote
The Crossing Desk quotes SOL → HYPE through Relay at any size, with the HyperEVM gas a launch burns, before you sign anything. The number you see is the route you get.
Crossing DeskProve what happened
Every crossing gets one receipt that binds both chains: the Solana deposit, the Relay fill and the HyperEVM deploy, hashed and sealed with a 3,309-byte ML-DSA-65 signature.
Seal VerifierCrossed, deployed, sealed.
A token reaches the board only after the server reads both sides back: the SOL deposit on Solana and the factory deploy on HyperEVM. Then it gets its seal.
The first token launched here gets receipt number one.
One receipt for two chains, with a signature built to outlast the curves.
- 01Both legs, one body
The Solana deposit, the Relay request and the HyperEVM deploy serialised together with sorted keys and no whitespace, so every verifier hashes identical bytes.
- 02SHA-256 digest
Catches any edit to the body. On its own it proves consistency, not authorship: anyone can recompute a digest.
- 03ML-DSA-65 seal
A FIPS 204 lattice signature over the body, bound to the context string moat/crossing-receipt/v2. That's what proves MOAT issued it.
- 04Two-chain attestation
The verifier fetches the Solana transaction and the HyperEVM receipt and checks both against what the seal claims.
{"type": "moat.crossing-receipt","version": 2,"status": "sealed","deposit": {"chain": "solana:mainnet","wallet": "<your Solana wallet>","lamports": 0,"signature": "<base58 signature>","slot": 0},"bridge": {"via": "relay","requestId": "<0x…>","hypeIn": "<wei>"},"launch": {"chain": "eip155:999","factory": "<MOAT factory 0x…>","token": {"address": "<0x…>","name": "<name>","symbol": "<TICKER>","metadataUri": "<https://…>"},"creator": "<your 0x address>","firstBuyWei": "0","transaction": {"hash": "<0x…>","block": 0}},"issuedAt": "<ISO time>","digest": {"alg": "SHA-256","value": "<64 hex chars>"},"seal": {"alg": "ML-DSA-65","keyId": "<16 hex chars>","context": "moat/crossing-receipt/v2","signature": "<3,309 bytes, base64>"}}
Two chains, two curves, two keys in view.
A crossing touches an Ed25519 key on Solana and a secp256k1 key on HyperEVM. Shor's algorithm turns a visible public key into its private key, so it matters when each one goes public.
| Address type | What the address is | Key becomes public | Before first use |
|---|---|---|---|
| Solana wallet | The Ed25519 public key itself | Immediately | exposed |
| HyperEVM / Ethereum account | Last 20 bytes of Keccak-256(public key) | At the first signed transaction | hashed |
| Bitcoin Taproot (bc1p…) | A tweaked secp256k1 public key | Immediately | exposed |
| Bitcoin P2PKH / P2WPKH | HASH160 of the public key | At the first spend | hashed |
| Contract (MOAT factory, curves) | No private key behind it | Never: there's no key | keyless |
No quantum computer that can run Shor's algorithm at this scale exists today. This is about how long a key has been on display when one does.
The algorithms, side by side.
NIST finalised its first post-quantum standards in August 2024. Bigger keys and signatures are the price of not relying on elliptic curves.
| Scheme | Standard | Family | Public key | Signature | Against Shor | Role here |
|---|---|---|---|---|---|---|
| Ed25519 | RFC 8032 | Elliptic curve | 32 B | 64 B | Broken by Shor | Signs your SOL deposit on Solana |
| secp256k1 | SEC 2 | Elliptic curve | 33 B | 65 B | Broken by Shor | Signs every HyperEVM transaction |
| ML-DSA-65 | FIPS 204 | Module lattice | 1,952 B | 3,309 B | Designed to resist | Seals every MOAT crossing receipt |
| SLH-DSA-128s | FIPS 205 | Stateless hash-based | 32 B | 7,856 B | Designed to resist | The conservative fallback: rests on hash functions alone |
What MOAT is not.
The fastest way to lose trust in a launchpad is to oversell it, so here is the boundary.
It proves MOAT recorded a specific crossing. Your Solana and HyperEVM transactions are still Ed25519 and secp256k1, and no off-chain signature changes that.
Relay's solvers fill the HYPE side. MOAT shows the live quote before you sign and checks the fill afterwards, but it doesn't custody the funds in between.
The rate is live and refreshes every 20 seconds. What you sign carries a minimum out; below it, Relay refunds the SOL instead of filling.
It's an ERC-20 on chain 999 with a bonding curve, not a HIP-1 spot listing on HyperCore. Graduation to an AMM pool follows the curve's rules.
Lower the drawbridge.
Name it, ticker it, sign it in Phantom. It lands on Hyperliquid with the receipt already sealed.