delphi.consensus.snapshot
Appended 27 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 - 2176
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id f69e4ff3-bcaa-42f5-a8f1-8044a9975b0f- logged_
at 2026-09-27T05:30:21.911234+00:00- previous_
hash a85da39fbedc72d348fed3f3aafd8c69d88918ab5b7446f39dc4d4c7bd6b9c65- payload_
hash 7f57fea1bf15a259caa2ef0d464b653ad97807e18e40e10648458bfb9e3688df- entry_
hash 9707c3c7be8115ce5fe9ed9ba8049376e96af97882c57dd020a3072306d0dee7
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-27T05:30:21.905440Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "f69e4ff3-bcaa-42f5-a8f1-8044a9975b0f",
"series_commitment": "2304edd2a59c862fcf9b7129bb0758ec3b16a5d2dd152cad820cb8c3c34f04ca",
"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
117fd5f89a3f7de2dbd68a541165bbd8a84e362ef39afcb996f417378a53bfcd- 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 - 2176
- tree_
size - 2389
- leaf_
hash 28263bc3f23ba795b0f30b68d9f38532afd65e24e164638cc50c6718282ecbc5- audit_
path (10) 0: 8a1b42d50679c206777e7525d00bd53d86727f659c9cce350478f8d938b88c311: 7afca9334cf087bd42ff045e135da3018aef2cb1c40ed8e5c948f676345359d32: dfaab98a4becfd042fb3b37de69ee41784c4630d9d68442d4ea3bb21a87ae8e93: ed3a76cf89ab882e3f8ce250f3dbb03f8c6da0f1d8761cbe57148314b5bd20a24: ca7191c480f6b18f2aa9dda035866fed87fbdd940ba16b9f842e3e09f1e1efd05: 0349dea9398b8aa40633af547e822a1da687592d53272f4e6aa136e48023a75b6: f30320e32b01d85ee25d3699765f61034c40add7177cc53ee3e39fdfed97b4367: 126596474757e47b31a2f4c9d89412108fada5bcdc7a19a9a1de3d4012be0b578: 03c349147789bfb063beb6c472906eef54792e9077566daa1ada925b4ce9b91b9: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 4f7f1a3085d540e3b69ac022c801823029c04ad350f74966858670c2038ea3cd
The earliest published head that covers this entry
- tree_
size - 2187
- signed at
- 27 Sept 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash b1b50955e5089069aa81067ad2479df134298ae6bf7dee437daf781fa54ff0b6- signature
t0dWB84xoVBksXiO35mfeoTvij91UZx6rGZhLHqb2/zFwm5RcmHkzpdfzuu5kxVcT2cgqmmgQGI1XHIHmyc5BA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10