delphi.consensus.snapshot
Appended 2 Sept 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 - 1279
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3d483c76-6358-495f-9f25-5cbef90fc78d- logged_
at 2026-09-02T05:32:20.765203+00:00- previous_
hash 5141d8f8997faeb917edecdfc2423bb092b2a096b57dafb11d58229df95c7c67- payload_
hash cb07bfd3c0aef34b3276f1224c9fa23d16ca34ee8fcd7aa9959c8d0561a32272- entry_
hash 5c20af38460d12094a1449fc49b75b97cf51f9359b9c754af2411f4ac03985d1
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-02T05:32:20.762330Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3d483c76-6358-495f-9f25-5cbef90fc78d",
"series_commitment": "6b4c5b4eefecefbc9f03298ce6dfa54813a20e5b1f36b10c28f08401fe56e988",
"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
3bc1ba7eab6117e703fe2adacbe48721c6288f82b95a29bd5a2c2e9033730d9f- 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 - 1279
- tree_
size - 2265
- leaf_
hash 5e57c305ddd9ee8a73935dbe7f6f884df402225c18f6c8ca3cd8e2301ce445c5- audit_
path (12) 0: 9d8d92e77b8a396afda92cce84d29e7b4f59eb021844be47628f1122770a501b1: 4d67530d6aedc9a81826214b2cb9b07f2dd605c1df04a7bd9ec119bbd81265262: 335d06b652f4653a401ad04ef24c9f6ce41735c184fe93db79839df5a68e5f8f3: 866fe3027eaa94b340fe4ea497d5b7c08fabbe9efe46d1186ec61385c8475e364: 38b17a82d2f2dc8c7ecbc13070b577b9a041e9eb93c528cdf9a58a66f2ea7f5a5: 8578cb2ca55eff365f20765077ed8ca1d3ab9d050ffca53408e9e038e9e51b696: 669172607016fd0304cbb59132e0f82cb4f48e391f29d72a97f4ceee2d3ffff47: ccb0e9f17cd47f20723bd8ade751778a3fd4e9649264dffce135260eaca872fa8: 6ce18fb0b650e54a2c9454c3e9abde48f8386826f5bd1752662ede2993ff557e9: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 15428b80842f9a0801cf7667918b216c9ce4186d9825e806ba86972b039c03f9- root_
hash 0feab2262fa1e39174e25fc17ea9383a6fe15fa5d22c96afd722849e59baa3f5
The earliest published head that covers this entry
- tree_
size - 1301
- signed at
- 2 Sept 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 7412c3bb0fe0de978d577bfb7d7e6c78c4415aac29193a116b150bd1dc28f398- signature
NpyT4m8rheEfWbFdEQNnccQG0Zzl3KXO1wHnZx7zD3lNnn81UHz/zavu3VUhzj72XmrSmaJLQKo1iyyww27pAw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12