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 - 391
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 4e06eb7d-ce53-4631-86d8-403a4f841a49- logged_
at 2026-08-20T05:32:04.245798+00:00- previous_
hash 18787546285c4f3dba55a50652098ddcbe3c2128fff75999052493afca3538d5- payload_
hash 6f667481bc926ebc02f7a524cca0e12326499ab983c400f2802fc4641f8e4502- entry_
hash 7700ec993f50fe77e2d20661fb40103af00af28ad494f72d363dc50ed80dbdcc
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.238268Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "4e06eb7d-ce53-4631-86d8-403a4f841a49",
"series_commitment": "cbe3aad9beb5ae6cf2bbe3a48d8ecbb74c22bd24bf987bf220a1fa502f5afbd0",
"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
853488c46c9fe2e84421bfb118f43280e137b41844846211b96eb3bb02171af2- 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 - 391
- tree_
size - 2341
- leaf_
hash 45ee9b251010d85bfa1aadff4314cc0b18fec933c707301018e6bdea41ac876b- audit_
path (12) 0: 94bd9ac163ccf74ffdd9613849bc2ca39b0561411cec7be2934886e5305236e51: 5fde7ddb46b071fb70a0441b04171b2418ff04cb3b5b3fe94a52999473e0ebbd2: 5d665467e6f723ba4022828a70123a7ce0403f1ec7027525040357c08162d52c3: 71d154e919310a784992e100689a38871f4f41c15543c18e2469da021f77dde14: eca43f1d4677fff737250e9c6ae429acee2927318faee7dceb605ef30f661f7e5: 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