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 - 1997
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 4bfc7aa0-f12f-479c-ba06-d8e4cebfe625- logged_
at 2026-09-20T05:31:21.052344+00:00- previous_
hash a8bffa9ae722022de579038c0e599c16e98c93fd0036b2c29b26f1d153484319- payload_
hash 61d1a402edfed464bfb71bc7ee683c3d8e4a6694ddc0c89c2a1f5740d24e7866- entry_
hash 6457ae65724c4c923007b2f72ff56425ec3f977f091ade76cbca5b10aaee6642
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:21.048652Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "4bfc7aa0-f12f-479c-ba06-d8e4cebfe625",
"series_commitment": "42e6ddaa330ea1e951e86f0b3003676100f193dff5c5ffc6ed358baae2d841ef",
"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
83c9a883010302cd4cc76fe1baf26af18839d770f4cf61a18518b80d1a345f60- 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 - 1997
- tree_
size - 2479
- leaf_
hash 7cc44f44181fee74197ba47ecfff2854694af0ccfc20dcab1c8ad1d82ac66c01- audit_
path (12) 0: 65c3fe8856b690f0bd610be71c6678c7953dceedbcdccd14b7ae2947b25328281: f01dc23f727341191a9f9cbe371f759b950e3a9423ba2b30ab4e03044d113b452: 6bae6118eeaf2a381d6cebf7bd10cec0ee07dc6a35db2d587e8691d6ddcaf12d3: 98e98cb2e99e90a10792886412c376d983058e52333234e7e071243c68afeb474: 0660e870df08b3e5f265fe28da6fd51268d00673b6dbcff1999891e134500c085: a50e0e977ad9842f45f35f6e8d03b29bd4c453b61b361ba211d57763c2a168e96: c321285e45ea8a57cf869ad4aefceaa5840e364ae5f182e7b0c7b58aab9054be7: 8018b7deda34c522f2ac360ffdd9cc85624549e7457ea594e86a7f04e9a264aa8: 5ab1df6751f0dac25a6ce29d97587d6e08dcdd2d94987223ead725483527e08e9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 8d949d6aef53b2e3322ef5e232755263eaea63b886b405d936c87ac0c842b6a1- root_
hash 2135d33fc3b42de9408df8505e145fcd175142e943af391ea41c56bc99a1e5e2
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