delphi.consensus.snapshot
Appended 4 Sept 2026, 05:30 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 - 1375
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3d483c76-6358-495f-9f25-5cbef90fc78d- logged_
at 2026-09-04T05:30:40.411629+00:00- previous_
hash 15df375374d30abb33149ba00a4d17d09321f967b5001f840c4055e42eb449f1- payload_
hash 27b05b67393a975eaba4237fbe1535c86bdb78f46b0241bfdfd874a2d4f4b340- entry_
hash da96b69b9261e47894335f7d7a49a93b7c80160fb1136ae68908498080989241
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-04T05:30:40.407517Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3d483c76-6358-495f-9f25-5cbef90fc78d",
"series_commitment": "34269a166b35f4ba68f9f9b89bf0c56a890e3b3e21cd212e62b16c8ec4ee3443",
"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
e92c5c96548c0d13df9947e31fcf3f0aaf067f5612100f7c9e0f41c210859d8f- 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 - 1375
- tree_
size - 2357
- leaf_
hash beda102fd7fc6348492f19ae387ecdce895370b6c1653a054dc91e65b04f5d2f- audit_
path (12) 0: 88571dda1c6f647b40a143ef60b29c5ce2362150941c7573f88e42eff2f955531: 369d664ee7d1678e7eef429f94219781dcb096b103d5edf007c15bcf8d2327c42: e5ac4da62bd3be9e62b1627e5de95d45cc1e99bcac7379e9077ad5eea01eb1dc3: 5aa0f2ad405e65e2714c921cb6a23af7ddb9e32bc11b6da206be9ce5540d56494: 25c062b992e8b376fe1970e5b2db0971ae78cbaa6bfc93de4703ea6207967ee85: c3facadbf527f8c700665ab7a62b70a42fd75526b21c5de879363bf38c06f8726: 3347dae74325660c6b1e768277c0a7f2169b7554b58c0815e1d6311ce75bfca77: 00aa16d00eabe2b61089fea4a6c3044cf3b1ced9f2af168276f93e239a98dae48: 73b80563a47162cfa99809097caf5d77512af3a28ebfbf76c6bcfd5f572cc1d29: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 2f361a0c4a49843181536f3a7baa572ba4bc0573be4bb8272112c3d056aa1031- root_
hash 58c8c5ab99dba36e8c6b398578e37592253a716c9cf756f72e78b6606a198d59
The earliest published head that covers this entry
- tree_
size - 1397
- signed at
- 4 Sept 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash dcdf356cdf9dc7ebf6b15487b75fbf56f1dd13b64c18428b5b1c3def4a10dd7a- signature
3byga8XRhlKNr2NA4ABo68hmWG9n+zteILiR72i24nQlgkl2AHzxfRM3GAGCw7aUDx0eN916Oq0zGWs0D7mPDA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12