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 - 876
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id d1b83331-68f7-4be7-a625-f7824bccab5b- logged_
at 2026-08-26T05:31:21.379071+00:00- previous_
hash 50d2b6a98fc78982479677b0f4e876ac0ca0b8da7bcd8cb7190f33477e873d79- payload_
hash c863e65e0176c501895bd49cafda86cd82487e3ca646b8c229d1fdb47e6a33b3- entry_
hash 3f6e7e2ec7a81ed1069eaa588bf58726d64a50c6202ea9e3905f0ca00e5670ef
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.375501Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "d1b83331-68f7-4be7-a625-f7824bccab5b",
"series_commitment": "60cc46795e21d10447e653f966ea711e427b81d7748523cc7cb0e97d1bec40f0",
"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
cc06c07c924160d516476b0e8efe704fc785a07c7ec944e45b060b3c96abf60d- 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 - 876
- tree_
size - 2265
- leaf_
hash bfd35602a5397b9ee5410f0b1e21d0b8ea1fe98d340aaeabb2731750ec549d59- audit_
path (12) 0: c45582281865732f6c7a05295817f6333054c9b61c79c31de81d3fac01f9e7db1: aa9eb5f964178d323df698e1e122746eb6a3cc799a39a058da1d4d41e98f43502: ab0b7f189fce72c19e88450efd8385dd697c6619b8c5e4bc3ac260ee493942083: 17f42e41d1825e52b0d1f223cc55151b535d51ec09e5a9fec5eeddeeb496a7504: 9d3b0fc7be061d6ac2084a548b4636fa59a79296e874df03c388ca8dc03100d55: 5b1ef59d9e2e8d37780772846782dd7ed8407159368e9e6247f6d4fc8bd287136: 4d2bb962b08e7d02e1409329aa3652b71103484fd25b8d3f56baa89c1b2c43407: bc6ace31149b3e9c1ba9d5f2b34ffb85a63422d9dcf2ebf241b2cac10329bca88: 184a24c3b623669a5fc418f1a01a448ab12c5b650e771370beaf16f761dd2e6c9: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: 15428b80842f9a0801cf7667918b216c9ce4186d9825e806ba86972b039c03f9- root_
hash 0feab2262fa1e39174e25fc17ea9383a6fe15fa5d22c96afd722849e59baa3f5
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