delphi.consensus.snapshot
Appended 21 Aug 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 - 532
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 48ef81cc-e8c7-4059-91e1-550a9ffc1391- logged_
at 2026-08-21T05:31:22.327359+00:00- previous_
hash 61402c80d8a9d147d7ac5e1dbddc45331cd1dbaf6ece031a985f1ea01bfc7114- payload_
hash fbd6cff2af5c8f6d09a36686dc5e36139ed40507b964dba7f10954ce233c4d7a- entry_
hash 71085b5ca43200a815ea1f5ceda63e92f43adec89f6c07575d8a8d103b99d6c4
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-21T05:31:22.324417Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "48ef81cc-e8c7-4059-91e1-550a9ffc1391",
"series_commitment": "0a1ebdbe9c7ba6c2210f1b5c37d07d310964b5dc94d632f20fffdec29f3287f3",
"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
fcf0516b56af4b62b1e1c4d285a45430a01100e7a016bda6edadd3990e309d6c- 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 - 532
- tree_
size - 2341
- leaf_
hash 0a1fc3e48e893ace529ff65afbc14bdba4a01ad72cacad4403d0079d2f9f4712- audit_
path (12) 0: 5354b847baac7c75a4a3528fc1aee09129ff3912a38372d0921183ca6be80cb71: 21b1bc43ed2194fc8ce0c59ebca6cf527588fa7c0b27c80923ddbf57f66c91f92: 20b5371afc8e32a091832ae2fcc4788cb789b4174e5c92f5113eb307c938f7b93: c0578d2bab6d9082b80b2bd24fbce082025e3269239aa3a8d6f18c7ca1e740634: 6a906620a7fa4c9bd1172711aa8294807c7b438fd2ab3c24d4fbc8ea4b4723395: 514fcd08b7a7708fc978766c3847337cf0929a642e3c50313cc548d93fde1c186: d6b94aad0e8d194db67ebed505e85b9867726f564ac0997b7630c3317356f0f57: ca7fb7b440d51df69e12966994a041553b2c0acd85e1779b8e2fe8f79a1a4ab98: 1ed805746441fabcaa9e107f622f886b1692796b8a67f3eaf5f2122c01401d239: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: bd18df2de60e205be411a53ea96887ec76f5a16c15250bf48e3f90dc788abbaf- root_
hash 9f32e37b52a81f4fc0f11a1b956464ef6acde09c58b0ce26dc44277199cb7df0
The earliest published head that covers this entry
- tree_
size - 562
- signed at
- 21 Aug 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 92c30356f864326ea5b77d1d568b8dd46798aa892ea36caafd50798e4442e809- signature
5gjvyMQAKCKkrfKE4aMmyLNO4EIVZGCpS3rtcSxEUacSoDSKoR/3VznuFflGgZKKdSSKpTgTy1ZrFKWVK6BiBQ==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12