delphi.consensus.snapshot
Appended 24 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 - 745
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3d483c76-6358-495f-9f25-5cbef90fc78d- logged_
at 2026-08-24T05:31:21.358474+00:00- previous_
hash cee65fdc1b8adb6d950b630d95c7c39b33412f9c2123b75be3e8d7c35c6f52da- payload_
hash 46be593b8d567769cb7454cfa1e97054e686c2dff277858fb0d2fb5671dff06f- entry_
hash 34b8f161a758d674a032edb10d7328d8138c0145c94b9e6b7cb9eb6a6be7f57f
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-24T05:31:21.355919Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3d483c76-6358-495f-9f25-5cbef90fc78d",
"series_commitment": "ac6107f4d828fa703f5501c881b9e761af48a7f1afadba6515ae76303d195bc1",
"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
1a7aae1c191b237a1ec7f346a3e234b0885bb1ce78e8b2cb86fc023e19db330b- 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 - 745
- tree_
size - 2305
- leaf_
hash 570166a17ba7628df3ac3cba81feb54fa76f5779b02f14734cb5978bd7063baf- audit_
path (12) 0: c52f093227ff92410db3b8b183263b080ea054387d8c31a8a24fbee286cf9ae21: 207de952642a5f9a342c596aa484b5b615e74d835a2568efac9759e620c2c7eb2: 3f28f911d26042f85acc2c0cfe97851b585fb2c99d090fcaf186ab1216f510933: bb10e950f1c30d7e74acc875b2aa0ef591d9d2b48a910fd9efcdffc130c059ae4: 8335811e9c7fe8827b37303eaaa95d4a6488055638006b48e867a188b026e5385: f61c26919896eb83bd50507688cc1ccfc0bb60fc4cb57a63d694786e83bb71096: 973deb9be25f19e01b3343769d1f20b7f7bf6fe2638c57970f015700d2ee78897: 9580dc2d498dc3b39d2b35bfb7dd13e8996199674c5dfe44e04c8ccc43e9c0d88: 1ed805746441fabcaa9e107f622f886b1692796b8a67f3eaf5f2122c01401d239: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: 4ed47b3cf2c766bbf573b761e9026e21f264edbbd6420d65b1efd886894c770c- root_
hash 9259657b60d7c54c7f061a7a621bf2f8747cab0885ee335ac1ed3b6657c9740d
The earliest published head that covers this entry
- tree_
size - 767
- signed at
- 24 Aug 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash a28d9edb9694f1cda2f626078fae254accc380b4f2549aa7194ad4e4bd63a67a- signature
JMkjMTErBa2bqo2Rs6CcdmWk6Ehro+QvUn6ngPbf4o9ZZnLXtGSJxijgC+C0p5sEaXG37JHg4YRCxAbtVD1mCw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12