delphi.consensus.snapshot
Appended 23 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 - 683
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 05901165-61de-4a02-b759-02a9bf89ef70- logged_
at 2026-08-23T05:32:12.301724+00:00- previous_
hash 617a9399786f05dccbfb21357e73666888bda440a581c391fa52d8cb06d1f519- payload_
hash 2d1011620cb52b92eb547788cf4e35cfa697cf57ddeaebeca4ccacadc6445282- entry_
hash 716b16e9d04c43038bb146a736e59bd32c32b1479862e7746001567934b1f137
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-23T05:32:12.298766Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "05901165-61de-4a02-b759-02a9bf89ef70",
"series_commitment": "d08bde9a2bf919cb857e7f8f3bced2b2b451856f311cf2f149853f10bb450630",
"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
fa7c30690a927c75af35a2353d14a939ad8382ed4d365a37e7a0d9e6de4bc7bf- 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 - 683
- tree_
size - 2239
- leaf_
hash 4c0524864d1b7012ecbd6d6684189436ccded7e92f8dff34cdfc5aca7d1bb6f9- audit_
path (12) 0: ddeedda3941239b801db9912d37f98cd2bd89f215dfdf127e350c9c8e7ac12d01: 8997192fd7acb9020e1d4d67941c62b7ed110ee9fb6353ba5bffdf08eb1b3f8e2: 08ff960d5f84653e0a8c470723d467049faf32503e676a545edbe1965c4a88803: 7f3fc4a4d415536f55e50fbcd30584e8cbf169940b514906f604929f03ffacd94: a4c2fb649f5e915bc7ba2775b0cf988a6756970f33d6fce0747ffa8da7c395d95: 2227b1e6f87ee00d0ed030cca3e6653e792b9214c57a30195159fc1d258a7ddd6: 4810b5c1f9344b5d296e3bee7c81348e090f31adadde16570bc3b8d3abb768f17: 9580dc2d498dc3b39d2b35bfb7dd13e8996199674c5dfe44e04c8ccc43e9c0d88: 1ed805746441fabcaa9e107f622f886b1692796b8a67f3eaf5f2122c01401d239: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: 9203a1600de814d3afb819f841569332c7e3b58c4d0e0ea56c377729f25dca49- root_
hash 03dd6fb33b4bd65222257eec0069956926795f14f7354795bcb42af5fe51ba08
The earliest published head that covers this entry
- tree_
size - 705
- signed at
- 23 Aug 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 4d18c6a52af8ef6fba64e938f1242a8d60e604e552526aae52071150eb66a202- signature
wJRAh51aHCkTsKK17vyEid6Up+l2HLMGcAnud6I240myQdRHSxzbQAOt1feLhwpcHeZI65DT1HKYBJyGn+cGCA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12