delphi.consensus.snapshot
Appended 20 Sept 2026, 05:31 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 - 1991
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 04bc3a9c-76fe-4aad-90b1-e3640e548e9c- logged_
at 2026-09-20T05:31:20.989255+00:00- previous_
hash 5b49e38133e0e4c684fcdd7615ba782b20fa09d0b8a919910fbfe6a98bc9ed9f- payload_
hash 8fa092bbc3e8bbc8950524ff74b8af15a69c1c01c799a1c29a33a31f429318d5- entry_
hash ac4712eb0e508bfffd9c5e03425433ef782470dd2be11302ecb9ab51a4a86164
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-20T05:31:20.970266Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "04bc3a9c-76fe-4aad-90b1-e3640e548e9c",
"series_commitment": "01ce43fbf7246c184b9c83d2b8f7f10d25b39fceaee96a8c4de243fa689f425a",
"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
ae939f63e37759b5c358506d0845f734616070d8ebdf958bf648a010640395af- 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 - 1991
- tree_
size - 2239
- leaf_
hash eb7c2e9889e31a6243743e9a81aa30f1c8b82c9c6ad01f03a78f49676d06e3a0- audit_
path (12) 0: 862c6732d88469ac5c5b1096568391a78294616101ca8788fc9619aabf87498f1: cb95428f044a89002ad4411da0f14faf4a4ba25d24d93ce05faf9111c83122ab2: 5b15424f0bf926b26e5f46cb7c43fde7b5045fc817bdf68922e137c3d06cb2933: af9ca2d4783e1a2a94ec7956c50f5e1020ff66207502281a336d8ba6082992284: 0660e870df08b3e5f265fe28da6fd51268d00673b6dbcff1999891e134500c085: a50e0e977ad9842f45f35f6e8d03b29bd4c453b61b361ba211d57763c2a168e96: c321285e45ea8a57cf869ad4aefceaa5840e364ae5f182e7b0c7b58aab9054be7: 8018b7deda34c522f2ac360ffdd9cc85624549e7457ea594e86a7f04e9a264aa8: 5ab1df6751f0dac25a6ce29d97587d6e08dcdd2d94987223ead725483527e08e9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 9203a1600de814d3afb819f841569332c7e3b58c4d0e0ea56c377729f25dca49- root_
hash 03dd6fb33b4bd65222257eec0069956926795f14f7354795bcb42af5fe51ba08
The earliest published head that covers this entry
- tree_
size - 2005
- signed at
- 20 Sept 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 60e3cd283b73840cd440288cca33b52ceafee6c202d421678a412f3c5ee05946- signature
cd67hFwY1ta97P30k//m20Gy5B+NCvWm0//2kBrcp9vTc1CKExyU43VM3CfB7s59bHxcLHAWq/omhe+LeHwvDQ==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12