delphi.consensus.snapshot
Appended 15 Aug 2026, 15:53 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 - 1
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 48ef81cc-e8c7-4059-91e1-550a9ffc1391- logged_
at 2026-08-15T15:53:34.875779+00:00- previous_
hash fc38e85ac3ddefc3e3f018aaf59a399ad9e167a370d9c62434b26b6a48cfc402- payload_
hash fa802593918c9fc35349b57027e3b7a3661916e05fd4f72be5421b94efea9e7c- entry_
hash a08f37cff791ca765b33214e127264b9cc0b08d83396dee596c2148a558b16a9
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-15T15:53:34.869711Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "48ef81cc-e8c7-4059-91e1-550a9ffc1391",
"series_commitment": "f9ef4bcd240ac4d48942237117cef854f4f20c04de3adc4013c2e9148717a5cc",
"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
19f0f1a86a6f6f1f439ecd131f28f60d1502e6c1554cc480590e3fdc6f23fb83- 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 - 1
- tree_
size - 2305
- leaf_
hash d9ca974c0cede57541dfcb283976c1340ad8f35bdc792d9a7e6c6470000dbe3f- audit_
path (12) 0: e6f9f9e33b9065874d934ce34dabf53925268e64079284b5a099f680365356d61: e18ecbcea86ce9cf0f0dbf66c3b29f8dae9b8f568206fc665cdfcb803cd7c5902: 0181e023c12bf413471cf696a1f35b944e2aa91d05e94025e4ca983e5220b8f53: 6accee06a91eebe583c1229064362cefcdec41ff4bb0d38479e32b13cdf4cc7a4: b70d290aa081a17cfd1dd59b61f1a28551b4aa8df2915bb773f8eda8b60841055: b74c92a6356a40d4a8987db99772ead75d18bf349905054ba53bbc3401d9b2b96: 432b3bec17cc8d9bd118f5d2d11fc56d0578ec1940af60be2192f2f1b8d43dc67: 925d039cfaa2795efce751d71988395a9d8544d4910a71d82c761e6c8e51ba2e8: 6e5b02022079dc614c5f74ca1c784cf9700d832e05c2eec11f0ad0a37376b46d9: 2fb679aab258481705c982e553094522ea7bb93361711a8387ebf359e8c3e43110: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: 4ed47b3cf2c766bbf573b761e9026e21f264edbbd6420d65b1efd886894c770c- root_
hash 9259657b60d7c54c7f061a7a621bf2f8747cab0885ee335ac1ed3b6657c9740d
The earliest published head that covers this entry
- tree_
size - 374
- signed at
- 19 Aug 2026, 20:25 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash ecf4adc708ae542a0339e03fd4cc181cf49d0329768627c5345c915a58bd813a- signature
3yL+JZfMhiQ6rm5rCTTg7iT+or04nCGVcQ08ILMw/d7eqvR4Jid7cEg2rQU5fCX7llStjVkTC9jVZjfGQvtMAg==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12