delphi.consensus.snapshot
Appended 3 Oct 2026, 05:31 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 - 2315
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 4bfc7aa0-f12f-479c-ba06-d8e4cebfe625- logged_
at 2026-10-03T05:31:12.404617+00:00- previous_
hash 679323822d6953f53f29b64b2ace8ebf8ec64b58877ff002e5aebd7d2e8ea4ca- payload_
hash baccf27ad9e779fb2e7ce805090e2025d4ef54ec7da0afe6fc60643048773ddd- entry_
hash 9a8cde36f30e93ccff30eae7438f494ef31e18c0190e687a2be93f194e0d6d28
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-10-03T05:31:12.395474Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "4bfc7aa0-f12f-479c-ba06-d8e4cebfe625",
"series_commitment": "085bb24e1b33c8b147e5ad3a906e2bfacfbc6f3115b0ff311e2cff1ff503024b",
"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
33f96195b4eb6a105652516e8fff770d1b7079ca3f71d99735e3c8391246645f- 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 - 2315
- tree_
size - 2479
- leaf_
hash 17fd48ddcd67dfcb0e93cf622ca66c582c391d6df004405ab5d197e8a3efbb07- audit_
path (10) 0: 86da81953997ec273b080bcb687446a4cf58dbfdc46edf932750580f71583b801: 666b243b720c610f4e87a4f3c3c2c179d3d3f9db91bcc26cf09677b8f58e16412: be32868ff4017ca71406d15fae2443047bd3481afe2bb89f7e21ae99886cdee73: 37b07d7e5dd5947a3c43fcad9f35a0624ed0dc80c484579a0c9e5980add1b6644: 2a8d45d5c5dd1d335c8971c0f86db7634941560caa50de678092b2fcafebfbc85: 8055e8d16004c9bd3edc12cb580b60b66991d223747a8a1be5c476f954671c5c6: f60923cdfcb3584afeffa8530ee1cafb60e6a0aff868cd02794b4b9e5ed208eb7: 99ee92a7962953bad0227dbe9ab05c66de08e3b0b7eb51768dee6e3fc62b3b558: 765303d6f29939e50694ecde6538ee53e894bb299166d5a65c9a000adbb546d99: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 2135d33fc3b42de9408df8505e145fcd175142e943af391ea41c56bc99a1e5e2
The earliest published head that covers this entry
- tree_
size - 2323
- signed at
- 3 Oct 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash d5cdf3ada5e9d6ff6f86cc94c6a7cd9965df1cd86b6e68dd8030daf1fd3631be- signature
1BQCMtKOV4dlhWYjBYTSEwsJ7gT5IVLMC39AMQobNHEVmLfgNgJd2teZf8zEq6geGuh0vLM1HXVqdZvXtRtjBQ==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10