delphi.consensus.snapshot
Appended 22 Aug 2026, 05:30 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 - 606
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 08ea8d0c-fe07-4a30-a823-6e71109f1fb5- logged_
at 2026-08-22T05:30:43.310022+00:00- previous_
hash d57e2db43b33390247ac1bdf1a90180897d6ddf73da3b7ad47d05c6d04060c3d- payload_
hash 5c0e43e36232b4e1114bd0de8193d1d70060c504f08991aa9b4723e5c89bc306- entry_
hash ae2c0cec2fc85088c31f5122601a824645ff435a30720d398395258098b995b6
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-22T05:30:43.305646Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "08ea8d0c-fe07-4a30-a823-6e71109f1fb5",
"series_commitment": "252e61008df70e7de01bb9bf0c6e5f310099a932714af57442d467880b9608bd",
"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
d964b28e1ef0bd6685697a9b10bb2b58be62509866aff31791dd6b9bbe0c37a0- 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 - 606
- tree_
size - 2239
- leaf_
hash d9ab5f3d79be4fa41c841ae17e108b2ddb3750409d1119803be3d46cba89e3ff- audit_
path (12) 0: 9b321706183227751bd290024171b5d6b61b43f16ed25a752590a2bd4a4de5a31: 152477c9f0696a84fec47306000ed09934501813b32a9f3c19798086f0fecad52: 7642da4b53d3645b25bc15035f2dc3227a482e6906f2f5430b6c744d0326d0063: 5220005c0a86cbc8fe6dde379254e3ada945f9e965340b95839870034860a88c4: 9f1dab1bdad6a3dafd37f58d152b6385fa55aff434f786595e4a900c74d597f95: 89673626539af9d3d599d3b42d3ef89916644decc1454127ebb129fd50cc8e466: 66d783f1a4106ac8ea73f0464db5328d95910b9613d356ca7a4d7238d180ef957: ca7fb7b440d51df69e12966994a041553b2c0acd85e1779b8e2fe8f79a1a4ab98: 1ed805746441fabcaa9e107f622f886b1692796b8a67f3eaf5f2122c01401d239: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: 9203a1600de814d3afb819f841569332c7e3b58c4d0e0ea56c377729f25dca49- root_
hash 03dd6fb33b4bd65222257eec0069956926795f14f7354795bcb42af5fe51ba08
The earliest published head that covers this entry
- tree_
size - 632
- signed at
- 22 Aug 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash ee7d3fc82f5aaff8097c262dfec5f324866dcd66ff2f57c5f03959246ce30e44- signature
5xMqhp5mkjyNaCZDqNNz8sCOKCPVWpN6XP3+g1675vS1ryFscLkuSpbpJpoeP1G64a52gFmsNs2Hi0lgRWDDDA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12