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 - 1241
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3b1bf8d0-fa87-4392-b4cf-333e6cba3622- logged_
at 2026-09-01T05:31:21.184439+00:00- previous_
hash 4697e0df41f8b51f671fb505e42a4606ea298bb86e29dc58b3a254e6293314fc- payload_
hash c4f19cb56979545a3a7d3ae36c840de06a224fb8191244a920e7336980d73a72- entry_
hash a0d2bf763c4f43b31502e25fe1c0ccdb1717cf0f890182f7028cc052896f14ad
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.181005Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3b1bf8d0-fa87-4392-b4cf-333e6cba3622",
"series_commitment": "376f9bbb6e036bfe3d8a6ba6f6ad9a48f81de70fb8a920ca4c4ffd8837f263e1",
"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
b7573f84255d2b5224c53035b4065ecd2268c0472a36a88610a3d59ba35c959b- 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 - 1241
- tree_
size - 2479
- leaf_
hash c05715d65b5c5a1d53abe07b8bec0ae6259f98da0281951959c6db396a4a12e4- audit_
path (12) 0: 5c4c5d8c7d2f50b82107e087a98474d38ea1de89db592b4bf2d660cc672b03041: 0b29f04664a42bd54638db7faf8fba5a7d2dc0c7fd98836614f7109dcea708e52: 54e29c8170419caf016eb445025d8530d54b7e9976edaaf3f2601fb2bf4ca9143: cd3e0b81fc320d2cd06b9ab22f1dc4f56fc7e1d64669944db481c89aaca3037e4: 62a65c450111e389fa7495295493df8efd4857c0cadf8512841f78ff850ff71c5: 6457d041f692165a2d435e4fc16b6e2b8617893057f2ad51fdffb8c9363d31346: 669172607016fd0304cbb59132e0f82cb4f48e391f29d72a97f4ceee2d3ffff47: ccb0e9f17cd47f20723bd8ade751778a3fd4e9649264dffce135260eaca872fa8: 6ce18fb0b650e54a2c9454c3e9abde48f8386826f5bd1752662ede2993ff557e9: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 8d949d6aef53b2e3322ef5e232755263eaea63b886b405d936c87ac0c842b6a1- root_
hash 2135d33fc3b42de9408df8505e145fcd175142e943af391ea41c56bc99a1e5e2
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