A public, on-chain record of every recommendation we publish.
Every published content version and every advisor sign-off in Resilient Kids is hash-anchored on a public consensus log within minutes of emission. You can verify, without our cooperation, that what you read in the app today is the same content our scientific advisors approved on the date stated — and that we have not quietly back-edited anything since.
How verification works
The same audit shape used in scientific publishing — append-only, cryptographically anchored, third-party verifiable — applied to every weekly recommendation.
When a content version is published, we compute a SHA-256 hash of its canonical contents — a fingerprint that changes if even one character changes.
The hash is submitted to a public Hedera Consensus Service topic. The chain returns an on-chain timestamp and a transaction ID we cannot change.
Anyone can fetch our local content, recompute the hash, and confirm it matches what was anchored on the date claimed. We re-verify weekly; drift triggers a public alert.
Every published content version
The full ledger of content versions Resilient Kids has ever shipped. Each row is independently verifiable on the Hedera mirror node.
Pre-launch back-anchoring of historical content versions is in progress. This page will populate the moment our submission worker confirms its first transaction on Hedera mainnet. The architecture (events, queue, projection, periodic re-verifier) is shipped — we’re finishing the chain wire-up.
What this proves
A pediatrician, a parent, a journalist, or a regulator can confirm — independently, in their own browser, without our cooperation — that the recommendation you read in Week 47 of Resilient Kids today is byte-identical to the recommendation our advisors approved on the publication date. Trust without trust.