delphi.consensus.snapshot
Appended 28 Aug 2026, 05:30 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 - 986
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id be56b97e-fbba-4073-8b29-04e6afa28138- logged_
at 2026-08-28T05:30:32.341982+00:00- previous_
hash cb7cd04029b5ffe251cef042d07d49f1adbb221b4dcaf529c35f49121be7a0fb- payload_
hash c534a2cd4588bd87f85d70a5e5da6d52c7baae3ae0c6f3dd53972e5ee7268c6f- entry_
hash 68f4d1cc693b9eb7400ebb0db44277d52ef872c20bafaca485ba86f7df16fd08
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-28T05:30:32.339718Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "be56b97e-fbba-4073-8b29-04e6afa28138",
"series_commitment": "b5c939051edd2b8ac0817b0ee9b5240a927f101194604a2cd9f3fd759214433a",
"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
85e2d228107f5847b390dc77aa97783c760fc5ca063bae1e031af5a9a5a9f34a- 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 - 986
- tree_
size - 2265
- leaf_
hash e8a2c55e8c4d1ae6169e8e6811e92d158d24019674f653934d41ba6edb0dc52a- audit_
path (12) 0: 2e1521fd342adc00308454668df867c84b1743cea2e1adf16c0460d3361c9fff1: b57630e444f76f31a05c9582daa8ef77a79a590ecccd8c0cb0bebb1f8c3731bd2: b0dfb4c0354ff0078cf0b9aa73a4183c812ab8b1f59dba1413702e996e05baa63: 4b0e837a82ed88172cec765f3f8afa5ab18b74abf71324e22bbdd14d34c7d0db4: cab083b9f449354ea28eda265bbc6964f57fe81c1792675c5daff2268b10700d5: 4b41a891f6be390c9a97127ce923d864bd6b99a26d96fe00a062a1a36ecc30d86: 881346e175348d0a346f32907950a49acd79893f71d89e46421e07e28bdd00627: 9f20cfd56c132d1d00fe76cb2e482a3a9b4fbe96bc0d292d29ba8016ce161e9d8: 184a24c3b623669a5fc418f1a01a448ab12c5b650e771370beaf16f761dd2e6c9: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: 15428b80842f9a0801cf7667918b216c9ce4186d9825e806ba86972b039c03f9- root_
hash 0feab2262fa1e39174e25fc17ea9383a6fe15fa5d22c96afd722849e59baa3f5
The earliest published head that covers this entry
- tree_
size - 1013
- signed at
- 28 Aug 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 31cb04f309e462f9e86fd5e2a26aeee8e0d75dfba1d3621c2717df431964a503- signature
p3eUja3ft5l0E0pT2RR92l4L5xcWlnzXx8qcK4NoGop0OIzErqTrbzeXab/1p1jrJ2TAQFjcSRJz+xTVBU6JDA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12