Sam Altman called it:
“we are going to again fail in 2026 to meet demand.”
On the record. Nobody can edit it, including Sam.
Sam Altman: “we are going to again fail in 2026 to meet demand.”
No machine-checkable test was locked with this record, so it is preserved rather than scored. Thonest never invents a threshold or deadline the speaker did not give.
This is kept for what it is: something said, on a date, from a source anyone can check. No test was locked, so nothing settles it and it is never counted for or against anyone. Thonest will not invent a threshold or a date that was never said — a claim scored against criteria written afterwards would prove nothing.
Submitter-attested — no machine-readable source
Added by Thonest from a public source. The person quoted did not submit, approve, or endorse this record; the wording is verified against the source itself.
Watch what they said — from 1:19:06 ↗
Reactions are about the record being worth keeping — never about whether the person was right. They are never counted for or against anyone, and never used to rank anything.
Discussion
Loading…
- ✓ Video and channel verified by YouTube
- ✓ Statement located at 1:19:16
- — Transcribed and timestamped by the submitter, who confirms they listened to the passage
Transcribed from the audio and confirmed by the submitter, who listened to this passage. YouTube confirms the video and the channel, not the words — those are checkable in one click by anyone. Watch the full moment →
From "Sam Altman: How OpenAI Wins, ChatGPT’s Future, AI Buildout Logic, IPO in 2026?" (Alex Kantrowitz).
History — append-only
Proof
2 hashes from this record to the anchored root
- 0xca3e400c998e8e2fa0170205895d1fd27d5a629d4d2484ca5b9616bdd14b4ddf
- 0xf90205866fbcf0903f2a14f18a4fb2258a8335c28702b0ae0d3eadbe1d2b05e8
batch #84 manifest · 4 entries
the contract refuses any batch that doesn’t follow the previous one, and has no function to edit or delete one — including for us
0x34b47002…dc007e on block explorer
view the canonical capture · the platform's own API response, kept verbatim and covered by the evidence hash
✓ The anchored proof cannot be rewritten, and the published record is append-only by default. Everything that happened afterward is in the history above — corrections are appended, never silently edited in.
The check runs in your browser and reads the anchored root straight from a public Base node — not from Thonest. How this works.
Disputes
No disputes have been filed. If something here is wrong — a misquote, a wrong date, a misattributed source — say so and it gets answered on the record. How disputes work.