delphi.consensus.snapshot
Appended 24 Aug 2026, 05:31 UTC. Its place in the chain is fixed by the hash of the entry before it; what follows is whether that place is covered by a signature.
The entry
- sequence_
number - 756
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id cd22f6a9-1eb7-4927-a2e9-6736a77b75cc- logged_
at 2026-08-24T05:31:21.429396+00:00- previous_
hash f78deae3cd0c198f7c06cb35eeb277073a8a2f470a175406e26ad5e204d5d6f5- payload_
hash 970cde5995cb6eecc32dcd3e8413291893948f9100dfef5c13af45b91c5a8a4d- entry_
hash 41c664147a6e6ec7f1bf49b5e07d4c035176a4096cfdf3906e742c880d1ab75b
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-24T05:31:21.426604Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "cd22f6a9-1eb7-4927-a2e9-6736a77b75cc",
"series_commitment": "4ec29202ae184acfeb21592a3ac8131be2da12d8b29ec283e564f7398fb98951",
"commitment_version": "v2"
}Shown indented so it can be read. The hash is taken over the canonical form of the same object — keys sorted by code point, no insignificant whitespace, UTF-8 rather than escaped ASCII, timestamps RFC 3339 in UTC to microseconds, decimals as their plain string form. The check below re-encodes the object canonically before hashing it, which is why an indented display cannot make it pass or fail.
Which digest recipe applies
The entry names its own version, so a reader can pick the right recipe without knowing when the salt was introduced.
sha256(canonical_json({question_id, computed_at, salt, readings})), where readings is the batch's populations sorted by population, each carrying exactly {population, method, method_version, sample_size, distinct_operator_count, value}
- salt
eca27646d80c61d9c5cf28c2e989f265541491b97fcf87c16d2bf446f6ac81b1- readings
- 5
- recompute
- sha256(canonical_json({question_id, computed_at, salt, readings})) must equal series_commitment in the payload above. Take question_id and computed_at from that payload verbatim, sort readings by population, and give each reading exactly the six keys served here — the values carry their stored precision and are hashed as the decimal strings they appear as
Verify it here
Recomputing the hashes in this browser… If this sentence stays, this browser has no Web Crypto and nothing here has been verified locally.
The proof, as served
- leaf_
index - 756
- tree_
size - 2341
- leaf_
hash 9767fef661db3cb62801ea172272155f3d1fcc3b6ea1cd56c5acef2f857b98dd- audit_
path (12) 0: 9284d2230d9d01ead814d156cec7aeb953aef4ff476b38d98328f075216d8b261: 70a176b5552783caf6b7a99997860390b43aca03924b261bd41d61bc82a66f502: 3dcb17761ae65c7de7b4989f6c123c85bb7dd79a715a123790f8fbfd009289b03: 55d5df2eaa0215b6d72a9297403a47ec36784b72c6399511c284bc19709a57a44: 572dcf66952f4e8587b10a8c21369b7d51d6a0a18ca3a80837e3a343e014bc175: f61c26919896eb83bd50507688cc1ccfc0bb60fc4cb57a63d694786e83bb71096: 973deb9be25f19e01b3343769d1f20b7f7bf6fe2638c57970f015700d2ee78897: 9580dc2d498dc3b39d2b35bfb7dd13e8996199674c5dfe44e04c8ccc43e9c0d88: 1ed805746441fabcaa9e107f622f886b1692796b8a67f3eaf5f2122c01401d239: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: bd18df2de60e205be411a53ea96887ec76f5a16c15250bf48e3f90dc788abbaf- root_
hash 9f32e37b52a81f4fc0f11a1b956464ef6acde09c58b0ce26dc44277199cb7df0
The earliest published head that covers this entry
- tree_
size - 767
- signed at
- 24 Aug 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash a28d9edb9694f1cda2f626078fae254accc380b4f2549aa7194ad4e4bd63a67a- signature
JMkjMTErBa2bqo2Rs6CcdmWk6Ehro+QvUn6ngPbf4o9ZZnLXtGSJxijgC+C0p5sEaXG37JHg4YRCxAbtVD1mCw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12