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 - 1735
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 04bc3a9c-76fe-4aad-90b1-e3640e548e9c- logged_
at 2026-09-12T05:32:20.876293+00:00- previous_
hash f0d790a467c9054c6faba156f19a157f8fc927fa97b20fe2f28264bd52a0e59d- payload_
hash 7db6f5dc3c4b043b487a5818033c5d07a9f243cca4f6e61246377ce7ae4a611e- entry_
hash 6d0e3080e5ca386aac7c9b727489da9d2f3b9adf188053ab63b186f9bb9c78c1
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.873224Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "04bc3a9c-76fe-4aad-90b1-e3640e548e9c",
"series_commitment": "ed3373f0d0263c88a1709ad86d136c54a81eaecf277ca05f6ccd659ac8209749",
"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
1a695b9215c4447691d9e37452d772c4739b3ebdda842c9ed86ff4d8241f8217- 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 - 1735
- tree_
size - 2285
- leaf_
hash 8cd31e5109b6ed1eb97d6db9a903ca8b56c964c65fdf913f44cb16f584c50eed- audit_
path (12) 0: 8ed40ad49989b89626d4ffa239eaaaca55d9f5f021c675340fbaf11c1d468e831: 67eb4a6e288e5702e7b6dede317e9990687cc23409dafd8599f61b8b37e509382: 52f3b1e03a1bf10fbd5771436ca5b42eebe804d032dc0506cbde2bd65caaab4e3: b814d945d5d232ab17cc126ec80a893077ef532c42c65e282285844adedf13a44: 0c9bd5c162fc6aaf5d9bf93b62d6c7267bc3226cfca9518555e4803f850180b65: fd82ea2957dec252aaf0f497194cc97cb06fa6fdc01911c77e1a2e46ff4eaa336: ac160a0852932e7e1298c12b7bbeac8a979011b4c86d850294a53e9c58329b547: 89bbeb672caa03ccca78c3e7d709e14d72ed0f279c7cfcd435bb71dc863239c68: 49fbc719d10777c21e02e255a1174dbc47e89c67c7b327c5f50e8ea1ffbb5bad9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: a95d574e00e9fefbc454b084e8cb19edc83831071366b2d8dc1af2f7114b646f- root_
hash 17330c6327e6363b8237bd4a68d5ee420a6d0f745c8d8bab0a90305d6bccba50
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