delphi.consensus.snapshot
Appended 27 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 - 941
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3b1bf8d0-fa87-4392-b4cf-333e6cba3622- logged_
at 2026-08-27T05:31:41.716554+00:00- previous_
hash fb5a1381ca4750180833b71b7698ed3501f3b966516c6c6ad53eca31c53e7aa0- payload_
hash eb18db7cd77f70e79e0e2205730ffab7e99e2ee1fc7c628e2b5447d074119795- entry_
hash df69215b4d5cc7ea762bf29698dd281f43bfd2f903a4cdf6a13e7278349bb223
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-27T05:31:41.714226Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3b1bf8d0-fa87-4392-b4cf-333e6cba3622",
"series_commitment": "26b795bcd0c3672f061b40f4389f7d417da31a4a67cd4902a8d64f7dfda2d2ff",
"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
e9f6156746580eb805aca4f534abf739decd968f05955b435e6caf49d79a2f61- 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 - 941
- tree_
size - 2479
- leaf_
hash 961092df1f813d84567c0e1ff6b2ae8a92e347ba675d03bcaea6642ec2c36197- audit_
path (12) 0: 310332eeecf4e1c0cf16248c18b8f6bbf67e80d64439ab4ac90e945ae51609d91: f1192e1d9bc73e35223b94bdb0f14c00431d02cf684380dc0f41e94de62672852: a237d08b82fe1c53ba46c32bce20c6d9cb76f0d75a8043afaf04bb7aee84ea5c3: c9c8c362a7ecdccc19a7672ba4001073cf861c675ade239244909d0e3c7a3e0f4: 4aeda3d843ef10be90d9659f518efeb4352e4f255b4919d31b8fe58f748367475: a4ff2459afb57ec6e04ab81c0944b7e45e77c02fa08b12d05f7c22eaad48ced76: 0b2df4116ce96d4c1fa68d027745d1dc76550ebc49d5cb7aa6fcb4e26ccf8f8d7: 9f20cfd56c132d1d00fe76cb2e482a3a9b4fbe96bc0d292d29ba8016ce161e9d8: 184a24c3b623669a5fc418f1a01a448ab12c5b650e771370beaf16f761dd2e6c9: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: 8d949d6aef53b2e3322ef5e232755263eaea63b886b405d936c87ac0c842b6a1- root_
hash 2135d33fc3b42de9408df8505e145fcd175142e943af391ea41c56bc99a1e5e2
The earliest published head that covers this entry
- tree_
size - 953
- signed at
- 27 Aug 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 777b84e80ce59d38be10789755416a4f30978c344b4fac71e55a1730db98b7a2- signature
RuM+HDdwLwkwChNgs5UCcJZC9MkAJ3Wm0H42BkAdbOcleJjXbre134gogmmC+Veo5jcMHalx4/2FVClJdH0ADg==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12