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 - 1697
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id cd22f6a9-1eb7-4927-a2e9-6736a77b75cc- logged_
at 2026-09-11T05:32:21.354586+00:00- previous_
hash 53c25d6c7b42651edb3afade6fa13a61a83f84e12395a3d4683f993bdea0c97a- payload_
hash 54fc33d18eab2166bc818c9901a2c78edc3c7df566909bc90ae3f16c32bcbda8- entry_
hash da81cc412a5dc2111e0e89a113d59af30f54bdddd9dfbd744ddcd3322923b563
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.350796Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "cd22f6a9-1eb7-4927-a2e9-6736a77b75cc",
"series_commitment": "99fe5618cbe93c8319b73b3bec99c61a2bf72670a074640609ea3f49b17b9bcc",
"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
24b12f4f5e01a2c8e3e288c6b757175bb3782a040a7c2e505806afec89745f5b- 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 - 1697
- tree_
size - 2503
- leaf_
hash 7fb4ca419c6def638ea4fe810e4ff62d1372e8a83c73602f16b2ddb49ccf37df- audit_
path (12) 0: 71ea4d942e5e8aa9d6cf0a9cbfc96086c20d5d266b6cd7f187c1b0537e8c6f471: 5a6f4d30b5f752bdce98607cb70f0b39b51978391d2e57c6fa0f5d8641f57cd92: b505bf4d80ced12f32e1052c50973697f122882703f94f2cd475fca40df823243: aa8ec3c3ded0b9593c78e2c80c56f7746b547496f4af7b145b72d7c5431780944: 7150a8a2fe4eec9d4ceee6bd07ba0db3dc162e8f34c7fe3a067e2fe5913ae9ec5: b819eb725b33287e475b3b957c5805ae185bf7fbbfbf66638ca28dc7f0256cf56: 67d3a5f070d2cf8390b34d7293fad5757f74160be9bb198580c670e63fbcd4217: 89bbeb672caa03ccca78c3e7d709e14d72ed0f279c7cfcd435bb71dc863239c68: 49fbc719d10777c21e02e255a1174dbc47e89c67c7b327c5f50e8ea1ffbb5bad9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: aa4b429c2497df4f846fe6b3e60223989226aaf0ba6013dc6f90c17afe986d9d- root_
hash c97f540ea605dcd0a8a4165044c60093cb885a8303800b87d215a424a4d5258d
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