delphi.consensus.snapshot
Appended 9 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 - 1614
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id cd22f6a9-1eb7-4927-a2e9-6736a77b75cc- logged_
at 2026-09-09T05:31:39.971747+00:00- previous_
hash f4c245e5c1da8fc4223dbe9a39207fdf787839d08754f648277d52ee3194efda- payload_
hash 03c23a847bc9dc1a908a523cc84473f3fb3e73a29e2bc88f0dbc15eae55d6874- entry_
hash 0af25ed19225c9e307d1c3161698267f83effdd3f24696faf65f1333ad9768bf
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-09T05:31:39.968649Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "cd22f6a9-1eb7-4927-a2e9-6736a77b75cc",
"series_commitment": "dd2a1173eec737951fc1ce2dba3c67334ce1db5dd0d32cb5de06bc3bd15ad31a",
"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
e850708b7842c8dc4de7ab0d756a05c4cab036bd4e47b24a71f2e151163cbf2f- 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 - 1614
- tree_
size - 2503
- leaf_
hash 14940ec8038c8ba942dab97d800a6f82baa0e251bed57628665900ce8164044b- audit_
path (12) 0: 301e789bc54c19b837269186c33bc3b2d4293b6dc646dd20430458b6c06ce8241: cd0e50c086c43cfb911c4997a6368300e9aa2ada275885c68d0833b5ed7fc7652: 49dac28303ae47c88ff7965f377273ff8ab33094e6e00963c39203390466036d3: d356bd65eb4bf39b04127b9c55e87889c1a333e64bf13bd91bb34f7f2de58d234: ce8813d73788a5a7ccef44404a8ca9577f9ff9897e64be3657e55edeb54438365: b1b6fae7089c27926a3b967b88f7de369c00e69d47160c303e67fd8ad3c0702c6: 00d36260786b8ce290bee853db49e73fdd5d2800eb992fa1e6e2b98e2e9d62487: f4a858c5afd6d2bbfe79825cc00005d2e5bc4cb6a3723b70509ff06cb4f713008: 49fbc719d10777c21e02e255a1174dbc47e89c67c7b327c5f50e8ea1ffbb5bad9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: aa4b429c2497df4f846fe6b3e60223989226aaf0ba6013dc6f90c17afe986d9d- root_
hash c97f540ea605dcd0a8a4165044c60093cb885a8303800b87d215a424a4d5258d
The earliest published head that covers this entry
- tree_
size - 1627
- signed at
- 9 Sept 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash ece15eb8383aee9bbf3f3bec9ccc72d87819c3947b61ecb8093ec13082289977- signature
9dr5EA8ZzKRK0L5i3/Zn8Rt3+PevClFJSGpb1IzYaNtVr+QKTJT2R+Qd9oJ77HQMV4y5WBTzci9qRcxNN4MqAg==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12