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 - 1935
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 04bc3a9c-76fe-4aad-90b1-e3640e548e9c- logged_
at 2026-09-18T05:32:21.088645+00:00- previous_
hash 1e1dc144574fe50a27b3e767b79a82889d6ff04dfa91d66375cb899e7081e1f7- payload_
hash 6de3fd3d35e0610755ca0b411353d240ddebc4abfc04fa32604fe47b339d86dc- entry_
hash 51534b4ca6a8681ad0160804de9b3e834289cfc52035d2eb27a3499fd02fcd91
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.081089Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "04bc3a9c-76fe-4aad-90b1-e3640e548e9c",
"series_commitment": "5776ed71f8317d18b18d34027cb1c249a9b8428c364012b1a9bb652d7bd3e8a7",
"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
82a29d6950ffca8c1184cbf503a1eb656fcda0ceb91f8b348c08d09ac42e3164- 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 - 1935
- tree_
size - 2265
- leaf_
hash 3c86f32313b9b361da47983a1dcd62fec911b647a1d33b2a3d17a4797077bb54- audit_
path (12) 0: 7d68ed42e291192709835923a27d04435d2adccfcaf74e1039fb273ee77d97b01: 1710f09af3d7cfc60584263623498696eb0c143ecf99261c3e54448d14d3ca772: 62b480cb2a257111acdccaf80f55fa5902f218ae6d045c84135fcd955a69ed473: dd036f4e423237898ca984bd6a31d7d58489a56812cb0e764bce24d9bfcfde194: bd7e33a8e8f23eb84b953194e9bc8cea4652a2b0f17357bc68363a71dac493885: 0492878de32691371666ba38c7018e50c68c7b28d04927428f78b3a2ea0e2a8a6: 4e9fd2189aa35b553f1041a8609fcd238f53b35903496c99c13850a60cd15a6d7: 8018b7deda34c522f2ac360ffdd9cc85624549e7457ea594e86a7f04e9a264aa8: 5ab1df6751f0dac25a6ce29d97587d6e08dcdd2d94987223ead725483527e08e9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 15428b80842f9a0801cf7667918b216c9ce4186d9825e806ba86972b039c03f9- root_
hash 0feab2262fa1e39174e25fc17ea9383a6fe15fa5d22c96afd722849e59baa3f5
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