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 - 537
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 0485b0c1-a674-414e-9778-a898c974bd9d- logged_
at 2026-08-21T05:31:22.373178+00:00- previous_
hash da774c7d2f3ff16dbd676c128f4955ec826b4731496e8c9db95a811f4bc5fe50- payload_
hash d0062cea6744f10123b7a1d1aaea849f4b386338e2b8f86c5e8b2d7422b53803- entry_
hash a79de63d00b6fc56fdacc29e5d63092290b9c97390edd51f197337ca3a01771c
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.370504Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "0485b0c1-a674-414e-9778-a898c974bd9d",
"series_commitment": "6a23426d7043eca8a234756a31250c959dc82f87b247f2840865511462c93318",
"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
bcbf6e7542338b8c83a9d94ceff926de8c796a80a5c012c897532c3475c70a6c- 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 - 537
- tree_
size - 2341
- leaf_
hash 229185a820d30b8bb89c819b776695840567d8893e2a1471cb083fd6b82913a0- audit_
path (12) 0: 9a8e47396f294960b84654cfd72caab8b585336889f73e2dfe50fa985379a8991: ad2fefd42d0d85aa698ada89d8f3174388260071e8aba0cb2651cbedc084581a2: 3aa448683a7bb89370e2e0215444ec9ffebb30fed87df6a2080ae978043137823: 7631e4e6e4e5dcd1ca06eb91d1a056143c5ecf63ad636f5b861406a02f8b03484: 6a906620a7fa4c9bd1172711aa8294807c7b438fd2ab3c24d4fbc8ea4b4723395: 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