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 - 2174
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id cd22f6a9-1eb7-4927-a2e9-6736a77b75cc- logged_
at 2026-09-27T05:30:21.881385+00:00- previous_
hash 9c4db0d44a134e951e9f126e3b2c24edea06635a8d62b670ec6cd6bacb202ee3- payload_
hash 5a4c4138e6c4078a81bbeef66afbbadbb9ea9be04c27ec7594b91cea4460cac9- entry_
hash 440cc7d9c5b0dfb462f366e79d6c09b201af559a2a5a3c2b2ae36f812f337b9d
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.873535Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "cd22f6a9-1eb7-4927-a2e9-6736a77b75cc",
"series_commitment": "63e959575c3b4b0e63c108bca99344463176f99933998ff1163f98a7c4c60cba",
"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
6120b9c47b5e0350ee3d4a629be674ec9ae13c89cadd0e56f94215acccd6f58b- 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 - 2174
- tree_
size - 2389
- leaf_
hash 23dc5349bda29a9fb4bbffe052ecf65d2aa86409dbcaaf0f9863864cdfcc3841- audit_
path (10) 0: d8ff3861039c73f0b6b32930fc0cf6eaedfc22258bda42573e0350bd615b021c1: 9b1e12d6d39a8c4e38649a953a237b9c95bde057280f42fde222061dc9814f792: 93223be8e555a6577a4d09e1c9d5883bf398350b554a5368d9bb7fdbe5d6854d3: bc54494ec26d46ee6d53a8ac2b531e6f585610511b47874527317bc58b5c78604: 9ae41f12a8d808947700fd5bb9f854759bbc814a9dd681b7d300197e26a268795: 50cc49d79f0f3c552cc19006c4d6b819801e07bb4acb2a3fb50f66393c28555e6: f4d02cca79f588f9c172b1dc53f54784db35848f8f8b4fa96ae1493d76b463787: 32d97e61743fccf6d32da7a407cb944cdd5c52aa0de4e874e2c78dadf7892a908: 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