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 - 984
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id fc61e6d4-5001-4db0-95d4-be60a131bd47- logged_
at 2026-08-28T05:30:32.327540+00:00- previous_
hash 8c99e38358bd970267f6f81b002d860812da89b4077df405b4f4fa9bb050946d- payload_
hash c74a99744cc59d44867fbf806b8654822f163dbaffef2a95107d6437eff864e4- entry_
hash 1699a9d43e31bdab7dbd57f8835bef7467cd1a6fbfe0a75d3a0356600af9ec2f
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.323049Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "fc61e6d4-5001-4db0-95d4-be60a131bd47",
"series_commitment": "757904870e43df80259b73ba33995bca498f08f5d2cd581fde9713ed84349264",
"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
2201069a287b65060e14a680169df4c5cd24883904c43ee973f5f0ea36d2c1a4- 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 - 984
- tree_
size - 2265
- leaf_
hash ad2693d24cae7947d8d700850e6fa3634b00200bf30274a320812049739c392a- audit_
path (12) 0: 85390660e7daf4b49047e63da6ccdb4b7a28600f6ecad9a1243489b51331ce191: 7a3291de2e0db83fafec379be4d4ddadd2537bfe14595653a1e0b54503aa6e562: 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