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 - 1006
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id a8c36f16-c0df-49f5-92d5-29bb1d0e58a9- logged_
at 2026-08-28T05:30:32.461794+00:00- previous_
hash 901c4a21502ad08e5fb2cbbc041228863ebdd267f449bfa7a435ca71bb185169- payload_
hash fbdecedc7519de8e1954fe2402bf7a09f200bb2e1309ca5fce1300e59a2628c7- entry_
hash 7cb4f7e01c852202c0143db34239604330ee734ed5f28f97e6a2db954257a577
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.459492Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "a8c36f16-c0df-49f5-92d5-29bb1d0e58a9",
"series_commitment": "86ea5dc72162178df65e6a81b0b9cb9894796eefec3f121e944ae22f29322bf4",
"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
d5c30471c402de82f77ce35edff0cbec1c1aed9e371dfb2c0933bbedfd8fa7a6- 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 - 1006
- tree_
size - 2503
- leaf_
hash a21e29760041ba70b9f22ed98164f09323bd03f7bffab20d3735c1e9ed47e583- audit_
path (12) 0: aff3eacb6c76d77ab9c529d8f9ee72347896be8f11a579f440e5ebc7deaca1a91: a68d3df833f17961a4a89f2390e6f768d28e11bb81c499d314b94bffb7fba9ce2: 5d1ac7b353e0968c79643862674e366f2240e7a90dfe5fe9f991af3c3a8ecbee3: e3fa450fe82476f7d5ee646913bcd363bf171e872c5b105509df91f23c7740654: 5cd71b38caf3c9d8f6854003e0049a5da4accff2c53ef41677f6123349a271575: 8c941da097b0f3f2bb90eb33ac96ee9bf2166f056afc3c3c862d79678bf5d9276: 881346e175348d0a346f32907950a49acd79893f71d89e46421e07e28bdd00627: 9f20cfd56c132d1d00fe76cb2e482a3a9b4fbe96bc0d292d29ba8016ce161e9d8: 184a24c3b623669a5fc418f1a01a448ab12c5b650e771370beaf16f761dd2e6c9: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: aa4b429c2497df4f846fe6b3e60223989226aaf0ba6013dc6f90c17afe986d9d- root_
hash c97f540ea605dcd0a8a4165044c60093cb885a8303800b87d215a424a4d5258d
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