Sources
The primary documents behind MOAT's claims. A reading list, not a news feed; none of these authors endorse MOAT.
FIPS 204: Module-Lattice-Based Digital Signature Standard (ML-DSA)
The standard behind every MOAT seal. It defines ML-DSA-44, -65 and -87, their key and signature sizes, and the context strings used to keep signatures for one purpose from being reused for another.
FIPS 205: Stateless Hash-Based Digital Signature Standard (SLH-DSA)
Signatures whose security rests on hash functions alone. Much larger than ML-DSA, but a hedge in case lattice assumptions ever weaken.
FIPS 203: Module-Lattice-Based Key-Encapsulation Mechanism Standard (ML-KEM)
For agreeing on shared keys, not for signing. Worth reading to see what the post-quantum toolbox covers, and what a key-exchange scheme can't do for a blockchain.
NIST IR 8547 (initial public draft): Transition to Post-Quantum Cryptography Standards
NIST's proposed timeline for retiring quantum-vulnerable algorithms such as ECDSA and EdDSA: deprecated from 2030, disallowed from 2035.
Polynomial-Time Algorithms for Prime Factorization and Discrete Logarithms on a Quantum Computer
The algorithm the whole field is preparing for. On a large fault-tolerant quantum computer it solves the discrete-logarithm problem that elliptic-curve keys depend on.
Quantum Resource Estimates for Computing Elliptic Curve Discrete Logarithms
Counts the qubits and gates Shor's algorithm would need against roughly 256-bit elliptic curves, the class Ed25519 belongs to. Useful for separating real timelines from noise.
RFC 8032: Edwards-Curve Digital Signature Algorithm (EdDSA)
The specification of Ed25519, the scheme that signs every Solana transaction. Its 32-byte public keys are what Solana addresses encode.
Accounts
Why a Solana address is a public key, and why program-derived addresses sit off the curve with no private key at all. The basis of the scanner's Solana verdicts.
Transactions
What a transaction carries and what each signature covers. Background for reading the create_v2 instruction MOAT decodes before it seals a launch.
BIP-341: Taproot
Taproot outputs commit to a public key directly rather than to its hash. That's why the scanner treats bc1p addresses as exposed from the moment they exist.
noble-post-quantum
The JavaScript ML-DSA implementation MOAT uses, on the server to seal and in your browser to verify. Read its notes on security before relying on it for anything of your own.
Relay: HyperEVM and Hyperliquid support
The bridge leg. Every crossing quote on this site is a Relay quote from SOL on Solana to native HYPE on HyperEVM (chain 999).
How to use the HyperEVM
Where MOAT tokens live: chain id 999, HYPE as the gas token, and the RPC the live readout reads blocks and gas prices from.