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 - 555
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id a8c36f16-c0df-49f5-92d5-29bb1d0e58a9- logged_
at 2026-08-21T05:31:22.534174+00:00- previous_
hash 5ae649970b560e17bfcc9258e096775088a413fc3a1aabd7488c721dcc7b3f67- payload_
hash ee94f36ab6b251b6eba04f41ac8d8abd9927b270fa2e1ad63b8d34e4ceb1457c- entry_
hash 807c1f8a8bda9a571f7adef51af2c6440e897d3a739715700ad35e92c382c1e1
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.530597Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "a8c36f16-c0df-49f5-92d5-29bb1d0e58a9",
"series_commitment": "c9fa5b6b315ad4792fa629e9760b481e0abcbd4e6852ddde0fb33dcb378091e0",
"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
7b597d172439b0ab5c645b6eade8e95e64c6c2bed00adc260e2d13225fb4f9f3- 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 - 555
- tree_
size - 2503
- leaf_
hash 9f8412b04e43a4df2fe2c22fd48f0fd19671785331bbaca202068508f39b558f- audit_
path (12) 0: 1290b09f7ed36692f9a34dd5dcce8c121dfbf5b3348c22669cff25e6eec3cea81: d0dcd615612f9960b385db6819870a9233205980ce21a7a42077ad3b9e90c10a2: 89f870756b61ff7a3ac16fe3cdb2bac86e190b5d9a5def5485749fdeefe798713: ee2b6f2364f7643589f15e70d3aaa42cbe5a2bca44a506b7c7713efdc4bc49054: e27725d3590bb2ad73e24cfdf0380a53e07adb00883c808f7f8fc52c29f5ec7d5: 3be471921f1b62c05b789a823149dfa434dc5fec50c48c92bc65a486a54189546: d6b94aad0e8d194db67ebed505e85b9867726f564ac0997b7630c3317356f0f57: ca7fb7b440d51df69e12966994a041553b2c0acd85e1779b8e2fe8f79a1a4ab98: 1ed805746441fabcaa9e107f622f886b1692796b8a67f3eaf5f2122c01401d239: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: aa4b429c2497df4f846fe6b3e60223989226aaf0ba6013dc6f90c17afe986d9d- root_
hash c97f540ea605dcd0a8a4165044c60093cb885a8303800b87d215a424a4d5258d
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