delphi.consensus.snapshot
Appended 3 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 - 1333
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 24c5a768-70af-4997-afe5-05e9edc2e4a7- logged_
at 2026-09-03T05:31:20.911332+00:00- previous_
hash b873c0ff8f8936fa5a8a95145afff3b4c8571c7f1fe445d4a6079bda4475e99b- payload_
hash 8b62d7f8bcb0ba2bf31b1e7599a417db70d59f0d63ed4edd2c8d2d578543ada2- entry_
hash 7f15e621fcc799bb21a4ba3267f3069c7f2aa8ea65e04281f4449e53c3b0509c
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-03T05:31:20.908098Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "24c5a768-70af-4997-afe5-05e9edc2e4a7",
"series_commitment": "086563105949f5af9ebb9a43dea9d3c3e284f68d975f92b9f76297a4ba514f47",
"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
e1e1cace8e22747aaa0adb36cc2b94317f1bdf654e291646b80ffc5db5a96ab4- 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 - 1333
- tree_
size - 2539
- leaf_
hash cdef7092f7c7087c75e07c586d9122c7d8a645b66ae6254520c249d5f7f804b2- audit_
path (12) 0: 9c361f8a9067be645d2e0a8bb30fc0a6ece37fc502ccf793951155a5a26c43ec1: 9e03a13e1ec9c12ba52a2792428d32c15121d57f2652dfe11fec57dfc2aa947f2: 9a63670a285cab92b06c5aa6d5290cb20e42dda345403c951c91781c274f71433: dfbe1af2d4d370a02df80cf16ad32518b6b20d84466dc8b341d3fac9f970d08d4: 2918c2aeb1134879bae40b295e56941c654043e35aeceab2d852a6af12421b575: b36c7c4e17776a5c001456b78736a38b0060838a2c1cca456f37637a9e1267416: 1856e988c0ca2de1232e3499545b496b7d991e639165b9289a3c3dc3f273d8d47: 00aa16d00eabe2b61089fea4a6c3044cf3b1ced9f2af168276f93e239a98dae48: 73b80563a47162cfa99809097caf5d77512af3a28ebfbf76c6bcfd5f572cc1d29: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 7833c416a5e9084d256ef204718818c64927b373cdeabf763b837dcea4eed9bf- root_
hash a725a4fc38f9ab511b484535b065f2f1d402485b98d909de2b2560ef782dde90
The earliest published head that covers this entry
- tree_
size - 1349
- signed at
- 3 Sept 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 7f923b9e276353e56131136c5f2d8734810b3ae593a7802c5ab7323e72ba7b33- signature
cFBBIpZO7O16ciWU8zV0mJX+pH5fdC2cAi7r1uTf6xLxXWweGyK8nkOKKpKkMiQp66DEILlOvMRMH3A5aU6FAw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12