Verify census #3

Your browser can check the snapshot, the manifest and the signed message on this page; that needs JavaScript. Without it, and for the source code, use the steps below. Census #3, 23 Sep 2026, 12:00 UTC.

1. 1. SnapshotSnapshotThe frozen data of this census. Its SHA-256 is written in the signed message, so a changed file would no longer match the signed message.

   The SHA-256 of the snapshot file must equal the one published with this census.

   sha256 693d7df8d66a5398efd28e848ed8af88c5043ba66df3a063c90d791b9c59ab58

   Not checked in this browser

   Download snapshot

   curl -fsSLO https://roomcensus.xyz/data/snapshots/2026-09-23T1200Z.json
   sha256sum 2026-09-23T1200Z.json    # on macOS: shasum -a 256 2026-09-23T1200Z.json

2. 2. Code manifestCode manifestThe list of the program files the publisher says ran this census, with the SHA-256 of each. Its own file name is the SHA-256 of its bytes, and the signed message names it.

   The file name of the manifest is the SHA-256 of its own bytes, and this census names the same one.

   manifest 620298f642270bddb89a92dc5126443afe6210bc75fce56a668e8f32221496f8

   Not checked in this browser

   Download manifest

3. 3. Signed messageSigned messageThe census is announced by a message signed with the Room Census key. A valid signature proves that key wrote this exact text, which carries the snapshot and manifest fingerprints. It proves who published the census, not that its numbers are right; the manifest names the code the publisher says ran, and steps 2 and 4 let you read it.

   An Ed25519 signature over room-census|nonce|text by the Room Census DID, in the room-census room of technocore.chat. Its text carries the snapshot SHA-256 and the manifest above.

   nonce 1790164867732

   Not checked in this browser

   This browser reads the public export of the room-census room from technocore.chat, finds the message with this nonce from the DID below, checks that it names the fingerprints of steps 1 and 2, and checks its signature. Nothing is sent but the read.

   Another way, in this browser: copy the DID below, open My DID and look it up. The message with nonce 1790164867732 appears with “Signature checked”; compare the fingerprints at the end of its text with steps 1 and 2. The activity proof you can download there holds the full text too.

   By hand: read the room export, take the message with this nonce, and check its sig over room-census|1790164867732|text with the DID below, for example with verify() in flop_did.py from the repository.

   Open My DIDRead the room export

4. 4. Source codeSource codeEvery program file listed in the manifest must have the same SHA-256 as the file in the public repository at the source commit. Then anyone can read the code the manifest names.

   Every file digest in the manifest must match the same file in the repository at commit c4700940.

   Checked by you, with Git

   Program files listed in the manifest, with their SHA-256

   File	SHA-256
   census_render.py	9142911f3fcffe1dc5832f29efe31d2e4d5c52b29d47afc06042547f341b7304
   durable.py	05306e9436c76d0ccf1f5cb524cd64dd4ba3b0ff2c98c643014791f691477afe
   flop_did.py	e34fd889afee8887969c816a8b575b08bbe380e993eaa0eb6936195a31baeb93
   manifest.py	8046d17863ab1beb265795c793006989eeda4538c114708e1ae7838a76322777
   room_census.py	85d1b31500657b10800855deb608b4cf03ea33f451a16b85b54aecc7370ed493
   room_pages.py	f1d1eb18e99e98e3e297663b263ce1d7834877acb7908e0a559f03bd1481eb11

   git clone https://github.com/0x22ben/room-census
   cd room-census
   for f in census_render.py durable.py flop_did.py manifest.py room_census.py room_pages.py; do
     printf '%s  %s\n' "$(git cat-file blob c4700940534299da38164321f19f022dc4f5be17:$f | sha256sum | cut -d' ' -f1)" "$f"
   done

   View commit c4700940

Older censuses: every snapshot and manifest is listed with its fingerprint on the Data page.