delphi.consensus.snapshot
Appended 6 Sept 2026, 05:30 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 - 1472
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 1b1a20a9-2af9-4c58-972e-a6628e241b09- logged_
at 2026-09-06T05:30:21.331181+00:00- previous_
hash 54770fa2aae6bc87efb9119a5682ad5700fb53eacedc894f67ecd25f3c505387- payload_
hash b489f3285178a924d27be0dbc02e5e1004bfc72d01403217fa021bd0dbca489e- entry_
hash 59e84505cfb1e7ca1c5d483259e0b43ddeca129f7c4e784ba530342cf49281c3
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-06T05:30:21.328058Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "1b1a20a9-2af9-4c58-972e-a6628e241b09",
"series_commitment": "b093f6040d7d0e3e8710e72ccb89893990e7a03be0fd4f85c6073948c94ec530",
"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
9269130c17181ec77f5ba8fff9421bb401d72be6a231f3cdd57a60847b00434e- 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 - 1472
- tree_
size - 2239
- leaf_
hash 3c99ccbb50da0a7024cb08770feee321504883a69a0ec9cf27a4ec856633dc48- audit_
path (12) 0: 6867a02e470e51f06684375e53c38dd06b9e8d402c890d2b86cae6e221fb246a1: e993291cd46e5631b542305480537be857c6227542289173dcbee527e8277b672: 1e777e9cbbbf9e3ea385e09e5aafe494cd1749b1925736cf69547027ff5789d53: a7c5cbeb04e50827003b059bdf59a4aa937e20372b015d22cc7b0263187deff74: c0a5ed0c56c19f12df6f28039ba42c4239cb6bb5489beb861f9b0de2a032879c5: 91804abf66bcb55033aaa7181b9ee3fb61db565440654bb166ade8248335340c6: 35aca0f2b9f8c478040e38216ad4f2e9efa65fae1c6fc41a8df2a826f260686c7: 59548e903d1441fb0d6e6d441d39382bb2fbf2f915e94e4c49c6bda187d8c1278: 73b80563a47162cfa99809097caf5d77512af3a28ebfbf76c6bcfd5f572cc1d29: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 9203a1600de814d3afb819f841569332c7e3b58c4d0e0ea56c377729f25dca49- root_
hash 03dd6fb33b4bd65222257eec0069956926795f14f7354795bcb42af5fe51ba08
The earliest published head that covers this entry
- tree_
size - 1493
- signed at
- 6 Sept 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 1fa4feff08bf18e521e5bb925c6c5fdbb5017b8c298b1beb9ba8937af38f607e- signature
aqpHHBZ3TglMYwcvhOlfahpQD8AtFI2Le5O0NnqlhVLEXF/fDrgc8TON7pwPSD6UixQPbRrEyUkW8rogVxpzCQ==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12