delphi.consensus.snapshot
Appended 16 Aug 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 - 221
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3b91df80-00fc-4a4b-b86e-3310edcb9332- logged_
at 2026-08-16T05:31:41.558477+00:00- previous_
hash 79c80281bb6e7d074509d3ed3905677710f01ed87d625a84609775a69a58c8c2- payload_
hash 09f94f1af9a76643c840213919b89ac0648edf0b3716437ad523017450eddc54- entry_
hash 2b214bb123a27fc9631e7aaa254139344fcc9ba77a7424d2d9005b484868053c
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-16T05:31:41.555528Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3b91df80-00fc-4a4b-b86e-3310edcb9332",
"series_commitment": "0c0fe16198f71659c3836e1fb4edda8a9e324d5f3fea30f620a74452271a0621",
"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
838a96d04fe7e2b727837301a12a5068c96d9e6ee31ea99698ba7ec22122a9f1- 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 - 221
- tree_
size - 2491
- leaf_
hash c05250fb1bc086680befa4a61a1166bb77b6b0264c1d1c90c87825e9d1c646e2- audit_
path (12) 0: 61d3b79310dc195a1b0acca85b1484ad5438dad6047e0b5cdbbeb454792e94771: 2e66a342a0663c7597c4a1039d4ccb9b6941fed20aa6911fa94f8d49b29e04ea2: ab23b57509d810210849412637afa2867b4b07611bd668dd8ac112d66d707e5e3: 86b9011e04f73c3ab305fab93b8b9df80f8bf0c75b915e9790d5df61e59519b64: 0c70dd2fede4f5de03a19de51d481a3000dd2955ad77d27064e219b6f84d1bfb5: fc441ad496235ad68d0ad62d88ed053be8000557ddba9a742a39c6c06af3a15f6: d84113033297e6a1a6778c4a1e0094059ebbb1414eced4e82d59b1e29bed26c17: 8e3ada3865734ef89cf9ebd82b633327831f303fabc83306d43c8e1c4685702d8: 6e5b02022079dc614c5f74ca1c784cf9700d832e05c2eec11f0ad0a37376b46d9: 2fb679aab258481705c982e553094522ea7bb93361711a8387ebf359e8c3e43110: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: 083d0806ed3c3d656f2d8c4762013d3fb4c0ed984cb03e95e8ae46936f2431df- root_
hash a9a1dac66ff7c8ec3d4b27b434ff70fbde5df3ef3dcd4b4fe4b41bb80f78a7c7
The earliest published head that covers this entry
- tree_
size - 374
- signed at
- 19 Aug 2026, 20:25 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash ecf4adc708ae542a0339e03fd4cc181cf49d0329768627c5345c915a58bd813a- signature
3yL+JZfMhiQ6rm5rCTTg7iT+or04nCGVcQ08ILMw/d7eqvR4Jid7cEg2rQU5fCX7llStjVkTC9jVZjfGQvtMAg==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12