delphi.consensus.snapshot
Appended 11 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 - 1694
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id d1b83331-68f7-4be7-a625-f7824bccab5b- logged_
at 2026-09-11T05:32:21.330005+00:00- previous_
hash 7cbe3dc44ad3b713be02620f7c83d2592baf4097e120cc6218a8bff4974cf3a4- payload_
hash 49fde97a1d10445631f017e81ef7fa63dcd6036249c27b3abe4fa405bc6e008f- entry_
hash ce57a40da8d73ca426c0484b9befb891032eae01392e1207e46a81d077d2d31d
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-11T05:32:21.325079Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "d1b83331-68f7-4be7-a625-f7824bccab5b",
"series_commitment": "6ba4c41cd5dd72b204485718445bf860ae6fb57d6cab5ccfff778105ba3237d6",
"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
fd02a0e7430b828c5f678c22d8164e9ccbc50a05cd52485ef2952ab83d7096c1- 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 - 1694
- tree_
size - 2265
- leaf_
hash c52c4efe7519cb4010552bdc38909f8ef2a2a45790304d2d19d5dfa5ad4625a5- audit_
path (12) 0: 52e5ac1da265ab6a9261736a815d467edf2f01762d4b74d100fd0e15579effff1: 38cac52cf88aa5aaf6839dd15ea08d0d4ef44f804607722a4db8711780a190f62: fd9c67e1b0fb0bc69f72c131f075e42e23c158ce2bccf9b2b80e5c90057cc9ef3: a71166ec0bc591942b11c00947c6b0d0bfc23ecd77c6bbc01d6eff52642a75a84: 58ab6b571e4523ea252504b45981c61c96978b26cbb70e0525c1539b1b7ed8bb5: 8453c042861ef52e19b9d1a9a8f53516dd414e406f8674b7dfe3260c435b50cb6: 67d3a5f070d2cf8390b34d7293fad5757f74160be9bb198580c670e63fbcd4217: 89bbeb672caa03ccca78c3e7d709e14d72ed0f279c7cfcd435bb71dc863239c68: 49fbc719d10777c21e02e255a1174dbc47e89c67c7b327c5f50e8ea1ffbb5bad9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 15428b80842f9a0801cf7667918b216c9ce4186d9825e806ba86972b039c03f9- root_
hash 0feab2262fa1e39174e25fc17ea9383a6fe15fa5d22c96afd722849e59baa3f5
The earliest published head that covers this entry
- tree_
size - 1709
- signed at
- 11 Sept 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash e91d99cb0270fb7ceae4d325a6b43249f697d71664628e72786a644f95d469d9- signature
4AJfAwvJaixLHP+4bphw9Qkl4ZaR6Cir4TrRrdxqNt4vK+qmVVd8CVQh/FIRVoQ98A3JuRAAUq4ybP3nTHqwDQ==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12