delphi.consensus.snapshot
Appended 15 Aug 2026, 16:04 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 - 73
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id ba007bf6-84af-41a3-bad7-f36ecf2ac953- logged_
at 2026-08-15T16:04:51.064746+00:00- previous_
hash 8bef5f3ac13c6d216354c7b598a904b1c4daf337c24c57ad8d36024bde017756- payload_
hash 438ef42949f245709b76931d752d47f501ed7183dc894ddd940d2b359dce994e- entry_
hash 568f955d1f5abbd2857cde1cbcc7f5b4dea077532b1ec9c87f7916c888c6d69b
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-15T16:04:51.056195Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "ba007bf6-84af-41a3-bad7-f36ecf2ac953",
"series_commitment": "b98e0bb827d77cc22bf8af987a83e79a8cee35c1aeb735a0fc80200a0379a02e",
"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
05af73c3cbfef65df99e56a4f7cecf8e82091ae46869ad2b0ace16d445c16678- 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 - 73
- tree_
size - 2265
- leaf_
hash 1e2baf9539476228daad9c9b72807a28552d877802929dd0fd1efac8ac371e6d- audit_
path (12) 0: 4c8ad8d95b2248af8346303bb4dbbb4312d7a7eabc5ab1758ed0aa50e57c5f641: baa21b3049c690af2d978af1cc4ee653d3d031398b29afe714c0534cbe62a9372: a7d95955a4c56b603d6f31d8346af3591c99e374bfd7bf1cdd43329853d2137a3: 816d24ee36243d05bc8fd07688e05d1386a27cce52a04f334daf1bcbf954b4d54: 90ca477c832ae34ed00dfa76c2b10e36cff69ccd72ce614d0c507e05920007b15: bfda397922356f7a423fafc090d2af03517b89157a8d6cc66d277e2cca96e8316: 9fe2edb4769e24911c893b0836891045cef78ef8ed4ae19ec89e6d92edfad5a37: 925d039cfaa2795efce751d71988395a9d8544d4910a71d82c761e6c8e51ba2e8: 6e5b02022079dc614c5f74ca1c784cf9700d832e05c2eec11f0ad0a37376b46d9: 2fb679aab258481705c982e553094522ea7bb93361711a8387ebf359e8c3e43110: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: 15428b80842f9a0801cf7667918b216c9ce4186d9825e806ba86972b039c03f9- root_
hash 0feab2262fa1e39174e25fc17ea9383a6fe15fa5d22c96afd722849e59baa3f5
The earliest published head that covers this entry
- tree_
size - 374
- signed at
- 19 Aug 2026, 20:25 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash ecf4adc708ae542a0339e03fd4cc181cf49d0329768627c5345c915a58bd813a- signature
3yL+JZfMhiQ6rm5rCTTg7iT+or04nCGVcQ08ILMw/d7eqvR4Jid7cEg2rQU5fCX7llStjVkTC9jVZjfGQvtMAg==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12