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 - 868
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 28453d7d-6676-414d-a36b-2fcf2cf13265- logged_
at 2026-08-26T05:31:21.327924+00:00- previous_
hash 847780312bd15c3e8fa53a0fa969c2c07f8e307cb32a99d2f33959ef85f5c4d3- payload_
hash 3b020d5e6a957e3681b1d4f161e72de2334e4d0b3bce57c11805710dfa28879f- entry_
hash 712df5ed09dd477cd55c272d0faf13e131afaeeff14d73634440259fd0062370
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.324731Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "28453d7d-6676-414d-a36b-2fcf2cf13265",
"series_commitment": "585e5e6588679e499251632df02726ffcb1bd6559476d709e4316f17106e7dd7",
"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
ae21a895c286f0b9fdd18c06c00de119c83baffbd658a0bf54d07bcf3e387400- 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 - 868
- tree_
size - 2265
- leaf_
hash 5876b90f983a43e2480c911fd22446e04d09bd37f2be9a47d54612e9b0e750ab- audit_
path (12) 0: fb64461cf1c149f0dea56e83f92336db9ceed7509224f1e36eb12de92b628a7f1: 1a5726f62bd7b20834adaa0961970e1ee052e95c9e15333d7acdf40b8e3213b12: e7663d1057a8b1494fb08b6dc00cb2c60ee2d795c87a6b018d5f2d60fa2e62b13: c7f7493207512f3616ae942f5f2e00afede3364bd7a86cfdc8e58f5dad8d99a34: 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