Dispatch 009

A signed ledger for our own claims

Dispatch 009 · Published 2026-10-16 · Updated 2026-10-16

grideos.com now publishes its main factual claims as a hash-chained ledger signed with an Ed25519 key, with an honest status on every entry. A company that argues for provable records should keep its own that way.

Grideōs argues that a record should be provable, not just recorded. As of 16 October 2026 the company applies that to its own website. The main factual claims on grideos.com, from the legal name to the verifier figures, are published as a ledger at grideos.com/facts.

What is in it

Each entry has an ID, the claim in one sentence, links to its evidence and a status that says how far you can rely on it: self-asserted, self-measured, publicly checkable or publicly testable. Most entries are self-asserted, and the ledger says so.

How to check it

Entries are chained by SHA-256 hashes, and the whole ledger is signed with an Ed25519 key published at /.well-known/jwks.json. The facts page carries a short script that checks the signature and the chain with nothing but Node.js. AI assistants and agents can do the same through a read-only MCP endpoint at grideos.com/mcp, which answers questions about Grideōs from the same ledger.

What it does not prove

A signature proves that the ledger came from Grideōs and has not changed since it was signed. It does not prove that a claim is true. That is what the status and the evidence links are for, and it is why the ledger keeps the difference between what Grideōs states and what anyone can test.

All dispatches · Facts ledger · Markdown