delphi.consensus.snapshot
Appended 8 Sept 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 - 1569
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 24c5a768-70af-4997-afe5-05e9edc2e4a7- logged_
at 2026-09-08T05:31:41.889274+00:00- previous_
hash b0e3d4a908e9950524104f6fcc78fc2aa80df8bf4aa19424928b2a74addd26e9- payload_
hash 4438b2b368afb8156faabd03a1347862cc3d67ac1ff34788fa5a440b7ec176f3- entry_
hash 599dea3d4bd0398f386f9e06c910aa4b406c4c2c13da290c0b91d3b407637dba
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-08T05:31:41.886590Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "24c5a768-70af-4997-afe5-05e9edc2e4a7",
"series_commitment": "ec6e6bfd98609cd1809e7efd869054887cb86db44e909417666cea12cca3e7f6",
"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
e192b92e9c752fcf5cb8f2cc15e6ca153cd5bed82b2c587935128942e20ad3b6- 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 - 1569
- tree_
size - 2239
- leaf_
hash 0d6551ec788dda50cdbafaac76f2df714acb4409d6679854ee5953c0d8942250- audit_
path (12) 0: bfc0ea6bf9b4e85edcf8dd30a0e63af9b0b72374241e5ca4c45fe9b5f0bee5e21: 4f2649e5f5f6a2ab0a9c9f8d58038c738b5a33b53f3c71e98a1b40c2210416232: ea770924285e82686307be9ce890a3dea8465ae43a9f2c80ede084ec5cc9f9443: 2fa5de6f80c93428cb6a0692def00ed5f75c808248704d534f2648d62349067e4: 809e28f51f4ac696b3be6332073f7d8f003d4040e293aeaaefd50761ec740ad85: 364ae4f1dc252468c1ac2579db13b9323b70f13f43ce81c26765a4bad76825cf6: a14c441df27a3a317d0289503a03490705cc204897178ef38c051eec450bf5357: f4a858c5afd6d2bbfe79825cc00005d2e5bc4cb6a3723b70509ff06cb4f713008: 49fbc719d10777c21e02e255a1174dbc47e89c67c7b327c5f50e8ea1ffbb5bad9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 9203a1600de814d3afb819f841569332c7e3b58c4d0e0ea56c377729f25dca49- root_
hash 03dd6fb33b4bd65222257eec0069956926795f14f7354795bcb42af5fe51ba08
The earliest published head that covers this entry
- tree_
size - 1585
- signed at
- 8 Sept 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash a224a45fec4b50dd9d3a17f401a022e1320b8849bcdcf3109bc5ef8fc4c335cb- signature
xJYNwZXpQpbXcZskXqf+SutDkfY7nOE9BO058X7fOfif0VtoI/OM8Nfg0bN8D3iUjEtOt+FT3k9g7zbVw7vLCg==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12