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 - 924
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id be56b97e-fbba-4073-8b29-04e6afa28138- logged_
at 2026-08-27T05:31:41.594666+00:00- previous_
hash b528cd9e1e67e99f3cc12af62ff2b7e2706eda6ca673ce7a19b4aa7d1432840a- payload_
hash 6974b95674e78a63b0b55ce48798b0aef331fba9839cee07034f9eb77876306b- entry_
hash f9126537d9e6861b8e3b103ab736d91b3f95926ffded295543034db745001580
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.591012Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "be56b97e-fbba-4073-8b29-04e6afa28138",
"series_commitment": "dca283f6ae51ed0eba3321f871451e1d8691106ed5844941abfc3d1fbb7f2723",
"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
f95e20db243b3527824032886a02cf7d4547ad842814214c0a2bf0a74849a4c6- 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 - 924
- tree_
size - 2239
- leaf_
hash f7e05be19e53b9ced13ea8574194bc02f53f69f405aad8e1749bc2f00945271c- audit_
path (12) 0: e7d8894c1c1309e3d2b6cb537c2d3cb26b5f88338dcdb8342ea7845a84fc141b1: c58d751f48349d11f801c286b7a5383012825fc0008b59cfded065852eb772fc2: a42c269ed87e3aa8f405310b538bb888f107b0fe5f91666f1e35c9db1642070a3: 2bdaa1a51ce1993395f846a80fbfdf0ab69533ff17e4b240dc953b208f1605254: de56fbc4af91f856b64481e0d71aeaade8792bcbcf18d89b9d8a18cced0d58ea5: 99bff9bbae4f32bf8db82e931bb3407e647ddb95798066fdf9855c6f9ef036ce6: 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