AUDIT · CHECK MOON WITHOUT TRUSTING MOON

CHECK IT YOURSELF

Everything Moon signs is public. One command re-checks the whole Tideline from scratch, using nothing but Moon's public keys. Keep your own copy, so any change Moon made later would show. And read exactly how Moon's keys were made and are kept, including what isn't done yet.

01

RUN THE AUDIT

ONE COMMAND

Needs Node.js 18 or newer. Exit code 0 means everything checks out; 1 means it found a problem and says which tide.

npx moon369 audit
IN YOUR OWN CODE

The same check as a function, for dashboards, monitors and other auditors.

import { auditTideline, fetchKeys } from 'moon369';

const keys = await fetchKeys();
const report = await auditTideline({ keys });
console.log(report.ok, report.problems);

For every lune since the first receipt, the audit:

  • Rebuilds the tide's root from every entry it lists. One changed, added or dropped receipt changes the root.
  • Checks both of Moon's signatures on the tide: Ed25519 and ML-DSA-65.
  • Checks the chain. Each tide carries the hash of the one before it, so no tide can be swapped, removed or reordered.
  • Checks for gaps. Empty lunes are sealed too, and every lune that has ended must have a tide.
  • Checks the count each tide sealed against the receipts the public log listed.

Options: --from 1928.05.06 starts at a lune, --json prints the report as data, and MOON_API points it at a mirror instead of Moon.

02

KEEP A MIRROR

Save every tide, its exact signed text and its Bitcoin proof. If Moon ever changed a sealed tide, your copy, and the proof already in Bitcoin, would disagree with it.

ON YOUR MACHINE

Writes tide-<lune>.json, tide-<lune>.txt and tide-<lune>.txt.ots to a folder. Check a Bitcoin proof with the OpenTimestamps client.

npx moon369 audit --mirror ./tideline
ots verify ./tideline/tide-1928.05.06.txt.ots
EVERY DAY, ON GITHUB

A free public mirror: this workflow audits Moon daily and commits each tide to your repository. The history of that repository is a record Moon doesn't control.

name: Mirror the Moon Tideline
on:
  schedule: [{ cron: '41 8 * * *' }]
  workflow_dispatch: {}
permissions: { contents: write }
jobs:
  mirror:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: npx -y moon369@latest audit --mirror tideline
      - run: |
          git add tideline
          git -c user.name=mirror -c user.email=mirror@users.noreply.github.com commit -m "Tideline mirror" || exit 0
          git push

Running a public mirror? Tell us at moon369org@proton.me and we'll list it here.

03

WHAT IT PROVES, AND WHAT IT DOESN'T

IT PROVES

  • No sealed tide was changed, removed or reordered after it was published.
  • Every tide was signed with the keys Moon publishes.
  • Every receipt in a sealed tide existed by the time that tide reached Bitcoin.

IT DOESN'T PROVE

  • Who made a file, or that what it says is true. A receipt proves a fingerprint existed at a moment.
  • That Moon logged every receipt. A receipt missing from the Tideline is one to question; check yours.
  • That a receipt is honest if Moon's keys were ever stolen. The beacon in each receipt and the Bitcoin proof limit what a thief could backdate.
04

HOW MOON'S KEYS WERE MADE AND ARE KEPT

Plainly: there was no witnessed key ceremony and no hardware security module. Moon's keys were generated with standard open-source cryptography software in a private cloud workspace, by Moon's operator, then stored as encrypted secrets on the API host. A backup is held privately by the operator. We'd rather tell you that than imply more. What protects you anyway is that every signature is public, and the Tideline and Bitcoin make any later change visible.

KEYMADEUSED FORKEPT
Signing key
Ed25519
2026-11-14Every receipt and every tideEncrypted secret on the API host
Post-quantum key
ML-DSA-65 (FIPS 204)
2026-11-14The second signature on v3 receipts and tidesEncrypted secret on the API host
Timestamp authority
ECDSA P-256
2026-11-15RFC 3161 timestamps for PDFs, code signing and Content CredentialsEncrypted secret on the API host
Root CA
ECDSA P-256
2026-11-15Only signs the timestamp authority's certificate and its revocation listStill on an online machine. Moving it offline is the next step.
CERTIFICATEVALIDSHA-256 FINGERPRINT
Moon Root CA2026-11-15 to 2051-11-154B:B0:02:FD:4F:1F:37:59:97:12:D5:29:89:D7:40:44:5B:25:18:C1:12:D8:1C:39:A5:DA:B3:20:0B:C4:7F:D7
Moon Timestamp Authority2026-11-16 to 2046-11-15E0:0F:AD:61:8E:57:A5:58:F9:E1:57:03:13:49:64:A9:4B:AE:B8:45:13:21:FE:BE:94:B0:09:8E:19:08:4E:A5
THE KEYS MOON PUBLISHES RIGHT NOW

Could not reach Moon. The keys are at api.moon369.org/v1/keys.

05

THE KEY LOG

Every change to Moon's keys, newest first. Nothing is ever removed from this list.

DATE (UTC)WHAT HAPPENED
2026-11-16Timestamp authority certificate reissued with the same key. The earlier certificate stays valid.
2026-11-15Root CA and timestamp authority keys created. Timestamps start at /v1/tsa.
2026-11-14ML-DSA-65 key created. Receipts move to v3, signed with both keys.
2026-11-14Ed25519 signing key created. Signed Moonmarks start.

The rules Moon follows for every key change, including what happens if a key is ever exposed, are in the key promise.

06

NOT DONE YET

  • Root CA offline. The root key moves to offline storage and is used only to renew the timestamp certificate.
  • Hardware keys. Signing keys move into a hardware security module, so the key itself can't be copied.
  • A witnessed ceremony. The next keys are made in a recorded ceremony with an outside witness, and the record is published here.
  • Independent mirrors. At least two public mirrors run by people outside Moon.

Each one gets a dated line in the key log when it's done. Live checks are on Status; the numbers are on the Tideline.