delphi.consensus.snapshot
Appended 20 Sept 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 - 1994
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id f69e4ff3-bcaa-42f5-a8f1-8044a9975b0f- logged_
at 2026-09-20T05:31:21.025001+00:00- previous_
hash eb6f4765da3758fc3e43c4a547a0eda46dee5da00dc5a16359b21030b6683de2- payload_
hash eefc47b78bd224aee7f9335d3211fbd6dc97a0c37067293572faf469d2029c3f- entry_
hash 1be195bce5031bbc944000d8bbeedeb2b776a9e9ab02fe2887c7cd3337b6499f
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-20T05:31:21.021238Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "f69e4ff3-bcaa-42f5-a8f1-8044a9975b0f",
"series_commitment": "480a93fda656d25292f35559b993fdd041e969257de26cc3d96ce1fcaace8e3b",
"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
c8f3846b75c08528c2c83287208ef96a4120838e640af03b1a9ae0616d2f6f7c- 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 - 1994
- tree_
size - 2479
- leaf_
hash eeb2eed89a5229cf0faa9e5f5e217645755f51971e64ce6ccfa7123c023b30e2- audit_
path (12) 0: 02f7adb49c2d07a0147312370c8a1412072a3f2d9d5720049884222156d7676c1: b8f8a1375808a38d5d2fce64a553377667007b3ba66556bc64fb9d5e350d15a22: 08ce321bd625303eeabe6db631b66f753b926f3f6f26cb7c49b96c6d959c647e3: 98e98cb2e99e90a10792886412c376d983058e52333234e7e071243c68afeb474: 0660e870df08b3e5f265fe28da6fd51268d00673b6dbcff1999891e134500c085: a50e0e977ad9842f45f35f6e8d03b29bd4c453b61b361ba211d57763c2a168e96: c321285e45ea8a57cf869ad4aefceaa5840e364ae5f182e7b0c7b58aab9054be7: 8018b7deda34c522f2ac360ffdd9cc85624549e7457ea594e86a7f04e9a264aa8: 5ab1df6751f0dac25a6ce29d97587d6e08dcdd2d94987223ead725483527e08e9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 8d949d6aef53b2e3322ef5e232755263eaea63b886b405d936c87ac0c842b6a1- root_
hash 2135d33fc3b42de9408df8505e145fcd175142e943af391ea41c56bc99a1e5e2
The earliest published head that covers this entry
- tree_
size - 2005
- signed at
- 20 Sept 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 60e3cd283b73840cd440288cca33b52ceafee6c202d421678a412f3c5ee05946- signature
cd67hFwY1ta97P30k//m20Gy5B+NCvWm0//2kBrcp9vTc1CKExyU43VM3CfB7s59bHxcLHAWq/omhe+LeHwvDQ==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12