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 - 936
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3707c33d-0301-4c72-8c13-ee685e8a0a88- logged_
at 2026-08-27T05:31:41.686260+00:00- previous_
hash 3c7be08d9352ae6487bf15690918c07da836055362c214a66fb8abf46bf0921e- payload_
hash feacc184501a998f2a1b1145423cf781157f93469cd02c4abbfc8b34d7d6ac2b- entry_
hash aa124403553a12f4134de14e023c06a9a1d04dd45764bd30594417225173a48a
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.683476Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3707c33d-0301-4c72-8c13-ee685e8a0a88",
"series_commitment": "f3cfb3b63e2a0fa8441f7a0a2042d95a141c036bc36f1fbd70933bd05dc5ecee",
"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
b38d9d28099917154d10b15ecb6d9e6a5639123a6cce61a3d238558882dc29b0- 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 - 936
- tree_
size - 2239
- leaf_
hash ea720c0e6f7adddc44156b6b001a7d7a5490fc2f22678286d5e6e274ec7da778- audit_
path (12) 0: f89bb6697942cf201b0eeb5924367eb4874b3bd890532c1e8ce8c252d34eb3b31: 1a0a1024858709da24ac15a1903f56bc83759dc5fac1e5254cbca407a79018882: e8529ace9987fbfdfefb789e4f38498c7a4726e1adcc283cac530533741cdd333: c9c8c362a7ecdccc19a7672ba4001073cf861c675ade239244909d0e3c7a3e0f4: 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