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 - 599
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id d8d7d8bd-61ec-4918-b395-799de97e359f- logged_
at 2026-08-22T05:30:43.241890+00:00- previous_
hash c54d902a456916d0c822a154990f0ad61576650e1cc6f7c034a58b047872ea1d- payload_
hash 81c1e64d733b61de4865d8ef3a6634dde8db583afdf769996e720739323cddb9- entry_
hash 1ccf684cf2f84179749a1ad677910a036b74f3aefd4b92c4b536f1bfeadbe601
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.239232Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "d8d7d8bd-61ec-4918-b395-799de97e359f",
"series_commitment": "bb1a2e9315e3b7c535bc1820faf7dc7f24adfcf324b392d4b6f4fe5a37002fbe",
"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
74a5890132b9924f753fca847d7af2804c99291764afd5299e8089d818d2525d- 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 - 599
- tree_
size - 2265
- leaf_
hash 5ec9431fbe4594851670cb1b0c02bb537e4161d52a8183e911739ddcf08735e3- audit_
path (12) 0: 7a6122fc770975a8aa7a940bfdecc18724a881565adfcafa5b948e6c5467b74b1: 3a0a9014d894c44f2333a188b083fc0312f90b47953f3f741b526433b270dcd52: a617a53a8fab419a223099a72ca454e6d8f04b6a2865d0d777606f26c7104b973: 93d359af5bb81cff68bda8bd94338095b18ce2bce163cd4895c2b7b45784f3ea4: 9f1dab1bdad6a3dafd37f58d152b6385fa55aff434f786595e4a900c74d597f95: 89673626539af9d3d599d3b42d3ef89916644decc1454127ebb129fd50cc8e466: 66d783f1a4106ac8ea73f0464db5328d95910b9613d356ca7a4d7238d180ef957: ca7fb7b440d51df69e12966994a041553b2c0acd85e1779b8e2fe8f79a1a4ab98: 1ed805746441fabcaa9e107f622f886b1692796b8a67f3eaf5f2122c01401d239: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: 15428b80842f9a0801cf7667918b216c9ce4186d9825e806ba86972b039c03f9- root_
hash 0feab2262fa1e39174e25fc17ea9383a6fe15fa5d22c96afd722849e59baa3f5
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