delphi.consensus.snapshot
Appended 26 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 - 883
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 4bfc7aa0-f12f-479c-ba06-d8e4cebfe625- logged_
at 2026-08-26T05:31:21.424592+00:00- previous_
hash d1b4f9b08dfb07fb33052acdb0fda41e1bae258c8687c1d9cb5bf95a6f81b55c- payload_
hash fb987206bc7e0050ce7f557799c4fae80ba2257cc1cc09ee78bdb1deae004623- entry_
hash 1752cd775c7fabb4bb2763baa061f4901acbaf81903363ea8cf2d1e87564fa93
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-26T05:31:21.422229Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "4bfc7aa0-f12f-479c-ba06-d8e4cebfe625",
"series_commitment": "1385c2c0f115b216b491078c4f4f881a766dbac7a348fc00cde7e5d4dda73c48",
"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
45dd77b89836cecc6c26e514e890414327bfd841e3f4b741ada7dc8b55bebb2b- 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 - 883
- tree_
size - 2491
- leaf_
hash 888504e800e44ee45a772de0b19533f4ec17de1d868d46b207c7f3d373ef213b- audit_
path (12) 0: 2e3e9d9e38182fc3b0f72f81ff3442142ced47bde9e52ee351988c8dbfdbe7661: 3a59c8c0500338a32229456e12a4099bfc6dda1c40b969a1963a20f71bb54d312: 12b39f286c3036d0e9e76ee0dd13ad1e5e44c3797c1374f725f1e8c9b77da9753: a9e4e0861ce0014560dc9e2f43f42bfcd1c10f21c1a807889a7d75f9661e64ff4: 77bfdc0443b4d73d782ce99c0c2aec8e8d9dc695ab1435aa46dbb4d09a0d4eff5: 5b1ef59d9e2e8d37780772846782dd7ed8407159368e9e6247f6d4fc8bd287136: 4d2bb962b08e7d02e1409329aa3652b71103484fd25b8d3f56baa89c1b2c43407: bc6ace31149b3e9c1ba9d5f2b34ffb85a63422d9dcf2ebf241b2cac10329bca88: 184a24c3b623669a5fc418f1a01a448ab12c5b650e771370beaf16f761dd2e6c9: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: 083d0806ed3c3d656f2d8c4762013d3fb4c0ed984cb03e95e8ae46936f2431df- root_
hash a9a1dac66ff7c8ec3d4b27b434ff70fbde5df3ef3dcd4b4fe4b41bb80f78a7c7
The earliest published head that covers this entry
- tree_
size - 891
- signed at
- 26 Aug 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 1b6242aee4572bc1cf018b1691811ecd6b368592cda0591cf6a4aeeddde5c07b- signature
Y/2YtRN8eDjfqUhrXHsTAsGI7CAljXh3GfV+XD3uVfaQMz3fIUak14+OLTbFm9tgH9HQdSJtHTtyD/roGWLnCg==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12