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 - 749
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id e732630b-b551-4965-92e6-7168c5a86d89- logged_
at 2026-08-24T05:31:21.382863+00:00- previous_
hash dde4cd767c1b178a9095cae7ef9f7f8d302c9dd6bd9248ace0ae04d113c758db- payload_
hash 2d51e15e68fff560df59082288979d9c75d7d80cca783218d2945ace99813b56- entry_
hash 6c5cca006bdc70f29ff34aebbf2874050e67b33c1ce73d3056042e82c731f96a
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.380213Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "e732630b-b551-4965-92e6-7168c5a86d89",
"series_commitment": "8ba78d8af217235b473258960da0e7598503ff498962f9b1f67d070b25837665",
"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
3e083fdbec860537793f377f7ddf6eb51d3acb809e223390bd7700eb38ce4a33- 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 - 749
- tree_
size - 2323
- leaf_
hash 3d4b2948ed045144a678c1344e927ee47f4afe2d6f7448f934e8e637baaa1f0f- audit_
path (12) 0: ff29904a8619082b4b539934c78d760aab9b5877c374d2f454ec561dc5373f211: a278337efb5a874ccbe47e1e84eb328ce07e3dd791eb0022af0d5170425a28cf2: 5767b19c469b23ca6af5de99541904da4f4f8d1b6d8c708306d4b8e2c5238e7b3: bb10e950f1c30d7e74acc875b2aa0ef591d9d2b48a910fd9efcdffc130c059ae4: 8335811e9c7fe8827b37303eaaa95d4a6488055638006b48e867a188b026e5385: f61c26919896eb83bd50507688cc1ccfc0bb60fc4cb57a63d694786e83bb71096: 973deb9be25f19e01b3343769d1f20b7f7bf6fe2638c57970f015700d2ee78897: 9580dc2d498dc3b39d2b35bfb7dd13e8996199674c5dfe44e04c8ccc43e9c0d88: 1ed805746441fabcaa9e107f622f886b1692796b8a67f3eaf5f2122c01401d239: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: c3259a319fb9b811eedac153ce91727bb54f7b550d8cceab957b75c3a0564058- root_
hash d5cdf3ada5e9d6ff6f86cc94c6a7cd9965df1cd86b6e68dd8030daf1fd3631be
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