delphi.consensus.snapshot
Appended 19 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 - 1969
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 4bfc7aa0-f12f-479c-ba06-d8e4cebfe625- logged_
at 2026-09-19T05:32:21.242245+00:00- previous_
hash a532b84657680d28f15444991ef21d19c388990791005b4b18a6bf95938e0e30- payload_
hash d12bd8a743a10301893cb0aa54363f1036b5c246383d8da0b833092030ad7472- entry_
hash a496c48641117183f089098c00f26147c9edc791704a0b0a42e3540fcf80c64c
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-19T05:32:21.237028Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "4bfc7aa0-f12f-479c-ba06-d8e4cebfe625",
"series_commitment": "3949d36297548044365bd6e522ff9955b956ca1afb1addc552565de57ab5c6cd",
"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
7ac6949d37db5338ef67ce67b6ebbf09740f40625a43edea8d711310f93fdb68- 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 - 1969
- tree_
size - 2503
- leaf_
hash 8414c4b095eb0df52e4d90096daf0877f5dde025a18e4f36b94816cd34ac9382- audit_
path (12) 0: ae9d3d89cecdc681f58cc02dd1213ac322b2904a2d7d0e8b3eefc1600c500e741: 0afb881784278ccab590953902cd95c1d8bca82c15e51fe68901e982ce7d353d2: 0224170d78ac56362e60b842104effe38125d142e1e119ccd74671c754f8e7423: f020276f2bbfe6da3d7b71623a484adf09e16a30f6a6e238131bc2e50cccae3b4: 92ca7172219fe5bc447476e5ff68272a0b5af1cbc550f81974bb208599433d2e5: 606aaf5303d1bdf7e430fa009f7a3bea14fe2b3ffbd61e9b69f34d4e43ed6c6e6: 4e9fd2189aa35b553f1041a8609fcd238f53b35903496c99c13850a60cd15a6d7: 8018b7deda34c522f2ac360ffdd9cc85624549e7457ea594e86a7f04e9a264aa8: 5ab1df6751f0dac25a6ce29d97587d6e08dcdd2d94987223ead725483527e08e9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: aa4b429c2497df4f846fe6b3e60223989226aaf0ba6013dc6f90c17afe986d9d- root_
hash c97f540ea605dcd0a8a4165044c60093cb885a8303800b87d215a424a4d5258d
The earliest published head that covers this entry
- tree_
size - 1977
- signed at
- 19 Sept 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 030d7ba0b761b8420ec6a8cc0c7a9c0b31f4c2f6ef433ff99c5ab3364ba82ab3- signature
46yzVUF2EU2OokUFFvY3uF63GWco2kfLcbaKRU/lmofoXQRYagMPrSTh+OnmHDVsj8htaTgxoLPexSkNWBXkAw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12