delphi.consensus.snapshot
Appended 31 Aug 2026, 05:32 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 - 1169
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 54324c2e-b8fd-4bfd-afc4-1b6e799c095d- logged_
at 2026-08-31T05:32:18.869208+00:00- previous_
hash ebd6f5b683567c1ac94f16559412470b940685086940f5eab0b033aea125898a- payload_
hash 844f084f0b2644ad1285e2005e8d2a2c82ca4c2db9000a195b416b9dae012b0a- entry_
hash 5042d1ebec11cb0a5d430c933feaa5e483bb917c56cd555fa76210f557a2e615
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-31T05:32:18.866063Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "54324c2e-b8fd-4bfd-afc4-1b6e799c095d",
"series_commitment": "a503e749502fc13a8fa7e194c4cda50c2e22ba7a032be0f6190a23b26d4d5985",
"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
74be3b3900ea4c8844128735e46506df5172c9e47fcbbf45ad85fd1bb8d96ca7- 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 - 1169
- tree_
size - 2285
- leaf_
hash 2bd25d9f4b3b3def1478f863cb5bc864b1eb7d04dd3384a23dca7227863c016a- audit_
path (12) 0: bfb357665b43f965728c7e71fc061bce2c7b85e4d730d5dedf1147641669b9a41: cce4e822004223593a403c346adc524f07e3733772595457fe3f352ccca866e02: dac12f99484dabd51573f86ceafe30f8f34d19263a8de3cbf4f16fa8a6d6adaf3: c24b8ebe729efb0844caf33ea93bce0da177a1922130e5e68980e96d67edc3fe4: 05e1ee3fdb63fd0cbe9859ca8f3232f6bd4133b7f87556de328354b396ec52e35: aaf78ed005cc51b57fcd96f4935a1f3c7fdd88f0303aa876df637cf03ce662466: 6af623eac90aa3987584d839f2701ff98677b56e888f60118d80a93d701c74b57: ccb0e9f17cd47f20723bd8ade751778a3fd4e9649264dffce135260eaca872fa8: 6ce18fb0b650e54a2c9454c3e9abde48f8386826f5bd1752662ede2993ff557e9: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: a95d574e00e9fefbc454b084e8cb19edc83831071366b2d8dc1af2f7114b646f- root_
hash 17330c6327e6363b8237bd4a68d5ee420a6d0f745c8d8bab0a90305d6bccba50
The earliest published head that covers this entry
- tree_
size - 1193
- signed at
- 31 Aug 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 15e3eb7357c2f6396dd33e1f606888695ff95a2f9b08f8019ac153af57c87266- signature
oYDFeMwvTGSzL/7VBsEVI+Y0GdW8Zywth+2mJP8ClwrkwRB8E6GNcFw3Uymh+sQFClvxu4FaueeuBpxLmZwNBg==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12