delphi.consensus.snapshot
Appended 1 Sept 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 - 1234
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3707c33d-0301-4c72-8c13-ee685e8a0a88- logged_
at 2026-09-01T05:31:21.137865+00:00- previous_
hash 59ad31fc79a524a560616aa710fdc9ba8a404666d3207791c2fdd943e9d7aab4- payload_
hash 40cb64606cfa0a2c76392099144a372048b0f5284dc5ca556f902e2d44529751- entry_
hash 921e9584a938c3647ed99c5f1823f2c8f146a218f65b6ed796142b6b9fa91ddd
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-01T05:31:21.135306Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3707c33d-0301-4c72-8c13-ee685e8a0a88",
"series_commitment": "998554b8e6394126d58555edbf1270a83600a25c845b4cad6baa165afce3bb8b",
"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
932848f0cdf27e77a805480215c23a62a23fb9fcde0cc60da233e19eb01b7e17- 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 - 1234
- tree_
size - 2239
- leaf_
hash 0d70c82503ba24d0fcc6375ca0111aec3f66325b7ba4048f35f0be91a86067ce- audit_
path (12) 0: 0a36a5a1f13c8e790c07ed3661768ecc4c715a1bb940d47d94f30ebe1a66b4641: e3495fdb36a5a26d71169af1328196d63f8c9fb0be604a75b7f820fd2b049a392: 0def3ccb8af1614a2957b87fcde3013e31a076e84be938c22116d3c4e1445f873: e417a4f135abd0a3547583e0869b74a30b92dd427abce02be6313ee43d05c9e34: 62a65c450111e389fa7495295493df8efd4857c0cadf8512841f78ff850ff71c5: 6457d041f692165a2d435e4fc16b6e2b8617893057f2ad51fdffb8c9363d31346: 669172607016fd0304cbb59132e0f82cb4f48e391f29d72a97f4ceee2d3ffff47: ccb0e9f17cd47f20723bd8ade751778a3fd4e9649264dffce135260eaca872fa8: 6ce18fb0b650e54a2c9454c3e9abde48f8386826f5bd1752662ede2993ff557e9: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 9203a1600de814d3afb819f841569332c7e3b58c4d0e0ea56c377729f25dca49- root_
hash 03dd6fb33b4bd65222257eec0069956926795f14f7354795bcb42af5fe51ba08
The earliest published head that covers this entry
- tree_
size - 1253
- signed at
- 1 Sept 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 3cad2e0ecd54264a32b17f29b929d62f47446173c606f2674397638082b88c60- signature
SHbETlpvRB27T/YGfMM7HotNXTLex8tuCpVRhveEwor5ov11zp/0/nH9vNjfR6pUQvGFOvKwCymEB9fXzs55Dg==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12