POST-QUANTUM

QUANTUM READY

A timestamp has to hold up for decades. Moon is built so a receipt signed today still can't be faked after quantum computers arrive. Here's the threat, what Moon does about it now, and how it keeps up.

01

THE THREAT

Quantum computers won't break everything. They break one specific thing, and for timestamps it's the thing that matters.

Signatures are the weak point

A large enough quantum computer running Shor's algorithm could forge the elliptic-curve signatures most of the internet uses today, including Ed25519.

Backdating becomes possible

For a timestamp, a forged signature means a fake receipt that claims a file existed years ago. That's the attack Moon is built to stop.

Fingerprints hold up

SHA-256, the fingerprint inside every receipt and the Tideline, is a hash. Quantum computers only give a square-root speedup against it, leaving it strong.

Records live for decades

Contracts, patents, archives and evidence need to be provable long after they're signed. Proof has to outlast today's algorithms.

02

WHAT MOON DOES TODAY

Every receipt is signed twice over the same bytes: once with Ed25519, today's standard, and once with ML-DSA-65, NIST's post-quantum standard. A receipt counts only when both signatures check out, so faking one means breaking both.

EVERY RECEIPT, TWO SIGNATURESLIVE
CLASSICALEd25519 · 8efd3211b23533ed
POST-QUANTUMML-DSA-65 · ba9ac6c331f7528a
STANDARDNIST FIPS 204
RECEIPTmoonmark-receipt/3
RULEBoth must check out
POST /v1/verify
{
  "valid": true,
  "signatures": ["Ed25519", "ML-DSA-65"],
  "post_quantum": true,
  ...
}
03

PROOF THAT ISN'T A SIGNATURE

Signatures are only one layer. The Tideline locks every receipt into public records that rest on hashes, the part quantum computers can't undo.

A fingerprint tree

Every receipt goes into a SHA-256 Merkle tree, so its place in the log can be proven with hashes alone.

Anchored on Bitcoin

Each day's tide is stamped into Bitcoin through OpenTimestamps. Rewriting it would mean redoing the hash work stacked on top of it ever since.

Anchored on the XRP Ledger

Checkpoints land on the XRPL within about a minute, a second public record outside Moon's control.

Proof that outlives a break

If a signature scheme ever falls, an anchored receipt still shows it existed before that day, because the record was already public and fixed.

04

BUILT TO UPGRADE

Moon is designed to upgrade its cryptography without breaking anything it has already signed.

Every receipt names its method

Each receipt starts with its version, like moonmark-receipt/3, so anyone knows exactly how to check it.

New algorithms slot in

When stronger standards arrive, Moon adds them as a new receipt version through its open proposals process.

Old receipts keep working

Every version ever issued stays verifiable. Retired keys stay published, and checkers accept every past version.

Re-sealed over time

Through the Tideline, old receipts can be re-anchored with fresh, stronger fingerprints and signatures, so a 2026 receipt is still provable in 2056.

05

CHECK IT YOURSELF

Don't take Moon's word for it. Send any receipt to the open verify endpoint and it reports both signatures. The checking code is open source, so you can read exactly what it does.

curl
curl -s -X POST https://api.moon369.org/v1/verify \
  -H "Content-Type: application/json" \
  -d '{"receipt": {...}}'
# { "valid": true, "post_quantum": true, ... }

SIGN SOMETHING

Choose a file and get a signed Moonmark in seconds. Your file never leaves your device.

TRY IT