public verification
Once a day, each school’s record is reduced to a single fingerprint and timestamped by an independent public service that nobody can alter. A school shares its verification page with families; the page shows every day’s fingerprint, where it stands, and how to check it yourself.
integrity and privacy →The school gives families its verification address; type the last part of it here.
how it works
The record itself never leaves the school. Only a fingerprint does.
Every entry carries a hash of the one before it. Change one and every later hash breaks.
At 00:30 UTC the day’s entry hashes are combined into one Merkle root, the fingerprint.
The fingerprint goes to an independent timestamp service and is confirmed in a public record within a day.
The proof is checked against the block’s own Merkle root and published here with the block number.
questions
Nothing on a verification page identifies a child, a teacher or an act.
One fingerprint per school per day: a hash computed from that day's entries, the number of entries, and the proof that places the fingerprint in the public record. Never an entry, a name, a note or a point.
Yes. The day's page lists the entry hashes and the rule for combining them, so you can recompute the fingerprint yourself; the proof file verifies with the open-source OpenTimestamps client against the public record.
OpenTimestamps: a free, open-source notary that writes a fingerprint into a public ledger nobody controls (the Bitcoin ledger), so the date it existed can never be changed. We use it as a clock nobody can turn back. No money changes hands, and no personal data is involved; the fingerprint is thirty-two bytes that reveal nothing.
The fingerprint has been accepted by the public timestamp calendars and is waiting to be written into a block, which takes up to a day. Once it is, the page shows the block and the check against it.
“a proper system where nobody can touch it.”
Mohanji’s one technical requirement