delphi.consensus.snapshot
Appended 30 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 - 1125
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 4bfc7aa0-f12f-479c-ba06-d8e4cebfe625- logged_
at 2026-08-30T05:30:41.190924+00:00- previous_
hash ca986622d54766471c2aba823070cb0953c95bcfd213b1fbfc036c7eb297dae8- payload_
hash 25145073e4e409a882af8616aff719dfdc2d8ea88a5c2b78d0dc055b883c8cf6- entry_
hash 14d1f882da9a4920dc09e1172fa1e56fc356bbae4bd28271f1aa79b5b1413882
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-30T05:30:41.187879Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "4bfc7aa0-f12f-479c-ba06-d8e4cebfe625",
"series_commitment": "23074f476a5f2344bfc34bedb5dc1137c494dec320af3e0654cf9f5dd19ef1bc",
"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
8f5b87e918756c594f1bd307832f1204c60e79deb8a807c1d5bc6dd70119c33e- 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 - 1125
- tree_
size - 2527
- leaf_
hash 7d92c79e7ebb5367ac4810894ca7db25db5cfda91849f7d771266bd25666dc5b- audit_
path (12) 0: d315843714e0afea91799a51958e81150eff9401b0136d138c37c60d4cea78f91: e291e5a5451f128e3082a5cd07d54d1acc3b35c67b970aa64e0cf0f0454f5ad62: c7ae5ee327dc1cbfb5bd80e1d38288e8c038e1d13478d988b4c395a5196b10603: a735ed70c9ee8bfac4793f187b84951baae8dcc85b6c12e8083efd1df93a10454: e4f0fb45f69e62faf8920f9f4026c1fea765f2a12d5baff8498c2bbb19a0f40b5: efa01dd0286ff83e9fd1c8442b397ce07b4cd15d103de784ae87eb507a2715bc6: 3330710dd5fef91aa0e763e3b3c0b21b7b27e549cf2bfbc05fee8e8bfb1f42b77: bbfee2f96690132143d2a2a16089df72535201b31174873b1f1a4d4c85a029a98: 6ce18fb0b650e54a2c9454c3e9abde48f8386826f5bd1752662ede2993ff557e9: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 6a1689c7a18dd6e26bb5ba9aa9beb34e33c31941a6b6f9809c8c7ed6c8391a49- root_
hash ec978d5c7cdf86c1addae478d489dfb54061a2da37f75e4557895152c63d6c38
The earliest published head that covers this entry
- tree_
size - 1133
- signed at
- 30 Aug 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash f93488269a5aeaf9d50291920769e871ba9d361f0fb72089c9ba41c88a2727b6- signature
nnzoG8Yk362jKSvRmRO456zSfVqvhFq0AoyJZsV0jjpigKArT+n7iaJbA8sAIeqGXEUgCqPLF9MrRlQug43xAA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12