delphi.consensus.snapshot
Appended 29 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 - 2231
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 4bfc7aa0-f12f-479c-ba06-d8e4cebfe625- logged_
at 2026-09-29T05:31:20.831090+00:00- previous_
hash b7b6298731f27f410ce8abb402396808fd59e6f3c4e1ebdfee40cb3a0492b440- payload_
hash b454b0662d24cf766bae4a9d4520e40d5854ddda7563a23270855712a9409906- entry_
hash f194ba7f0ca6a0416947c65a1a89091fe509ce5935ee242fc7c88ec66939285e
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-29T05:31:20.827261Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "4bfc7aa0-f12f-479c-ba06-d8e4cebfe625",
"series_commitment": "2a819bdee04e598d87a470f0067bb91967889d07c0ba7171291e29de2d1fb113",
"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
a5fce35590037277ac716a66562d28b3aa154ef247274684611481ccf5cfd1aa- 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 - 2231
- tree_
size - 2503
- leaf_
hash b9bb53b0ac6977c3404388d8eb6f93b02e1524332574eb9d79097836e4e85779- audit_
path (10) 0: e5025c8516080e40f4afcb6186acb3c82be0ea1e04d34526578b911f4b8751821: e10f4c2f5ec334ec8d5742fe2e9509c908cd6e505891efb638d325cadbfa30c22: fdd5bd9205a2a4540976078b110f171fe552b84c4a6c8742c90db46426c88d9d3: 8ecfa0211918b2e9d96b6da731a3372dc96703f1648e49caae3b3b8476b6eac34: d2c68d760af74d87740ca89ff1ff67d32bd189e548ad56ef83ea1334e37149175: ff576d5d5ebff608e9a429939d33e803b4f824aa935c65d508ae2b3f2eec66696: f30320e32b01d85ee25d3699765f61034c40add7177cc53ee3e39fdfed97b4367: 126596474757e47b31a2f4c9d89412108fada5bcdc7a19a9a1de3d4012be0b578: 47a3489f8ed18aca1e6e6b6ae98a5d47ac64bb31c7314e873c7cbac9cda2eebe9: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash c97f540ea605dcd0a8a4165044c60093cb885a8303800b87d215a424a4d5258d
The earliest published head that covers this entry
- tree_
size - 2239
- signed at
- 29 Sept 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 03dd6fb33b4bd65222257eec0069956926795f14f7354795bcb42af5fe51ba08- signature
u8ChL0jIyB0SQwYB26vHeURVL3Ia2DcWQObp46M30jJWJb4SKWQ36EVhUNp29FUDMGkSZ7aAlkHhiTbNS6OGAA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10