delphi.question.published
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 - 28
- entry_
type delphi.question.published- entity_
type forecast_question - entity_
id 6eba5275-6e6a-4119-81bb-48c75288862c- logged_
at 2026-08-15T15:53:36.195415+00:00- previous_
hash 1c761165566fe951a960975617bcb6ca8e05a14bb1b98d4e8ac272d9421eea3d- payload_
hash d65fbcd764a2b98e84fb92764731216a1bb49182f3c71555416ce35ce2041ff9- entry_
hash 8823d7cf66957d029012b5fa4dd00cd28c51cd715462b2b319a95fbe12a12480
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"slug": "will-openai-announce-a-model-numbered-above-5-6-between-24-august-and-31-october-2026",
"title": "Will OpenAI announce a model numbered above 5.6 between 24 August and 31 October 2026?",
"origin": "EDITORIAL",
"timebase": {
"clock": "REAL_UTC"
},
"closes_at": "2026-08-23T22:00:00.000000Z",
"opened_at": "2026-08-15T15:53:36.192163Z",
"blind_mode": true,
"provenance": "PUBLIC_RECORD",
"description": "GPT-5.6 began rolling out on 4 August 2026 and a cyber-specialised variant followed on 10 August. The question is about the version number rather than about a flagship, because the number is the one part of the announcement that is not a judgement call.",
"question_id": "6eba5275-6e6a-4119-81bb-48c75288862c",
"resolution_criteria": "YES if a post dated between 24 August and 31 October 2026 inclusive on openai.com/news announces a model whose version number, as written by OpenAI, is strictly greater than 5.6 — for example 5.7 or 6. Named variants of 5.6 do not count, however capable.",
"expected_resolution_at": "2026-11-02T12:00:00.000000Z",
"canonical_source_policy": "The dated post list at https://openai.com/news/.",
"resolution_rule_revision": 1
}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.
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 - 28
- tree_
size - 2285
- leaf_
hash 22fad4eebc784cab32a6183d98630b46955bf3fbdc160f04fd8593e241344562- audit_
path (12) 0: b05879de5514a51ad16e5a06ff43aff4e7111cb86e25c93f2cd643e45d3d88b11: 967a7c0abbc6916ad66392ca2b1444c0e2244e3206796ae5909fe8e38a006fdb2: 1bab8e6b1385cbd43dadbbe19c62fa5e79c714dc2ed265dd3bc33b2b34b507c93: 1cf5d64fb4965f4940c526fa698108d7c4578146408b3cd51dabd149d5674bd74: 7d6682fa6e600d077f7841e30621efe19877a3f61ce600d24a3eb3948d17dd255: b74c92a6356a40d4a8987db99772ead75d18bf349905054ba53bbc3401d9b2b96: 432b3bec17cc8d9bd118f5d2d11fc56d0578ec1940af60be2192f2f1b8d43dc67: 925d039cfaa2795efce751d71988395a9d8544d4910a71d82c761e6c8e51ba2e8: 6e5b02022079dc614c5f74ca1c784cf9700d832e05c2eec11f0ad0a37376b46d9: 2fb679aab258481705c982e553094522ea7bb93361711a8387ebf359e8c3e43110: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: a95d574e00e9fefbc454b084e8cb19edc83831071366b2d8dc1af2f7114b646f- root_
hash 17330c6327e6363b8237bd4a68d5ee420a6d0f745c8d8bab0a90305d6bccba50
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