delphi.consensus.snapshot
Appended 28 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 - 1001
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3b1bf8d0-fa87-4392-b4cf-333e6cba3622- logged_
at 2026-08-28T05:30:32.431981+00:00- previous_
hash cfe5b1318a7aa32b06d751c7709888c79988fe15974673ecb8958d132463c693- payload_
hash 2061fdb0e10e7112ee6d316ae13f95bad4f79e6853331928562426dd34d5e233- entry_
hash b91f3c95d36fa8a181890bb53bcf9814aacb34c02a80c48652c08174f6fd6363
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-28T05:30:32.429915Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3b1bf8d0-fa87-4392-b4cf-333e6cba3622",
"series_commitment": "b8727ca131d5a3ec8b4f6c48709f2763b680f1fae33282b794b29ecbdd02a3b7",
"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
6271b8fbacc64f8e046fe7af6985fa3fae58921854eeb230267c8e8d87e23602- 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 - 1001
- tree_
size - 2285
- leaf_
hash 9c2e7169ecfc9b43dd2c4bd3c1b1b519a02e1841dbb7c32fccfd3af3ea0bfb16- audit_
path (12) 0: 27fe2e31367fd5c10fe17d79a2c636c5a18850b50de7df61d6b3b783855f6aee1: d5ea42637bd8f4f950e95d33e5a179655c091985ff8d46f59fdd13f0e9cfe4fe2: 1edca8405679b12b353901b2874554f8f1764f583fa5c998d1bdffd0366de4ca3: e3fa450fe82476f7d5ee646913bcd363bf171e872c5b105509df91f23c7740654: 5cd71b38caf3c9d8f6854003e0049a5da4accff2c53ef41677f6123349a271575: 8c941da097b0f3f2bb90eb33ac96ee9bf2166f056afc3c3c862d79678bf5d9276: 881346e175348d0a346f32907950a49acd79893f71d89e46421e07e28bdd00627: 9f20cfd56c132d1d00fe76cb2e482a3a9b4fbe96bc0d292d29ba8016ce161e9d8: 184a24c3b623669a5fc418f1a01a448ab12c5b650e771370beaf16f761dd2e6c9: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: a95d574e00e9fefbc454b084e8cb19edc83831071366b2d8dc1af2f7114b646f- root_
hash 17330c6327e6363b8237bd4a68d5ee420a6d0f745c8d8bab0a90305d6bccba50
The earliest published head that covers this entry
- tree_
size - 1013
- signed at
- 28 Aug 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 31cb04f309e462f9e86fd5e2a26aeee8e0d75dfba1d3621c2717df431964a503- signature
p3eUja3ft5l0E0pT2RR92l4L5xcWlnzXx8qcK4NoGop0OIzErqTrbzeXab/1p1jrJ2TAQFjcSRJz+xTVBU6JDA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12