delphi.consensus.snapshot
Appended 19 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 - 1970
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id a8c36f16-c0df-49f5-92d5-29bb1d0e58a9- logged_
at 2026-09-19T05:32:21.253346+00:00- previous_
hash a496c48641117183f089098c00f26147c9edc791704a0b0a42e3540fcf80c64c- payload_
hash 8b76c3fcc8b938eecccb0c7ba70a0a8505c89b77393f2a4427dab536307db320- entry_
hash c7b6831154dbdc6e92a5613e68267fff085656ef6ee60d14cfd546bfe03dfbeb
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-19T05:32:21.249018Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "a8c36f16-c0df-49f5-92d5-29bb1d0e58a9",
"series_commitment": "a12191c9efaefe85753cafc51cd047a30605f72fb3c6d9ff24d0c700bf72be65",
"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
b6f1c8d0893d4ef9eeb8910a32bf99065007eb35e55d44a8f2cd6d8158df2ab5- 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 - 1970
- tree_
size - 2491
- leaf_
hash a031a88df289cd6b54c844de535a46be584fbcafe24ca7063208c6a59f8bff0b- audit_
path (12) 0: daf4798db10d030a14632dfb971f2c3fb271dd6c727a6cb20265f368a36047ca1: a895605af72d5a369c9fa1f17743f1ea94e7a52d5de76227abfd435ad0f099692: 0224170d78ac56362e60b842104effe38125d142e1e119ccd74671c754f8e7423: f020276f2bbfe6da3d7b71623a484adf09e16a30f6a6e238131bc2e50cccae3b4: 92ca7172219fe5bc447476e5ff68272a0b5af1cbc550f81974bb208599433d2e5: 606aaf5303d1bdf7e430fa009f7a3bea14fe2b3ffbd61e9b69f34d4e43ed6c6e6: 4e9fd2189aa35b553f1041a8609fcd238f53b35903496c99c13850a60cd15a6d7: 8018b7deda34c522f2ac360ffdd9cc85624549e7457ea594e86a7f04e9a264aa8: 5ab1df6751f0dac25a6ce29d97587d6e08dcdd2d94987223ead725483527e08e9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 083d0806ed3c3d656f2d8c4762013d3fb4c0ed984cb03e95e8ae46936f2431df- root_
hash a9a1dac66ff7c8ec3d4b27b434ff70fbde5df3ef3dcd4b4fe4b41bb80f78a7c7
The earliest published head that covers this entry
- tree_
size - 1977
- signed at
- 19 Sept 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 030d7ba0b761b8420ec6a8cc0c7a9c0b31f4c2f6ef433ff99c5ab3364ba82ab3- signature
46yzVUF2EU2OokUFFvY3uF63GWco2kfLcbaKRU/lmofoXQRYagMPrSTh+OnmHDVsj8htaTgxoLPexSkNWBXkAw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12