delphi.consensus.snapshot
Appended 12 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 - 1738
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3b1bf8d0-fa87-4392-b4cf-333e6cba3622- logged_
at 2026-09-12T05:32:20.898343+00:00- previous_
hash 84297024acb23f70563eec822db19c93c4707ccfd7e6f683e09507184bc4c3df- payload_
hash ac895147ec09091a54dcbd0c417306007212fb3b89d4e2807f2f923a49c0f8c1- entry_
hash 1ccfc13333fae6a63de2442f35fec68a4159122deb2f266714d122a5ae37410c
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-12T05:32:20.895875Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3b1bf8d0-fa87-4392-b4cf-333e6cba3622",
"series_commitment": "b2762911dfe63502aa7694827f7f8bf1baaa718e612dc946e919906b52adbe8f",
"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
0029c37c0579b9ec3fd07a507bb2dcd2c1c97369ba8f446590eff24aad211599- 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 - 1738
- tree_
size - 2305
- leaf_
hash cf7f844fa87af3191bf6ea75826956f18691f7d2c2212243ff95e9b7b1104870- audit_
path (12) 0: ff6ea4973d2222cf096f71708e14354828f91d137abd0703dac2d00248e8f6c81: 19d0536740cb5a6bc78d4e6301fe4cae8d7d18b0a94a5e9586ae6e6b9c82b4ce2: 4175cc4cebe6e682022c589321051accadc556b88f023bd207f3f5dddb63cfef3: 635aae6193961455327075b2fe16ff662110a049f19d8f0882cf12b56058acb74: 0c9bd5c162fc6aaf5d9bf93b62d6c7267bc3226cfca9518555e4803f850180b65: fd82ea2957dec252aaf0f497194cc97cb06fa6fdc01911c77e1a2e46ff4eaa336: ac160a0852932e7e1298c12b7bbeac8a979011b4c86d850294a53e9c58329b547: 89bbeb672caa03ccca78c3e7d709e14d72ed0f279c7cfcd435bb71dc863239c68: 49fbc719d10777c21e02e255a1174dbc47e89c67c7b327c5f50e8ea1ffbb5bad9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 4ed47b3cf2c766bbf573b761e9026e21f264edbbd6420d65b1efd886894c770c- root_
hash 9259657b60d7c54c7f061a7a621bf2f8747cab0885ee335ac1ed3b6657c9740d
The earliest published head that covers this entry
- tree_
size - 1749
- signed at
- 12 Sept 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash e8cba9a99f4a57e7aaabf2bd0c850bb0715afb51953cf8fcda65ca036a6c608e- signature
cNlPz9oqpkHabbJeJhuOvJLMF32ooelAhyWb8yHCQmsqZM9LEZ0petdc0dMGAZbz5avsJ6pUSC4TluX7fEBpAw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12