delphi.consensus.snapshot
Appended 2 Sept 2026, 05:32 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 - 1285
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 24c5a768-70af-4997-afe5-05e9edc2e4a7- logged_
at 2026-09-02T05:32:20.818662+00:00- previous_
hash 11754ad612d2cee24b2ef4a6ddb496403ce4d4a59a25c96193a6c59cf7482192- payload_
hash 35dc6170d0fe05dac22a07f6ef8adb0172260e8848cbc9ecbd2b16a26951757d- entry_
hash 0b7956532eca0f35767e2e83a60bb7ad5da0bbe54b4cf9ae90373027a5eefce4
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-02T05:32:20.815287Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "24c5a768-70af-4997-afe5-05e9edc2e4a7",
"series_commitment": "ca67ade36bd71b079b844a835bb408d79814087b5b77d3c4012251c5557f5cc2",
"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
5542c5615481e325a51cfa8d60abc83a8861d1066ed06ef9f9ab68c801609696- 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 - 1285
- tree_
size - 2265
- leaf_
hash ec67ff171bba6a7778a258ca21217bf519429ffe1b8d94f28ea1571bc084b540- audit_
path (12) 0: 8d08966920f31faf5a8f1a908470873f2e06677edcc8f272eaef7465e261459e1: 3b999185f6212217b91a8181982b8b72fee1dca99b3f6e95b8e485d1ad25a3722: 74d1697a1151830f7cb11fa450af3a5573051f7af85cbe0855152ec93072c2643: ae4b9b092482ed9232c486acb17a965d99b37a1615b436d45be7c16ff749dc9a4: 3bab3dfacdb4663eededa2dd912fa671e084bbce8b9478f98ff785f76bc67f205: 338aa13e9ab3bf9fc959251d8ac5778963ee124660725c2266d53394765b5c306: 1856e988c0ca2de1232e3499545b496b7d991e639165b9289a3c3dc3f273d8d47: 00aa16d00eabe2b61089fea4a6c3044cf3b1ced9f2af168276f93e239a98dae48: 73b80563a47162cfa99809097caf5d77512af3a28ebfbf76c6bcfd5f572cc1d29: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 15428b80842f9a0801cf7667918b216c9ce4186d9825e806ba86972b039c03f9- root_
hash 0feab2262fa1e39174e25fc17ea9383a6fe15fa5d22c96afd722849e59baa3f5
The earliest published head that covers this entry
- tree_
size - 1301
- signed at
- 2 Sept 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 7412c3bb0fe0de978d577bfb7d7e6c78c4415aac29193a116b150bd1dc28f398- signature
NpyT4m8rheEfWbFdEQNnccQG0Zzl3KXO1wHnZx7zD3lNnn81UHz/zavu3VUhzj72XmrSmaJLQKo1iyyww27pAw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12