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.
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
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:
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.
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.
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
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.
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.
| KEY | MADE | USED FOR | KEPT |
|---|---|---|---|
| Signing key Ed25519 | 2026-11-14 | Every receipt and every tide | Encrypted secret on the API host |
| Post-quantum key ML-DSA-65 (FIPS 204) | 2026-11-14 | The second signature on v3 receipts and tides | Encrypted secret on the API host |
| Timestamp authority ECDSA P-256 | 2026-11-15 | RFC 3161 timestamps for PDFs, code signing and Content Credentials | Encrypted secret on the API host |
| Root CA ECDSA P-256 | 2026-11-15 | Only signs the timestamp authority's certificate and its revocation list | Still on an online machine. Moving it offline is the next step. |
| CERTIFICATE | VALID | SHA-256 FINGERPRINT |
|---|---|---|
| Moon Root CA | 2026-11-15 to 2051-11-15 | 4B: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 Authority | 2026-11-16 to 2046-11-15 | E0: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 |
Could not reach Moon. The keys are at api.moon369.org/v1/keys.
Every change to Moon's keys, newest first. Nothing is ever removed from this list.
| DATE (UTC) | WHAT HAPPENED |
|---|---|
| 2026-11-16 | Timestamp authority certificate reissued with the same key. The earlier certificate stays valid. |
| 2026-11-15 | Root CA and timestamp authority keys created. Timestamps start at /v1/tsa. |
| 2026-11-14 | ML-DSA-65 key created. Receipts move to v3, signed with both keys. |
| 2026-11-14 | Ed25519 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.
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.
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.
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
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:
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.
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.
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
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.
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.
| KEY | MADE | USED FOR | KEPT |
|---|---|---|---|
| Signing key Ed25519 | 2026-11-14 | Every receipt and every tide | Encrypted secret on the API host |
| Post-quantum key ML-DSA-65 (FIPS 204) | 2026-11-14 | The second signature on v3 receipts and tides | Encrypted secret on the API host |
| Timestamp authority ECDSA P-256 | 2026-11-15 | RFC 3161 timestamps for PDFs, code signing and Content Credentials | Encrypted secret on the API host |
| Root CA ECDSA P-256 | 2026-11-15 | Only signs the timestamp authority's certificate and its revocation list | Still on an online machine. Moving it offline is the next step. |
| CERTIFICATE | VALID | SHA-256 FINGERPRINT |
|---|---|---|
| Moon Root CA | 2026-11-15 to 2051-11-15 | 4B: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 Authority | 2026-11-16 to 2046-11-15 | E0: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 |
Loading from api.moon369.org/v1/keys…
Every change to Moon's keys, newest first. Nothing is ever removed from this list.
| DATE (UTC) | WHAT HAPPENED |
|---|---|
| 2026-11-16 | Timestamp authority certificate reissued with the same key. The earlier certificate stays valid. |
| 2026-11-15 | Root CA and timestamp authority keys created. Timestamps start at /v1/tsa. |
| 2026-11-14 | ML-DSA-65 key created. Receipts move to v3, signed with both keys. |
| 2026-11-14 | Ed25519 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.
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.