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 - 1471
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3d483c76-6358-495f-9f25-5cbef90fc78d- logged_
at 2026-09-06T05:30:21.323724+00:00- previous_
hash 3184e7e6935618c2e904a9d012e034635643ae1b2320daf577d34477f868f7f2- payload_
hash c95b218aee897458c435ef47c11fd1cb37ac60f89394a5cc26d47a18935972fe- entry_
hash 54770fa2aae6bc87efb9119a5682ad5700fb53eacedc894f67ecd25f3c505387
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.320368Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3d483c76-6358-495f-9f25-5cbef90fc78d",
"series_commitment": "573edadddc1f0a210cfd8b46ec72920fb05af3e646be5d16c3fe057bb39ec571",
"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
c2525c6f4f093ae00b682e5c48cbce61a260cfb5b496a35e287ab1266f200d48- 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 - 1471
- tree_
size - 2239
- leaf_
hash 155a68597a989c8279715a49d6b488ce4e75c8537cbb507d1a6ebbb093705c78- audit_
path (12) 0: 98fad43d8b95ec824f495f66a84f62b7d3c79f593892ad276c93e394b3332b071: 1ed25be685c52c1fdbc163a45998659ea00dd551dc9323885e4a3ae0d91200652: 648901d7292c4497bb9ffa6ee330501e0ab717c4ae397b4f0c1879e64229b1963: 42878820b43512c1c2a2581b37f5793117180ef94b0b6fb782bc174177b1b3124: 9e3b1fad5bed14df89530da1d2006a48cab26220fb47a6eebf75bca76dedd3df5: 739ca866d241c50f0e2e976ae4aa9642352c635f5cd45baa14657876e95d20b26: ef252f031089471cd75411471a0532012f4deaced96acde8a10c0024e7faaa357: 59548e903d1441fb0d6e6d441d39382bb2fbf2f915e94e4c49c6bda187d8c1278: 73b80563a47162cfa99809097caf5d77512af3a28ebfbf76c6bcfd5f572cc1d29: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 9203a1600de814d3afb819f841569332c7e3b58c4d0e0ea56c377729f25dca49- root_
hash 03dd6fb33b4bd65222257eec0069956926795f14f7354795bcb42af5fe51ba08
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