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 - 1578
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id a8c36f16-c0df-49f5-92d5-29bb1d0e58a9- logged_
at 2026-09-08T05:31:41.950926+00:00- previous_
hash 345039fb7771e4a36721cdba3f833ce7ac2c582db3411e872dd4b89b1dee6e29- payload_
hash 1f21948ce91333e37082c31b2852ad9a8c14113a5af10aba0f6980431ef0f62b- entry_
hash 18f1548452bc484e7cb3ddf80b13c87a106184bdf072023a864db58197b7ba18
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.948297Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "a8c36f16-c0df-49f5-92d5-29bb1d0e58a9",
"series_commitment": "3966a9c0ef6d979cbb8231bffa639559fb1b958b101c006c24b4e28fdc35e604",
"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
39844365f2c1a5342d004368cf2fa1c5b033aa34b57d07793b938da6332117b6- 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 - 1578
- tree_
size - 2479
- leaf_
hash f2e95bf1882fed437f3647722d6994e5f169c2b8799692b3f31e43e9c94c7351- audit_
path (12) 0: 7459395928e45e6b6cee7f9f660a26788c7ebc11c8530eb535bcd0f0d66ed6c51: 6826b1d82d4929a56705b63ce8a4f986264eb9d3555867172be2c80f69d422342: 28056f4e54fc31b508edf0fe19cb2ce6c5d0b4edb41396cff9aa2591593d3d4e3: 610d4c945632d2bd3d49d9e2ff0fa424ad7c3926bd51bf9ed89e58800f2723014: 809e28f51f4ac696b3be6332073f7d8f003d4040e293aeaaefd50761ec740ad85: 364ae4f1dc252468c1ac2579db13b9323b70f13f43ce81c26765a4bad76825cf6: a14c441df27a3a317d0289503a03490705cc204897178ef38c051eec450bf5357: f4a858c5afd6d2bbfe79825cc00005d2e5bc4cb6a3723b70509ff06cb4f713008: 49fbc719d10777c21e02e255a1174dbc47e89c67c7b327c5f50e8ea1ffbb5bad9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 8d949d6aef53b2e3322ef5e232755263eaea63b886b405d936c87ac0c842b6a1- root_
hash 2135d33fc3b42de9408df8505e145fcd175142e943af391ea41c56bc99a1e5e2
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