delphi.consensus.snapshot
Appended 7 Oct 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 - 2381
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 4bfc7aa0-f12f-479c-ba06-d8e4cebfe625- logged_
at 2026-10-07T05:31:41.094996+00:00- previous_
hash 42ff0d15e2f05e6d940a655432ac20608a27b6456f94b561c9ff6355d1142cc5- payload_
hash 762760184f21bce7e76aacd90369ee38ce2373be78714450b4dfc1ccf1f03ceb- entry_
hash d5a97ee35a495441b0a2e8f479317c164cd840e959af916acc56bd8eb98c203d
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-10-07T05:31:41.086947Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "4bfc7aa0-f12f-479c-ba06-d8e4cebfe625",
"series_commitment": "952561f4237632f5bf6b499721cf1589a061aa8d70e8a468b07bc01271e84842",
"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
5c3c8a56bc151a52a6fc4d2d0efe433dda61ec294204c81529f8721f44d11bac- 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 - 2381
- tree_
size - 2479
- leaf_
hash 1bd8b2e51edd60ed027373c3e13c490d4620a7a9ad44315ebee9dc60bfb5a947- audit_
path (10) 0: b4be158bdc2b78e0ab4845fbc84ffa13a29c5f3215de9f117ad3b241572363f11: 6086326171ac1307f1326521ed726274dd36402d59577bac2e44f7c68a9db2d92: 42d317d009b9e1010b5818c7ea3887f7a64ef2b39d88819e1f18c857c426534c3: fc28f53df00f457fd3d4a8e811932af1b21bc3cf334215416193dcdc85459c254: f38b2eb220334d214d29a37edbab4195582a7000f288ed7ecc2ffb43ec2890bb5: 3e5c5766e4940cb7dda94351a5e27dfc8f706fef9342e7bf2324464ea61fae746: 834c6985c52ea8f25de55920638ea90cbddfd15c7f0b1819c969144787359e5b7: 99ee92a7962953bad0227dbe9ab05c66de08e3b0b7eb51768dee6e3fc62b3b558: 765303d6f29939e50694ecde6538ee53e894bb299166d5a65c9a000adbb546d99: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 2135d33fc3b42de9408df8505e145fcd175142e943af391ea41c56bc99a1e5e2
The earliest published head that covers this entry
- tree_
size - 2389
- signed at
- 7 Oct 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 4f7f1a3085d540e3b69ac022c801823029c04ad350f74966858670c2038ea3cd- signature
UvlhE38UEMJnByU4DF/P6uC9M52OV15VOwl/s2iGtS9adIxo97fOZi78iEbiFPZnaVezyW7TYC3vGMp7K4L4Aw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10