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 - 1237
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 24c5a768-70af-4997-afe5-05e9edc2e4a7- logged_
at 2026-09-01T05:31:21.157771+00:00- previous_
hash 0395169a336f6192a8d40680a49b10686cd3dd7b3156049a56eee60347cbed23- payload_
hash 9b5e2af760f97a959274c8702a7408a81ce291c9697d460d5b72cedb3497a2b1- entry_
hash 2e5f16ef5823b4b16c0c99800e7c8a2e4267553a31ac67fe69f975b0d1b8af27
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.154922Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "24c5a768-70af-4997-afe5-05e9edc2e4a7",
"series_commitment": "fc51261582085dca0ca85de59601d3da28a556a9539b0d817a66c4e755803e04",
"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
12a4b04e209b56e7baa96b3963a919e11225118660306e4b0f48a2ba7a55a721- 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 - 1237
- tree_
size - 2239
- leaf_
hash 08695cb5e2f8dd95ca1476330138f6a63b4df4f021b1d26a2598cbafc18996aa- audit_
path (12) 0: d821cb86b242b2615691a04d09269efe0c1d2329325363b98f5368258b3185dd1: 2d2ca6f979ed0e9b53765ee5d7bbd136a36441de3ac1d84cf01bbfd7ba9c08ad2: b7f48a9aac223bfe560ff40c415289da983b359fb2ad38084de1e0a6847949ad3: e417a4f135abd0a3547583e0869b74a30b92dd427abce02be6313ee43d05c9e34: 62a65c450111e389fa7495295493df8efd4857c0cadf8512841f78ff850ff71c5: 6457d041f692165a2d435e4fc16b6e2b8617893057f2ad51fdffb8c9363d31346: 669172607016fd0304cbb59132e0f82cb4f48e391f29d72a97f4ceee2d3ffff47: ccb0e9f17cd47f20723bd8ade751778a3fd4e9649264dffce135260eaca872fa8: 6ce18fb0b650e54a2c9454c3e9abde48f8386826f5bd1752662ede2993ff557e9: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 9203a1600de814d3afb819f841569332c7e3b58c4d0e0ea56c377729f25dca49- root_
hash 03dd6fb33b4bd65222257eec0069956926795f14f7354795bcb42af5fe51ba08
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