delphi.consensus.snapshot
Appended 23 Aug 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 - 693
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 29f1e88a-b6de-480c-bc2f-f234c647455d- logged_
at 2026-08-23T05:32:12.388921+00:00- previous_
hash 26c53a82ee14206dc1f22c175204cb4a3062a81c00cfac0b7157e97e7a3524b3- payload_
hash 5d1c2563cba236f30d65e7de4193bce2b145ed4b6571d9ef390263950ea45c5f- entry_
hash 870bd1e9c2389431e0ff67feaebfebb042ef6f7a25a19e4bb79b243ebfbfc94b
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-23T05:32:12.385313Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "29f1e88a-b6de-480c-bc2f-f234c647455d",
"series_commitment": "4d03709e4ca41b542687d3ebfcf355495ca20fdebae3ebce746f19057114fc07",
"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
4e88b9d2ca24d308387d621604c317f9fd77924d266477b1cec3915864913016- 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 - 693
- tree_
size - 2491
- leaf_
hash f8a8b44dc98a4a03b86fa632e30b98ef84754b7397d46b524ac9844f57093659- audit_
path (12) 0: 7cc15645a4c2b70f6dcb88046c19e9f3e9b7ee3a16961b77d50516425552ae451: e645fedeadc82c69bad222f1e4c42048505a001e8132c4a80dc24cc7c4088dea2: 7d449d7a25d795f69392b847c78a6ede41884dffb31ababcd5655e9bcd1e76383: 52d0f369dda1a16f211bd7ae0496cd4b598b4c1eb89500aebd36eb2a093263fb4: fb49fd9d2272d5c20a7d64cf3e296707a11241bb487e4842b84ef1ff2deb929b5: 2227b1e6f87ee00d0ed030cca3e6653e792b9214c57a30195159fc1d258a7ddd6: 4810b5c1f9344b5d296e3bee7c81348e090f31adadde16570bc3b8d3abb768f17: 9580dc2d498dc3b39d2b35bfb7dd13e8996199674c5dfe44e04c8ccc43e9c0d88: 1ed805746441fabcaa9e107f622f886b1692796b8a67f3eaf5f2122c01401d239: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: 083d0806ed3c3d656f2d8c4762013d3fb4c0ed984cb03e95e8ae46936f2431df- root_
hash a9a1dac66ff7c8ec3d4b27b434ff70fbde5df3ef3dcd4b4fe4b41bb80f78a7c7
The earliest published head that covers this entry
- tree_
size - 705
- signed at
- 23 Aug 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 4d18c6a52af8ef6fba64e938f1242a8d60e604e552526aae52071150eb66a202- signature
wJRAh51aHCkTsKK17vyEid6Up+l2HLMGcAnud6I240myQdRHSxzbQAOt1feLhwpcHeZI65DT1HKYBJyGn+cGCA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12