delphi.consensus.snapshot
Appended 6 Sept 2026, 05:30 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 - 1483
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 29f1e88a-b6de-480c-bc2f-f234c647455d- logged_
at 2026-09-06T05:30:21.419335+00:00- previous_
hash ec2a73fabcda7c4198e2dc86c659e40663c90c1ac431b4e7f5acff85b5a2684a- payload_
hash 7532d577e6472f2b192760f650cceee4d6fecc4cd2444db411bf8b0d140a9961- entry_
hash ee898a3a3ced5c75b47bd33e80e61bdcf4392c2f5ff512b73672bff1ec861680
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-06T05:30:21.417314Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "29f1e88a-b6de-480c-bc2f-f234c647455d",
"series_commitment": "b215d22f4d70b16d4c6fe81167cdcd921987413ea8d60c36291573cff9306e43",
"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
c0f7aba0460a7d0b6ee0bae0df377301ff1cbac4fac538ec115f5ea8c5177721- 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 - 1483
- tree_
size - 2479
- leaf_
hash fc2390f3faf79643adeb1db69673c56f27383d99696a11f6e1896dcad32b1644- audit_
path (12) 0: b1d8bb99430cb6ddf59c25045bf87f261339927b1c21dfdd889cb4aa78339c7e1: 6cc5dff7e460567288979833d338e59fbd6ad48153977177f25f93f6c58d08702: 613758c68ba8ec936b88ccb36b4b3546c2ea475ef6bcc72bafb40820bc8174cf3: 07701079593dc85e21d709129f54a92611a58e43a3c312b79b1c96ae6853945d4: c0a5ed0c56c19f12df6f28039ba42c4239cb6bb5489beb861f9b0de2a032879c5: 91804abf66bcb55033aaa7181b9ee3fb61db565440654bb166ade8248335340c6: 35aca0f2b9f8c478040e38216ad4f2e9efa65fae1c6fc41a8df2a826f260686c7: 59548e903d1441fb0d6e6d441d39382bb2fbf2f915e94e4c49c6bda187d8c1278: 73b80563a47162cfa99809097caf5d77512af3a28ebfbf76c6bcfd5f572cc1d29: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 8d949d6aef53b2e3322ef5e232755263eaea63b886b405d936c87ac0c842b6a1- root_
hash 2135d33fc3b42de9408df8505e145fcd175142e943af391ea41c56bc99a1e5e2
The earliest published head that covers this entry
- tree_
size - 1493
- signed at
- 6 Sept 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 1fa4feff08bf18e521e5bb925c6c5fdbb5017b8c298b1beb9ba8937af38f607e- signature
aqpHHBZ3TglMYwcvhOlfahpQD8AtFI2Le5O0NnqlhVLEXF/fDrgc8TON7pwPSD6UixQPbRrEyUkW8rogVxpzCQ==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12