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 - 1165
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 0485b0c1-a674-414e-9778-a898c974bd9d- logged_
at 2026-08-31T05:32:18.835934+00:00- previous_
hash fa747055e936a2f4cacacdd5d53881652d933c5f4dd0adcb5b2162a0bf569c70- payload_
hash 7da2aebe4c79269222ce8aeb39673d461b8f9421791c5f70626c1d321400a353- entry_
hash 341a3dcf19b72bcd92bfb07ff76bf31d1e1559d1290a3bb7e02e1e5d4f588935
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.825242Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "0485b0c1-a674-414e-9778-a898c974bd9d",
"series_commitment": "0ed398a4097d8ab4b9c3f40a6ec78e0dc2710d83ce7a7d50cb96ee6275c6ad08",
"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
eb1027f8e3f684aa51ed1c2572a5854a3b3a70d8fbbc49c2d9247516b8a5a5a5- 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 - 1165
- tree_
size - 2285
- leaf_
hash 318dfc9a2565adc8184dc81d6f231e8882b8064d4800a9b60cbf20bc26c5f646- audit_
path (12) 0: e7a0a895b2c164e7ef038d2c395c75ce2d80de49fdde30c6321c07db9b2f861c1: 476faf69bf2ca7e9f3cee9963d7ed3d8295c3ed719763c3784efe6df16374b592: 96790fea855a2323cf990096caccbf9e08a1e3edce40bbdad70a9c72edfabc3d3: 532daf0de78d1a7b94a4ba2c610f58df1992de18c63860e297e86a7b7efc3cea4: da87246dc6d20b70673209939d1141cefa7d5b2ed7a4ca0fbaa8b93a893bc6775: 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