delphi.consensus.snapshot
Appended 10 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 - 1653
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 24c5a768-70af-4997-afe5-05e9edc2e4a7- logged_
at 2026-09-10T05:30:41.057572+00:00- previous_
hash 8743f63de12de91247a8e9df83156459716c18e1326b6a9898e68817273f456d- payload_
hash 1c587b70f6a8e7c1d82f5ea4deaea8c35f2fed4f22c95d9642ed5f0f82da7e1e- entry_
hash fe3f485ffefbf91ae6e0fafdada55df4de1eca12f375aeca4228736e1bb8e87b
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-10T05:30:41.053575Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "24c5a768-70af-4997-afe5-05e9edc2e4a7",
"series_commitment": "2eae0ca25251135515011a3e8e66c05714b7a964d3ee0852369250e43f73c31d",
"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
142a2af46559ac8b2560b4d3a83c36f8125d610fcf944373948a6c2954e052b3- 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 - 1653
- tree_
size - 2239
- leaf_
hash b20366df2781c8cecb7fe4fd1ce496eb41a630529a5f98f5a8054e09c4cd0871- audit_
path (12) 0: 761c69b6ef8ddbedc3784b774d68d7646f3e86c11e47fe74c6ee21991b0418521: f8ff9b364280a1aed6dec480a723124fe1dc22a10c03f9bfe95edf7c4874f0172: 6e9866438437fc18da83c6f84e8d48e0d802bf0762732fd7250734dcb01fe4223: 5fa484a0fc2acc1d3a864f3a4ff30f37014723dd710355f60cadafa942770bc04: 3e3b5e32b4d43ed48e4b662c8baf5aa348a5a0701fb48ccec5fa81ff8dd1d49a5: 68134fb504110907cd6ea503e3b9ad00d7f4eeee8e5c017e134a0023f49e1d2b6: 00d36260786b8ce290bee853db49e73fdd5d2800eb992fa1e6e2b98e2e9d62487: f4a858c5afd6d2bbfe79825cc00005d2e5bc4cb6a3723b70509ff06cb4f713008: 49fbc719d10777c21e02e255a1174dbc47e89c67c7b327c5f50e8ea1ffbb5bad9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 9203a1600de814d3afb819f841569332c7e3b58c4d0e0ea56c377729f25dca49- root_
hash 03dd6fb33b4bd65222257eec0069956926795f14f7354795bcb42af5fe51ba08
The earliest published head that covers this entry
- tree_
size - 1669
- signed at
- 10 Sept 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 523070ab7c9144911686b260582d7847bb9af7cd001319dcd81f849fddf5ca28- signature
tlF26vhUzkZ1g6+zQtD/Vl7F+8URBvYLFh6zLzoV9MBBJJwMGhXJhrE3GhWFFjxrBmxlZH/66rXkfK9tIDB4Dw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12