delphi.consensus.snapshot
Appended 12 Sept 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 - 1741
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 4bfc7aa0-f12f-479c-ba06-d8e4cebfe625- logged_
at 2026-09-12T05:32:20.922679+00:00- previous_
hash 521522cc6abfd3495dc606f2d1bfe97db34467d259a80b90963b1868ef7d0d62- payload_
hash 909a1be73662b8e072ad864e5b03777ab3b519c87058d0c2d197483f5468fab5- entry_
hash ad64144d135aeff62e60ec1e345993aa78724d823b9ca3769e8b0fb9d7074d18
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-12T05:32:20.919297Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "4bfc7aa0-f12f-479c-ba06-d8e4cebfe625",
"series_commitment": "bab8b78c5fceda06554d21ad058c47d7da7cb9a41993e6050eacb80e302063c0",
"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
4e9a85238a43c6f3f718944c3c51f8330146469c68be135073ef5a8de2df4071- 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 - 1741
- tree_
size - 2491
- leaf_
hash 6f736c42b6433dfdb4bf1fb145d140e6831643d6ab339d134a82cdc67c7d607d- audit_
path (12) 0: 2bddc501168ae39501b7bbc95c1cc8adc8a785654523a0fea7c02085786ed4cc1: 9be536d15db50fd930977fc68113178a9ea8df992784f678a4261fb7e83d97902: 7ceb1182f31279c25c1429ed9e9aeb2b7fe602377f49ac63d25334ccd8a8aafe3: 635aae6193961455327075b2fe16ff662110a049f19d8f0882cf12b56058acb74: 0c9bd5c162fc6aaf5d9bf93b62d6c7267bc3226cfca9518555e4803f850180b65: fd82ea2957dec252aaf0f497194cc97cb06fa6fdc01911c77e1a2e46ff4eaa336: ac160a0852932e7e1298c12b7bbeac8a979011b4c86d850294a53e9c58329b547: 89bbeb672caa03ccca78c3e7d709e14d72ed0f279c7cfcd435bb71dc863239c68: 49fbc719d10777c21e02e255a1174dbc47e89c67c7b327c5f50e8ea1ffbb5bad9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 083d0806ed3c3d656f2d8c4762013d3fb4c0ed984cb03e95e8ae46936f2431df- root_
hash a9a1dac66ff7c8ec3d4b27b434ff70fbde5df3ef3dcd4b4fe4b41bb80f78a7c7
The earliest published head that covers this entry
- tree_
size - 1749
- signed at
- 12 Sept 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash e8cba9a99f4a57e7aaabf2bd0c850bb0715afb51953cf8fcda65ca036a6c608e- signature
cNlPz9oqpkHabbJeJhuOvJLMF32ooelAhyWb8yHCQmsqZM9LEZ0petdc0dMGAZbz5avsJ6pUSC4TluX7fEBpAw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12