delphi.consensus.snapshot
Appended 17 Sept 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 - 1914
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id a8c36f16-c0df-49f5-92d5-29bb1d0e58a9- logged_
at 2026-09-17T05:31:41.709783+00:00- previous_
hash 91bca19b78b2937f1dfaeb9fa8042cf6235e4088a12306f8904b411f3c70a420- payload_
hash 8105b58369cf76a77bbe5460618407b28816b56f23e6f7dcced8e53a8087289a- entry_
hash 6fd1b5ad771e17d75a1b1554f4dff3fb76c1104fca31ec9ced9e412cd828da82
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-17T05:31:41.706246Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "a8c36f16-c0df-49f5-92d5-29bb1d0e58a9",
"series_commitment": "bd8cf98b7b66cfd390b70395d4df99caa8d60790145e809ab87b811a3976204d",
"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
fb839bf4a8eb2186a204219393eae3fdc2e77fc2f778274df966383df5bfff5c- 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 - 1914
- tree_
size - 2515
- leaf_
hash 5775bd47d37741c5b49f71210001b2de5d30bfa703d45f4db1465be69606debc- audit_
path (12) 0: 705d1c476ca1dc19a1d0fd123370f28d7de6d260bf70556cb17c6443c3b802281: ff875c3523dde941936e7cead27e4137803522f2adb2c3a77a18621854c9fc6b2: 31171b76fa3a7e2d2634981db718d3e24ce8c3097a15c67fed3df4e855f551863: 7dac6c581b798949c69306005e2f5d924d733f853a6c9a00fd6412f85ad03ac04: cc6b75f197277762b6837a9f28956ddb80000209e849f7395b445025b8a73d975: 8163d9522cee5c395b431cb6244dc9be07640c46717beda36e36f07660c958786: e58805ff3adab5c7bd3bd83274fc881f7ac4f076b0dd834beda95d34af7800d77: 250a7c52b8fa3c4932ca872a3a7842e2fb00579ab86c9b5fb8782329fdedf9fc8: 5ab1df6751f0dac25a6ce29d97587d6e08dcdd2d94987223ead725483527e08e9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 07e77d0b86e68e9f9b9a10013a0034c87fc2ef91312163906ab27730e4a116c8- root_
hash 94ed3e67e0f3ca6ab90e872a7f03020d191548311e8610028e47ddc18fbfbf90
The earliest published head that covers this entry
- tree_
size - 1921
- signed at
- 17 Sept 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash de4645b3ae57c2a319bdaadccc8424330c3686a79d031b007b80eca0ed78c863- signature
XoarI5Mzcez/Mayoy5WfSvWoXgXCDcdhQdMw2EQ2bH4TFS2FfvvlUkHv+csOCREKJBJN95gFWB6udc2z582ZCw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12