delphi.consensus.snapshot
Appended 21 Aug 2026, 05:31 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 - 527
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id b6f50ed5-05a7-40ca-90e0-588fcc89df0b- logged_
at 2026-08-21T05:31:22.281769+00:00- previous_
hash 44d85d9702009be24aec5f81b5a953cd80af0bf4a6a9f4d48d4a2a3627d91751- payload_
hash cd6934a4cd40e7846e1fee0f1a7488744d43bd8c551e63996dd0480f2f2cdf39- entry_
hash cc740b25ce920c2a67fc9350af121345f73d826aeade6edabc2c4852b848f6fc
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-21T05:31:22.275156Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "b6f50ed5-05a7-40ca-90e0-588fcc89df0b",
"series_commitment": "d4018d197907565f3377f05f7b5b7e59e00fd03ab0ba58cdbdb9d41bb5ee57da",
"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
6bf4383cb914d9a626b704475f14de4d51d3fd991c1faa6512524e0bb5dca53f- 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 - 527
- tree_
size - 2341
- leaf_
hash fe090fe2ab408ec27c8cc7d72ec452f3a75c4846f3a460b959370ede5171fae1- audit_
path (12) 0: 85e05a3f86afe723f0ac190aab20a50f5aca500dfd74ba61cceeab203148681e1: 01a24479ac40642f5a59651040145fe09920baea8bd76e3185d4320de5e363702: 292b5b03bee19fb262cdd17db145b91d826fbd42555f4e9b4d093bc0588838a53: 0450eb02b2a8859ef7e232e55d4c8adcc0c9a5c74b4038bd5956da60b5a3bc474: 40a60fba891cae6b386c086033836f2fd08c736a131803fc8e8fed062fc33a9b5: 514fcd08b7a7708fc978766c3847337cf0929a642e3c50313cc548d93fde1c186: d6b94aad0e8d194db67ebed505e85b9867726f564ac0997b7630c3317356f0f57: ca7fb7b440d51df69e12966994a041553b2c0acd85e1779b8e2fe8f79a1a4ab98: 1ed805746441fabcaa9e107f622f886b1692796b8a67f3eaf5f2122c01401d239: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: bd18df2de60e205be411a53ea96887ec76f5a16c15250bf48e3f90dc788abbaf- root_
hash 9f32e37b52a81f4fc0f11a1b956464ef6acde09c58b0ce26dc44277199cb7df0
The earliest published head that covers this entry
- tree_
size - 562
- signed at
- 21 Aug 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 92c30356f864326ea5b77d1d568b8dd46798aa892ea36caafd50798e4442e809- signature
5gjvyMQAKCKkrfKE4aMmyLNO4EIVZGCpS3rtcSxEUacSoDSKoR/3VznuFflGgZKKdSSKpTgTy1ZrFKWVK6BiBQ==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12