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 - 987
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 7fc5454c-0827-492e-a574-d01f70586fc4- logged_
at 2026-08-28T05:30:32.348604+00:00- previous_
hash 68f4d1cc693b9eb7400ebb0db44277d52ef872c20bafaca485ba86f7df16fd08- payload_
hash 08bd78905348aba027c45d90ece8a122f4dfe89d5e5527de9606bdd29b403655- entry_
hash 242f5f6375cfb577bf7f5e7a3876f56556fcb24d6b8acb1f61425fa9d40954c8
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.345797Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "7fc5454c-0827-492e-a574-d01f70586fc4",
"series_commitment": "c26b9bff56b8d609e5591c2c6329de185b35752a3687e85e433b52cc1bf7b45f",
"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
0d119cc0e274fadbbb30e11879ca1f968a0cde6d0b32c228e97ebc4834cf68d8- 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 - 987
- tree_
size - 2285
- leaf_
hash 2e1521fd342adc00308454668df867c84b1743cea2e1adf16c0460d3361c9fff- audit_
path (12) 0: e8a2c55e8c4d1ae6169e8e6811e92d158d24019674f653934d41ba6edb0dc52a1: b57630e444f76f31a05c9582daa8ef77a79a590ecccd8c0cb0bebb1f8c3731bd2: b0dfb4c0354ff0078cf0b9aa73a4183c812ab8b1f59dba1413702e996e05baa63: 4b0e837a82ed88172cec765f3f8afa5ab18b74abf71324e22bbdd14d34c7d0db4: cab083b9f449354ea28eda265bbc6964f57fe81c1792675c5daff2268b10700d5: 4b41a891f6be390c9a97127ce923d864bd6b99a26d96fe00a062a1a36ecc30d86: 881346e175348d0a346f32907950a49acd79893f71d89e46421e07e28bdd00627: 9f20cfd56c132d1d00fe76cb2e482a3a9b4fbe96bc0d292d29ba8016ce161e9d8: 184a24c3b623669a5fc418f1a01a448ab12c5b650e771370beaf16f761dd2e6c9: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: a95d574e00e9fefbc454b084e8cb19edc83831071366b2d8dc1af2f7114b646f- root_
hash 17330c6327e6363b8237bd4a68d5ee420a6d0f745c8d8bab0a90305d6bccba50
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