delphi.consensus.snapshot
Appended 8 Oct 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 - 2398
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id a8c36f16-c0df-49f5-92d5-29bb1d0e58a9- logged_
at 2026-10-08T05:32:21.094335+00:00- previous_
hash 3fa5051c71caa4d907f17fa8a23c28ccfae90dfadab95df48b01ab6d43119757- payload_
hash fe8cb436a4ef5606fdb857c3568f7ee2bbf846a3b8e23b49e75962397e310982- entry_
hash e9b1b7d12e6dabfca68edd6dd1f5405931c2734a13aa465ed8583accc90a0a3c
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-10-08T05:32:21.087377Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "a8c36f16-c0df-49f5-92d5-29bb1d0e58a9",
"series_commitment": "489f471502463f357c3184e3f1034e0096eb458cddd19200b1ed77e011165933",
"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
1b58d526f6921cebd014e59d0cc569fd701abc7f89e45fe2b78fd581490f1c38- 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 - 2398
- tree_
size - 2479
- leaf_
hash e712c4b35273cf8eb63f51198ed4964da3b5aa6f87b65a46b135484b682ea6af- audit_
path (10) 0: 977a0d3779bef285b431e845850cb207f7547ae20e40d298ceee2a3f6dc00d631: 7c015570d1494590d9af7339431ee8663307aac8c9059b28da302b06b21e3d6c2: 32f4ae1a9c2501900ee51bbfd6de451ca41daac877dbf4a2b3d7134d717c22c93: 6d139f9ed8ada8a8ad0faf4429631a25390bd84f98ec3176d32c2878244c2a444: 5a9b5c3bbfe4872d51680afcd853c4eed3977ea9a65a63d48e58875c83d6ee145: 3e5c5766e4940cb7dda94351a5e27dfc8f706fef9342e7bf2324464ea61fae746: 834c6985c52ea8f25de55920638ea90cbddfd15c7f0b1819c969144787359e5b7: 99ee92a7962953bad0227dbe9ab05c66de08e3b0b7eb51768dee6e3fc62b3b558: 765303d6f29939e50694ecde6538ee53e894bb299166d5a65c9a000adbb546d99: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 2135d33fc3b42de9408df8505e145fcd175142e943af391ea41c56bc99a1e5e2
The earliest published head that covers this entry
- tree_
size - 2405
- signed at
- 8 Oct 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 4eef6060c1a86765c41fc475675c40859e9183cff9ea197195987acb5a90176e- signature
QwUVoQex+SpRs5ZFJNphfLrl+ELAHBLeDYNey7Bjm9lof0t99cJa7JPMsk13JMhvdHw5lnWb+IY/ik34rk9tBQ==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10