delphi.consensus.snapshot
Appended 20 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 - 408
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 04bc3a9c-76fe-4aad-90b1-e3640e548e9c- logged_
at 2026-08-20T05:32:04.434053+00:00- previous_
hash 78250f65ce86709cc9dd23cca11e4b3503ff31f6c414c51ad0ef074a439064ff- payload_
hash 74ccdc05b38e29592dc9d43572ccb3d7cee2bab7ba160bd6eddb4ed3b1238715- entry_
hash 25e571b51453c85a3c3f315b6dffab590e4323a06c1424bed8580354771cb904
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-20T05:32:04.431179Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "04bc3a9c-76fe-4aad-90b1-e3640e548e9c",
"series_commitment": "39ed7dda4a5f1d063d7dfff27fddb25fcc98fb03f67f3b22d1b29b82de019c65",
"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
433d5fc47e0150b55e4302fe90ec1795e38d10e588615d2bc344acde901be78b- 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 - 408
- tree_
size - 2341
- leaf_
hash 0c6574ea816677542cf66f6f0e3a877d8d4bcf461520fcdee3f121569e42aafd- audit_
path (12) 0: 121826f9619b7113275584f65a1b8aa42f3509b8f0376df5bda6100784dfe22b1: 5d9a8cfa159770a904e3793bc05e65969745619431571df8dd9d8a58a6f73af32: dbcdac3c41b7cda3fa042afc41bf5abc8b9a84bf653d0c1d0d09a4af709ffdf73: d7f6d830cbbcb028c376e415b44fec6a32808417729b134219b9f2760e2348414: e9ce3f76891edf80f477b94303c58cda836a2fee83115980324002fb3086b02c5: ca5653a876128a523cf2cfbb92753bd3b2efcd68fb0a333d8831f9dbc31f40516: 6e74d8c74f1def32a7db82800d33c40daa3b7b59ecb7185679e1c92bd30802bd7: 3f258839204d1369f50a8ff655e9cddf1578324dbefa9cee96d9636587ca8cca8: 895db6b8306be0a0cab88cc38987289ed45422a6223f6a873d831c26678719179: 2fb679aab258481705c982e553094522ea7bb93361711a8387ebf359e8c3e43110: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: bd18df2de60e205be411a53ea96887ec76f5a16c15250bf48e3f90dc788abbaf- root_
hash 9f32e37b52a81f4fc0f11a1b956464ef6acde09c58b0ce26dc44277199cb7df0
The earliest published head that covers this entry
- tree_
size - 422
- signed at
- 20 Aug 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 9c6be349cd97b775052fcc773f0abdf8cd1a1257f06093ed26c9c9952dfb94df- signature
ow3fRwdLR0tq0deU8FpO8JPoa6pZKmumgC9RgKJmNLf3oZLYwaUh6p4uQg63+K0+GQYzDZyo7+D094TL1sLyDQ==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12