ParetoAlpha
The log · public · daily

One line a day, stamped by someone else.

Every day at 02:30 UTC, one fingerprint over every record on the ledger, chained to the day before and stamped by an outside timestamp authority. If any past record were rewritten, the day it was on would no longer match a stamp we cannot forge.

It reveals nothing about any family: not who, not how many records, not what kind. A family holds the path from its own records to each day’s line; it is inside every prudence file.

9 days · each entry names the one before it: unbroken · 9 stamped

Day (UTC)RootStamped byCheck it
2026-10-02c858bc607a102ac0…timestamp.digicert.comentry · token
2026-10-012e7818ce4c30dfdd…timestamp.digicert.comentry · token
2026-09-30970b2548be07dd20…timestamp.digicert.comentry · token
2026-09-294c7108a239a68f6a…timestamp.digicert.comentry · token
2026-09-28375404ea2abf82fd…timestamp.digicert.comentry · token
2026-09-2744dde8312e882a09…timestamp.digicert.comentry · token
2026-09-26ab7ae83cc3adfc49…timestamp.digicert.comentry · token
2026-09-2597549f37e5bedb51…timestamp.digicert.comentry · token
2026-09-2488205e6d4ee918ea…timestamp.digicert.comentry · token
Check a day yourself
curl -o entry.json "https://paretoalphasystems.com/api/log/YYYY-MM-DD?format=entry"
curl -o entry.tsr  "https://paretoalphasystems.com/api/log/YYYY-MM-DD?format=tsr"
openssl ts -reply -in entry.tsr -text | grep "Time stamp"        # when the authority saw it
openssl ts -reply -in entry.tsr -token_out -out token.der
openssl pkcs7 -inform DER -in token.der -print_certs -out chain.pem
openssl ts -verify -data entry.json -in entry.tsr -CAfile /etc/ssl/cert.pem -untrusted chain.pem
# Verification: OK. Change one byte of entry.json and it says FAILED.

The whole log as JSON: /api/log. Each entry’s prev is the SHA-256 of the entry before it; a family’s inclusion path is checked by verify_prudence.py, standard library only.