delphi.consensus.snapshot
Appended 22 Aug 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 - 600
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id ba007bf6-84af-41a3-bad7-f36ecf2ac953- logged_
at 2026-08-22T05:30:43.250747+00:00- previous_
hash 1ccf684cf2f84179749a1ad677910a036b74f3aefd4b92c4b536f1bfeadbe601- payload_
hash d1aa8546e263b656678beb58be78e146b46f69f50602b03c445fb4dd19b74e3d- entry_
hash 5959c2a72125b8d855c6fdcadd02150ce843ac94b5d0ca787d9c19fd7d9800bd
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-22T05:30:43.247981Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "ba007bf6-84af-41a3-bad7-f36ecf2ac953",
"series_commitment": "b0c2b3620b93405a83179fadad060732759fba2869674b667c7bcabc210bae1a",
"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
fea2910698ebd4f4a1ddb53e25c0005a6ce515fabd4cbc5093a67ebe996f76f5- 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 - 600
- tree_
size - 2265
- leaf_
hash eb164db9d86f6bcf574749746565f5e6a98df946436ab866644bfedde64dfc5e- audit_
path (12) 0: 72fddc95d2e269ca1e7ccbc47ac043489340db33ad10979d13777ba1f618f4fa1: 00104302c4cfd4864cdc6524248316ce5296a0b1a6b6c1b3f2d20d34ee819c402: 1bab96f8e2ee86702205b810dca8c11b7cce97dd8dc0467510ffdade1267306f3: 5220005c0a86cbc8fe6dde379254e3ada945f9e965340b95839870034860a88c4: 9f1dab1bdad6a3dafd37f58d152b6385fa55aff434f786595e4a900c74d597f95: 89673626539af9d3d599d3b42d3ef89916644decc1454127ebb129fd50cc8e466: 66d783f1a4106ac8ea73f0464db5328d95910b9613d356ca7a4d7238d180ef957: ca7fb7b440d51df69e12966994a041553b2c0acd85e1779b8e2fe8f79a1a4ab98: 1ed805746441fabcaa9e107f622f886b1692796b8a67f3eaf5f2122c01401d239: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: 15428b80842f9a0801cf7667918b216c9ce4186d9825e806ba86972b039c03f9- root_
hash 0feab2262fa1e39174e25fc17ea9383a6fe15fa5d22c96afd722849e59baa3f5
The earliest published head that covers this entry
- tree_
size - 632
- signed at
- 22 Aug 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash ee7d3fc82f5aaff8097c262dfec5f324866dcd66ff2f57c5f03959246ce30e44- signature
5xMqhp5mkjyNaCZDqNNz8sCOKCPVWpN6XP3+g1675vS1ryFscLkuSpbpJpoeP1G64a52gFmsNs2Hi0lgRWDDDA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12