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 - 552
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 29f1e88a-b6de-480c-bc2f-f234c647455d- logged_
at 2026-08-21T05:31:22.503467+00:00- previous_
hash dc97c052a566a770e5e66e1496fc62e3e4d3a7e4d089a69e3b2f6b7f401b569b- payload_
hash c13886e3491dddab028adc9b9dc1886d9f36ce525b8059afd012094f12f6570d- entry_
hash 16dd85613fee519330a093625943509d54b10b7cdcbf25a3440f0598a71f0c5e
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.500188Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "29f1e88a-b6de-480c-bc2f-f234c647455d",
"series_commitment": "6b09167ad8de2798a509cbaed2bb92e883900aa1796022aefe82da436f581849",
"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
34dd0b3ace3f834f17c7fc2da6251fdbb9387df9a989f64a186b5587d9e25432- 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 - 552
- tree_
size - 2503
- leaf_
hash 91745948ff6c157a3479de43a0cb7ae9857bb36434037ebf8ab1adf61f9f21cc- audit_
path (12) 0: d1ed52c825b40ef0896e5951437545256e6cdf14e6a57675eef7377a6a0308271: f198291c12b7c153ccdfb55dc6e8856533f562de1afcc6739dbd194e82fd452e2: 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