delphi.consensus.snapshot
Appended 26 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 - 864
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id fc61e6d4-5001-4db0-95d4-be60a131bd47- logged_
at 2026-08-26T05:31:21.299235+00:00- previous_
hash 0b5310b55f853fa9e7efc12e73919f09b697356a4740fca9fef4fba889cca495- payload_
hash 319d8e576380894c93114bab149f1804c59243b582ec609c2f555033044de76f- entry_
hash b7fb41dd332976fd10a23d4c5d620aae37cc6e0184fef164dc40f215f3505a52
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-26T05:31:21.293489Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "fc61e6d4-5001-4db0-95d4-be60a131bd47",
"series_commitment": "2d9af9c5c8c8e7ca4005e16bc64b665e3b3efe4616a0c9be8375dd5ecb0dad3e",
"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
3afe4c1f41fd470ce6c62c02b4e0347e257c697ff8fa898f56392fd74567ec89- 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 - 864
- tree_
size - 2285
- leaf_
hash dbed5216ee84b14bfd0405d75a014be6770c7668066723a9ed6a6712b9eb7a82- audit_
path (12) 0: b1472c6e7f80498e825c2a95b496e8db2d461793de231fb29040037e8cf6105e1: 57a8ca6087a6f226318381b4e733e925f4dcb7ebc191ba5f6b4e14bc6ae57d7c2: a0b0da0111861c1bba8713955f61e4f3f1f1821fda297f87cf450a3e0cd514a33: c7f7493207512f3616ae942f5f2e00afede3364bd7a86cfdc8e58f5dad8d99a34: 9d3b0fc7be061d6ac2084a548b4636fa59a79296e874df03c388ca8dc03100d55: 5b1ef59d9e2e8d37780772846782dd7ed8407159368e9e6247f6d4fc8bd287136: 4d2bb962b08e7d02e1409329aa3652b71103484fd25b8d3f56baa89c1b2c43407: bc6ace31149b3e9c1ba9d5f2b34ffb85a63422d9dcf2ebf241b2cac10329bca88: 184a24c3b623669a5fc418f1a01a448ab12c5b650e771370beaf16f761dd2e6c9: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: a95d574e00e9fefbc454b084e8cb19edc83831071366b2d8dc1af2f7114b646f- root_
hash 17330c6327e6363b8237bd4a68d5ee420a6d0f745c8d8bab0a90305d6bccba50
The earliest published head that covers this entry
- tree_
size - 891
- signed at
- 26 Aug 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 1b6242aee4572bc1cf018b1691811ecd6b368592cda0591cf6a4aeeddde5c07b- signature
Y/2YtRN8eDjfqUhrXHsTAsGI7CAljXh3GfV+XD3uVfaQMz3fIUak14+OLTbFm9tgH9HQdSJtHTtyD/roGWLnCg==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12