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 - 922
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 4e06eb7d-ce53-4631-86d8-403a4f841a49- logged_
at 2026-08-27T05:31:41.573638+00:00- previous_
hash 3e2973c00a7b58f679a557ccc0fd1c99531f9e5422761ee0f208df5f19071320- payload_
hash 9117b2e93ff65cb4a370907a6f0e02633970f48ad453f881ace1e1a11167b21a- entry_
hash 4c6915c6f05124cf64301097c9600a1bafb9fe1b59641f8036c5a77cce42f7fa
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.565902Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "4e06eb7d-ce53-4631-86d8-403a4f841a49",
"series_commitment": "14ddb2cbe257fcd6eeb8e9b4f2bb312a5dbf60a54bc938d07b36266d788fc86a",
"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
943c393b1e243396863a525dfb75e89aa1518435929191fc579c7e56235c35b1- 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 - 922
- tree_
size - 2239
- leaf_
hash b29387a7bb00962223724c53ec2b7d21c0c587c31c789ea6a7e8698ab49c8c9e- audit_
path (12) 0: 34c746775596c0db958af3ffc70d80fef1604704f33cd597a9abdd369e581ef81: c50d9f954e1800f9739322faf1b071b02fd182b0610294b671212bc7c78279b52: 73c5aae7a5efc8338c55e979d8892f42de90d4ccb34b8169bfb4e60c4756cc003: 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