delphi.consensus.snapshot
Appended 14 Sept 2026, 05:32 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 - 1810
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id eb8beb52-14b3-4956-b29e-909a936abbc4- logged_
at 2026-09-14T05:32:20.068528+00:00- previous_
hash 23ba47177cc37268655bacdb3acccfa5a511e624d5b6d08dbc45f946c325bcf2- payload_
hash fa67a1de8702c3da8690bbba36cd158e014817fc389fcc09dfd6bd8876b11b76- entry_
hash 7aec5d75a07c283e0bd1711e00d2905966151a3656782c39df30351a2f495995
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-14T05:32:20.064266Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "eb8beb52-14b3-4956-b29e-909a936abbc4",
"series_commitment": "2a3be4df418b351889f2a74f3d990908873006ed21238b946865b46ef31bbc69",
"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
a32154a720a8d011956e627101a73076cb7d40785a336b713883b71d5a2ab9ee- 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 - 1810
- tree_
size - 2265
- leaf_
hash f7c9b89222663aceea0637fd9c64d1c8bdabd73aed5d1383b5d4ba257fb97cc5- audit_
path (12) 0: 06023a2313431babaa68e22c2e46bdf3383727de624245bfdc513c500f70a2831: b09092ea1e315b6522a726d816ed645421e479c4ae9f6ebbf85d0cdaa70976ed2: b17b2214978d531da9a1f6801a937563669990437b1fc8efc5c684c6b3347d163: 66ff171c7d092ba1daae4586ca5cede959d23aaf3c4c93a2d0d5e93c28f017d84: 910ebb775e841c1de5206f3757643ca7d376ad37a8e3efed1b2f1d57a8b5e2085: 35e93264a628694567ffa81b9f6b6754295524d7648668627e7e79e320561d416: 66e877548a61fd36a62ff399c81b1533c5b6efa4d42185e861a4558efb824d297: 250a7c52b8fa3c4932ca872a3a7842e2fb00579ab86c9b5fb8782329fdedf9fc8: 5ab1df6751f0dac25a6ce29d97587d6e08dcdd2d94987223ead725483527e08e9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 15428b80842f9a0801cf7667918b216c9ce4186d9825e806ba86972b039c03f9- root_
hash 0feab2262fa1e39174e25fc17ea9383a6fe15fa5d22c96afd722849e59baa3f5
The earliest published head that covers this entry
- tree_
size - 1827
- signed at
- 14 Sept 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 6e05cf324ce30b70ee7ce89eee15228fde23a83f821f9ba8523ebaf1d8fefc5d- signature
uMGbdZogepiib7kJvGrMkp166pSNlL4XyQglenQ+IL0wzHUIeA4uonjnlmZa4EixtTu6l4fAF5nBpky7UwM9BQ==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12