delphi.consensus.snapshot
Appended 23 Aug 2026, 05:32 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 - 673
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 48ef81cc-e8c7-4059-91e1-550a9ffc1391- logged_
at 2026-08-23T05:32:12.230691+00:00- previous_
hash d3f8f0c216dc84b463b2a8c82b7cc5b98937ae240c34f0a2b69527d172914f6d- payload_
hash 3990f4ab9f6119d625bee34d53bf93b17f02f256005703be6a5c7c147dc26e3f- entry_
hash 8c80cea2fd834a9c407990c5833cf8ea5690357e7fa22853de69fb967d3ae1c9
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-23T05:32:12.228332Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "48ef81cc-e8c7-4059-91e1-550a9ffc1391",
"series_commitment": "f6ff34d0a2e429e4b1e7d018f006087885afdf5266f8d0d3709579bc2b4b89c4",
"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
eeb4d62f760b6b3853e75362e96484f38cfaba64b10aa3c24d798ae0314f91af- 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 - 673
- tree_
size - 2239
- leaf_
hash 9e2038d5c860a1e58dafde49c368ebca1895479eebde4ca1221b25ebf0285823- audit_
path (12) 0: 6c45712ce2d4a068250a96cac10afea4b182db371d63a0a117d353c328f47d3a1: ab7b09f802fbacaa1c6d8c0ad5fecbf3a0d984bb781e522a55e8df29f8107c1f2: a38493ff0caad6f96674e4acd6824814225979a7fe5adc98e54addcfceaeb3743: f7f788a73bf873839c7d6aeb7c15a61615bafe04b7cb3e3e65fdeddf1a069a2a4: a4c2fb649f5e915bc7ba2775b0cf988a6756970f33d6fce0747ffa8da7c395d95: 2227b1e6f87ee00d0ed030cca3e6653e792b9214c57a30195159fc1d258a7ddd6: 4810b5c1f9344b5d296e3bee7c81348e090f31adadde16570bc3b8d3abb768f17: 9580dc2d498dc3b39d2b35bfb7dd13e8996199674c5dfe44e04c8ccc43e9c0d88: 1ed805746441fabcaa9e107f622f886b1692796b8a67f3eaf5f2122c01401d239: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: 9203a1600de814d3afb819f841569332c7e3b58c4d0e0ea56c377729f25dca49- root_
hash 03dd6fb33b4bd65222257eec0069956926795f14f7354795bcb42af5fe51ba08
The earliest published head that covers this entry
- tree_
size - 705
- signed at
- 23 Aug 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 4d18c6a52af8ef6fba64e938f1242a8d60e604e552526aae52071150eb66a202- signature
wJRAh51aHCkTsKK17vyEid6Up+l2HLMGcAnud6I240myQdRHSxzbQAOt1feLhwpcHeZI65DT1HKYBJyGn+cGCA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12