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 - 548
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 04bc3a9c-76fe-4aad-90b1-e3640e548e9c- logged_
at 2026-08-21T05:31:22.472689+00:00- previous_
hash 15ca916cf9ef51407c79c41898ca6f2f43f0fc762c157228bbece3b89d301919- payload_
hash 40b6bbd6081be4122cead5e2d04a3e3c61d7da1d5b06698b9602eeaa97459fd6- entry_
hash ce7af919beeada3f97001612d71bea635fcdfdb6849c38c912b0d652b0255f2b
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.469938Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "04bc3a9c-76fe-4aad-90b1-e3640e548e9c",
"series_commitment": "8313a59c2856a1b04e586faaf3fb453294daf8b0ae2c2579c5559747877be42a",
"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
d4501a38d461168ddb53b89c5e1e133b3a6e5de5602afd731ef22b95914250a0- 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 - 548
- tree_
size - 2285
- leaf_
hash 27305d4d7cbb29479ea4582bd22e17bd792b0e64639e1426535eff81dedbd765- audit_
path (12) 0: a3b461e5b7f35cb213ad4baea6d285472603ce80b37417abc6fbd5f9eb74c77e1: 58a57d9e6703dd8adc1722f3df487ef7ca4f7636d357b94e17414086501541ab2: 8ef7d35067c3cc441580e159b945b26f7d9d32ff5ea4fbfaf70670b2816ca6a43: 2e50e3cf6a89670a37738a538227bf47698de811db24b3f6eb62727ef5b0d2c14: e27725d3590bb2ad73e24cfdf0380a53e07adb00883c808f7f8fc52c29f5ec7d5: 3be471921f1b62c05b789a823149dfa434dc5fec50c48c92bc65a486a54189546: d6b94aad0e8d194db67ebed505e85b9867726f564ac0997b7630c3317356f0f57: ca7fb7b440d51df69e12966994a041553b2c0acd85e1779b8e2fe8f79a1a4ab98: 1ed805746441fabcaa9e107f622f886b1692796b8a67f3eaf5f2122c01401d239: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: a95d574e00e9fefbc454b084e8cb19edc83831071366b2d8dc1af2f7114b646f- root_
hash 17330c6327e6363b8237bd4a68d5ee420a6d0f745c8d8bab0a90305d6bccba50
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