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 - 1938
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id f69e4ff3-bcaa-42f5-a8f1-8044a9975b0f- logged_
at 2026-09-18T05:32:21.123677+00:00- previous_
hash 6cdaf6499dc642fc0d5f60b8bcb63fefb2c09f0e85ade791d4387e239c01d21c- payload_
hash 503bf90988a17a695671264a0fc514a711677067f59d48424f460f86697a9613- entry_
hash 5fba4b6aa2bda14d9f31fd629b505179d3dcd0213321e3cbc3edce09863890ce
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.120128Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "f69e4ff3-bcaa-42f5-a8f1-8044a9975b0f",
"series_commitment": "757c9ed34827f2c55042312d9f575d0064399de5ab39b66d2fd39d4bdd938414",
"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
1c4477d09dd874e7004ef1ed96b99bd7bce0feccdc7174aac75695e694ccaf55- 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 - 1938
- tree_
size - 2503
- leaf_
hash 71cf498d536ff9e517c8c27143badf9302a5346e9c5dcce5a86b4a92c62fede7- audit_
path (12) 0: 9a26253e0df4b0739122fd4d96b3923ae4fdf91b23bae529d00815989323f74d1: 47ff4c78540fbeeb1b469c7f14d9de2749be1928dda105df593bb032143711e92: 0a4ba9c68241b1d77587633a68b050da28ea7828bd725b83afcd4ef6207442283: 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