LEGION empire ledger — notary hash chain
What this is: an append-only, hash-chained ledger (empire_ledger.jsonl, 17 entries, 2026-09-25 → 2026-10-10).
Each notary_day entry records the SHA-256 and size of LEGION's internal snapshot files and of the local SQLite
database files of LEGION agents on that day, so that a later silent modification of those files is detectable.
It contains fingerprints only: no data, no measurement, no claim about any third party.
What it is not: it does not prove that the fingerprinted files are true, sourced or up to date. It is not updated in real time; the last entry is dated 2026-10-10.
Correction (2026-10-12): how to read counts.datasets
In each notary_day entry, counts.datasets (129 on 2026-09-25 … 586 on 2026-10-10) is the number of local
SQLite database files of LEGION agents fingerprinted that day (agent-*/*.db). It is not a number of published
datasets, nor of sourced or up-to-date datasets, and must not be quoted as such. The entries are hash-chained and are
deliberately not rewritten (rewriting them would break the chain); this note corrects how the field must be read.
Verify
python3 verify_kit.py # downloads the ledger, checks the hash chain and the Ed25519 signature of the file
Signing key: legion-receipt-key.json (SHA-256 of the raw key a7c6a35b1c2c81d589a30c2ad628679bdea9da4139d49aa3c42cdde6e1c65036, to be checked out of band).
License
CC BY-NC 4.0.
- Downloads last month
- 316