delphi.consensus.snapshot
Appended 7 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 - 1526
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id f69e4ff3-bcaa-42f5-a8f1-8044a9975b0f- logged_
at 2026-09-07T05:32:20.534595+00:00- previous_
hash 66cc68591f190c942417ff6e0e7792e34173d050e190d10ebdbb3f98a582126c- payload_
hash 4bb8f1e7c1056c2b98b747fce850dee3097876c62b27101fbda68aed16d52c42- entry_
hash 1a065c5f86a796c9885730063e00b2e0cf5f7b1fd60ccc025d9aead6a0c54d45
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-07T05:32:20.532206Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "f69e4ff3-bcaa-42f5-a8f1-8044a9975b0f",
"series_commitment": "20efb608ae229f7bf38137dc647483e24295c1cd17bf54e53cd45fed835b91f5",
"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
79d80653abca077ec076de284adf3b11077e7ecdfcd9fc25fbfd6e42587a9c53- 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 - 1526
- tree_
size - 2285
- leaf_
hash 37aaf270deda20c1add761ebd1509b1ec23f4982d0e921e31064e25702d4dbb6- audit_
path (12) 0: 37e0fc0c9b2f4ae180ae3c19b93e0c93c42059245f4d9690bba6c786e9c8f65f1: 2c0eb582c301d263cb6d5c85435e337d6c8455d1ee78f52e93173dd7236fcdc22: 85ce6878a73ba99a700d99e380bd6f3086ae8ae0097c95e0389a7f2dd63917cc3: 2d5f1c8f0e4cf98870b8991615229d0b85a8c2fa1952ab64005e8c93b7dd51904: 186fd3378c18fea8fb6da7f0fdb301f4b90c8983dfa5aa0bb5375f2b2699bda15: 116fe9e1fce946c94a088265bf94d7539ae1b7eb30ec656da7e96abcaee8da4a6: 35aca0f2b9f8c478040e38216ad4f2e9efa65fae1c6fc41a8df2a826f260686c7: 59548e903d1441fb0d6e6d441d39382bb2fbf2f915e94e4c49c6bda187d8c1278: 73b80563a47162cfa99809097caf5d77512af3a28ebfbf76c6bcfd5f572cc1d29: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: a95d574e00e9fefbc454b084e8cb19edc83831071366b2d8dc1af2f7114b646f- root_
hash 17330c6327e6363b8237bd4a68d5ee420a6d0f745c8d8bab0a90305d6bccba50
The earliest published head that covers this entry
- tree_
size - 1539
- signed at
- 7 Sept 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 5f62430a970697dbff207fbbc55e8c2e5cef33d00f3440f0eb91ce69905c40a4- signature
Cp1jg9rr3x9GvHY4Gcbb4Ye3N4dXZIRAhxuuWkgecXc4Q/yKfKaNU1B/1nlLfseihdJ4SzKVkZGsC9+w/DufDw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12