delphi.consensus.snapshot
Appended 27 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 - 928
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 08ea8d0c-fe07-4a30-a823-6e71109f1fb5- logged_
at 2026-08-27T05:31:41.628946+00:00- previous_
hash 58ad3a6ec39c05c3e98887ef0a1ebf3453b7cf0701d4b83c1440b15e198bef28- payload_
hash 54e1cc0eeecb51ce6a845c8496ed619f330f1a3aac9f46b1b64cd56f6973ab98- entry_
hash 48ca1ab9f791ab95dbee7894ad65d92df5de9877f17f1bba96e67b4397120717
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-27T05:31:41.625937Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "08ea8d0c-fe07-4a30-a823-6e71109f1fb5",
"series_commitment": "16e9086ec04f0c3b682017ba484e3765043f2e941bdc0c2a4d76c38d403d332b",
"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
376f1df7a03ea119324a9cac3628093aa0c82f5c2c2b79540f1406f200fd445d- 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 - 928
- tree_
size - 2239
- leaf_
hash 4dff1978171248211849d67fda0a40fc5b666a8d4b9c9658c396abcc8a9efe54- audit_
path (12) 0: 13c1c227f6b95d84c8a0d96708b92f1e7ecccf6afe698165313d291d16a2f82d1: 57ff8599b9f1b6641a94cdb6b049295daca77c0f8a4e99750d23679df45f2a822: 928f6e6bd6e7ee5363bc77866dd40976369cb47830cc82c73708ba27f55e36633: 509cf4811e748dc46ba1a53f678867b9772ce5e96414d7d13d85e057ef28d2b24: 4aeda3d843ef10be90d9659f518efeb4352e4f255b4919d31b8fe58f748367475: a4ff2459afb57ec6e04ab81c0944b7e45e77c02fa08b12d05f7c22eaad48ced76: 0b2df4116ce96d4c1fa68d027745d1dc76550ebc49d5cb7aa6fcb4e26ccf8f8d7: 9f20cfd56c132d1d00fe76cb2e482a3a9b4fbe96bc0d292d29ba8016ce161e9d8: 184a24c3b623669a5fc418f1a01a448ab12c5b650e771370beaf16f761dd2e6c9: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: 9203a1600de814d3afb819f841569332c7e3b58c4d0e0ea56c377729f25dca49- root_
hash 03dd6fb33b4bd65222257eec0069956926795f14f7354795bcb42af5fe51ba08
The earliest published head that covers this entry
- tree_
size - 953
- signed at
- 27 Aug 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 777b84e80ce59d38be10789755416a4f30978c344b4fac71e55a1730db98b7a2- signature
RuM+HDdwLwkwChNgs5UCcJZC9MkAJ3Wm0H42BkAdbOcleJjXbre134gogmmC+Veo5jcMHalx4/2FVClJdH0ADg==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12