delphi.consensus.snapshot
Appended 18 Sept 2026, 05:32 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 - 1940
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3b91df80-00fc-4a4b-b86e-3310edcb9332- logged_
at 2026-09-18T05:32:21.146062+00:00- previous_
hash d2095e170f27f60808189dea530dbba98c024ecd1ffbcfbfdcc8fd350ef4cf2f- payload_
hash 4a2f6c4e16f95ce60d20a3bcf56c319e2fad4dd27c52ddaa371d64513af82ff9- entry_
hash 1bd06b14e2af1637d43cb3c90072806cd7c9c621b13b870ecdc12428c22b4af4
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-18T05:32:21.142601Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3b91df80-00fc-4a4b-b86e-3310edcb9332",
"series_commitment": "f848cd9ba278775bacf91a45e1cc45664b4d12391d5c5e87b605e979f61301b9",
"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
3601520af49f3e6f71a3fba8632d0c26d21902fa5db537b8290f44008bd39d22- 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 - 1940
- tree_
size - 2503
- leaf_
hash 0b6c41cbf2cdf2ad002ff9830b11f55caf83438c66b4463be250bd5ec084afb2- audit_
path (12) 0: bed61d8c105452fafe24732d4040685664d7025aa0e53b35eee75dab2f5b1b3d1: 96453715e9553736ccee421cf0895385defbd5787f0c8b141e5ad039e361babd2: 9c8387e076d05b8bb0945f57850e38b2ef76c8113fe1b1588549e116b80e6d623: bec2a01303f79e00d81a0d29300beffcbd1c0ee87f799a7a8c5a31ee2a6aeb0d4: b9f2de6cc3e44867935ef9833e308607efbad788fe83684134602fe6ce8f26275: 0492878de32691371666ba38c7018e50c68c7b28d04927428f78b3a2ea0e2a8a6: 4e9fd2189aa35b553f1041a8609fcd238f53b35903496c99c13850a60cd15a6d7: 8018b7deda34c522f2ac360ffdd9cc85624549e7457ea594e86a7f04e9a264aa8: 5ab1df6751f0dac25a6ce29d97587d6e08dcdd2d94987223ead725483527e08e9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: aa4b429c2497df4f846fe6b3e60223989226aaf0ba6013dc6f90c17afe986d9d- root_
hash c97f540ea605dcd0a8a4165044c60093cb885a8303800b87d215a424a4d5258d
The earliest published head that covers this entry
- tree_
size - 1949
- signed at
- 18 Sept 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash f455650aa2cf4254c137b61b1d8f7ad47bc080ff7255c20626952c7791299db1- signature
flB01xMion6G9ejOsOY+uXvlOhsUe1s6Lq+SyU/SUGoynHdlnR5iwUAOezgBqbGfIBoqIWZ2I/8SwtSLIvhYCw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12