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 - 1565
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 05901165-61de-4a02-b759-02a9bf89ef70- logged_
at 2026-09-08T05:31:41.845309+00:00- previous_
hash a14dacbf20da6698b153202ed06f5cc091bb11dcadc96c0415cb7852cce30c75- payload_
hash 2a199c300c61a53ab84dcc3f6530365fb0aaa50b13f48525536a856b715d3703- entry_
hash ea46cf1671eb6ee063da35a23edc193eceecb5016ffed4a027954ead06dc20fc
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.840222Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "05901165-61de-4a02-b759-02a9bf89ef70",
"series_commitment": "3fc7fd786b89a27630ed006054d3c07b97a6c9e3a40d9fc2fe6a04f10b94d3ab",
"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
92e32aa8cd142373af9241960ca44b1b5fab487ef31dc4adf249b14b485d1b59- 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 - 1565
- tree_
size - 2239
- leaf_
hash f844df584468c24dffed79ba919ad6fd3d92b2b3175ecdb44f3775554312ddfe- audit_
path (12) 0: fef43d3db6a3596a40b1d1c1970c5a82241aff6efcd513307eb91a20ef9de2cc1: 2c1e8bb6c57363ead33c68b44a605e51f870e6a2b949e2077b26fc0be9de5df52: 82ae525b8850446a9092cc7af4aff6abe0ae575b8eea763b59084618041a0c653: aada6ebd03991fa1d61f61964da5ddf98cb3d8156ef9befae4c29aee12f5668d4: c63c56181eb3856824b063325b2e6c8ee64431e679d56e9238a6872228f648755: f2f7717586444815727d63f86cc5877958512d732169cabce0cefd8ec595f85d6: 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