delphi.consensus.snapshot
Appended 8 Sept 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 - 1570
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id d1b83331-68f7-4be7-a625-f7824bccab5b- logged_
at 2026-09-08T05:31:41.895740+00:00- previous_
hash 599dea3d4bd0398f386f9e06c910aa4b406c4c2c13da290c0b91d3b407637dba- payload_
hash 42718db3d6f7b4cbf698d73c4775a1778bfbea3e07e268735e51bf8916da3657- entry_
hash 5ba1c53141390cfc209e59f0c08909ba170f41f892155e63b7929cf66d6f56f7
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-08T05:31:41.892766Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "d1b83331-68f7-4be7-a625-f7824bccab5b",
"series_commitment": "909ff0fa5fcac10f2e50d3f93bdd85920307185913bd396b874e574ec4bcf8cc",
"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
4401a5e0727b86b4ebfa9500745bb62f99cdd887fa5e7849a0ae7e39d9c63763- 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 - 1570
- tree_
size - 2239
- leaf_
hash 3b5e9566cc9e41ba18a7a4a59486ff65aae58b6d38921fe087c3d560da4168b8- audit_
path (12) 0: 868606c24a7ccff2fa4b9080cf8b0842f582e4440429d7ed983d8df68f61bd901: c7af9f340d2d00d66df579a04f2bdea7c4f93ad5e4fb6750cb5b151066130c192: ea770924285e82686307be9ce890a3dea8465ae43a9f2c80ede084ec5cc9f9443: 2fa5de6f80c93428cb6a0692def00ed5f75c808248704d534f2648d62349067e4: 809e28f51f4ac696b3be6332073f7d8f003d4040e293aeaaefd50761ec740ad85: 364ae4f1dc252468c1ac2579db13b9323b70f13f43ce81c26765a4bad76825cf6: a14c441df27a3a317d0289503a03490705cc204897178ef38c051eec450bf5357: f4a858c5afd6d2bbfe79825cc00005d2e5bc4cb6a3723b70509ff06cb4f713008: 49fbc719d10777c21e02e255a1174dbc47e89c67c7b327c5f50e8ea1ffbb5bad9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 9203a1600de814d3afb819f841569332c7e3b58c4d0e0ea56c377729f25dca49- root_
hash 03dd6fb33b4bd65222257eec0069956926795f14f7354795bcb42af5fe51ba08
The earliest published head that covers this entry
- tree_
size - 1585
- signed at
- 8 Sept 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash a224a45fec4b50dd9d3a17f401a022e1320b8849bcdcf3109bc5ef8fc4c335cb- signature
xJYNwZXpQpbXcZskXqf+SutDkfY7nOE9BO058X7fOfif0VtoI/OM8Nfg0bN8D3iUjEtOt+FT3k9g7zbVw7vLCg==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12