delphi.consensus.snapshot
Appended 4 Oct 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 - 2332
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3b91df80-00fc-4a4b-b86e-3310edcb9332- logged_
at 2026-10-04T05:30:21.153523+00:00- previous_
hash 1424c04dc318e416e8ed87f828a196e0ecaddd4b89b24f37de6c4e9384fb0b97- payload_
hash e27b594012e4c694d2f7b8a855dae59f027eac956751321b8d5c5585bc24204e- entry_
hash 726d6d668e3767743715b048412a9a39aa99d77cf2c392c7689c0fa4f98cd5f6
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-10-04T05:30:21.143384Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3b91df80-00fc-4a4b-b86e-3310edcb9332",
"series_commitment": "b9a95a026605277ad49b562d5be0da27df35e4142ed9f960223fddd9f2735324",
"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
8782c1d6f1e60434969931ea91abfd5c7837f0ed3fe048eeeda2dd16bb34a9c2- 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 - 2332
- tree_
size - 2389
- leaf_
hash 5fa7a8af72b78b1f0da126da5def2e0803c57ff3ef51faf4030d6c0a2ecff51d- audit_
path (9) 0: 1f4696a94a8dc69aa5cd936516de720b035b25a8db1471ec9a62680610f1a6451: e2c45da37c336f07851d303e7a2b1cbaa5cc09036017de2819d9c24f7ba0ec042: 36435e33d92c7db35301b061e47f8b11a17a90bf3d67d6652a8c8ab1daa853713: e4b8a71b844ed5f12e965aee16ea73f6f5bc8a82b5e1c9f8bde5458e3d7fbc604: 5c26e136e60e36307df95582430f3ae73b38a515c084d9e67286aac314bad5075: 8055e8d16004c9bd3edc12cb580b60b66991d223747a8a1be5c476f954671c5c6: a996b154fe63ce51a611e48e1d6360e7e9e40f1d5821b39e97eab310e640deab7: 765303d6f29939e50694ecde6538ee53e894bb299166d5a65c9a000adbb546d98: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 4f7f1a3085d540e3b69ac022c801823029c04ad350f74966858670c2038ea3cd
The earliest published head that covers this entry
- tree_
size - 2341
- signed at
- 4 Oct 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 9f32e37b52a81f4fc0f11a1b956464ef6acde09c58b0ce26dc44277199cb7df0- signature
aIyBq7WrK8z+2h6auUYK0NfeCTmCYzALpNq2nd+/ftrgcBTOpYxoi/MI/0VyV7rvp4VcCF127Asgtj/m4wmxBg==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 9