delphi.consensus.snapshot
Appended 24 Aug 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 - 758
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3b91df80-00fc-4a4b-b86e-3310edcb9332- logged_
at 2026-08-24T05:31:21.441661+00:00- previous_
hash c56a9805e21244146d3c820795e7e0f640b482153e8bef9f2173a324d0ded199- payload_
hash 965e11a7873ccd12ed90d76ee3379204da3748d8e501257cf53e65a05346389d- entry_
hash fee063a8cc3b198003e1220e6d05b7cdfa10735b25c5e13f1ad528574dc61914
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-24T05:31:21.439212Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3b91df80-00fc-4a4b-b86e-3310edcb9332",
"series_commitment": "6ab5f27eb291612d53e52fa7d2d16493980fd8c0b6a6ef139c354a8ea805700f",
"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
2f695e4f2cdc044e90bd893ffbf2bbe9611ad98b709a206c62ea6adb36eb2a6f- 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 - 758
- tree_
size - 2515
- leaf_
hash 5d155c7d529b93b76a1dd8b4d4893ce7f24e42d52a7a1d2870c090d95ae2b939- audit_
path (12) 0: f07b18f734fd49ee1ba22554dbf059d5d1957274898820368ba1c8251c8985e71: 60801b3ed5272701320d1b6fd06d49eba52cf9793f29429799c5849ef25ff6fb2: 3dcb17761ae65c7de7b4989f6c123c85bb7dd79a715a123790f8fbfd009289b03: 55d5df2eaa0215b6d72a9297403a47ec36784b72c6399511c284bc19709a57a44: 572dcf66952f4e8587b10a8c21369b7d51d6a0a18ca3a80837e3a343e014bc175: f61c26919896eb83bd50507688cc1ccfc0bb60fc4cb57a63d694786e83bb71096: 973deb9be25f19e01b3343769d1f20b7f7bf6fe2638c57970f015700d2ee78897: 9580dc2d498dc3b39d2b35bfb7dd13e8996199674c5dfe44e04c8ccc43e9c0d88: 1ed805746441fabcaa9e107f622f886b1692796b8a67f3eaf5f2122c01401d239: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: 07e77d0b86e68e9f9b9a10013a0034c87fc2ef91312163906ab27730e4a116c8- root_
hash 94ed3e67e0f3ca6ab90e872a7f03020d191548311e8610028e47ddc18fbfbf90
The earliest published head that covers this entry
- tree_
size - 767
- signed at
- 24 Aug 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash a28d9edb9694f1cda2f626078fae254accc380b4f2549aa7194ad4e4bd63a67a- signature
JMkjMTErBa2bqo2Rs6CcdmWk6Ehro+QvUn6ngPbf4o9ZZnLXtGSJxijgC+C0p5sEaXG37JHg4YRCxAbtVD1mCw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12