Rob Toews called it:
“In 2026, details of SSI’s approach will finally leak to the public.”
We find out by Dec 31, 2026. 126 days to go
Rob Toews: “In 2026, details of SSI’s approach will finally leak to the public.”
MET if Substantive technical details of Safe Superintelligence's core research approach become public via reputable press reporting, leaked documents, or company/employee disclosure. Vague public statements about ambitions or 'a different mountain' without technical substance do not count at any point, before 2026-12-31 23:59 (UTC).
Settles by documented review of public evidence against these locked criteria; the reviewer is named and the reasoning published.
The original wording did not settle the timing on its own. The reading above was chosen at registration and locked with the claim — it was not decided after the fact.
Test details
Resolves TRUE if, between January 1, 2026 and December 31, 2026, reputable press reporting or a public disclosure reveals substantive technical details of Safe Superintelligence's core research approach or paradigm (e.g., its training method, architecture or research agenda). General or non-technical public remarks by Sutskever or SSI staff that do not describe the approach do not count.
Quote verified against the 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.
Read the original on forbes.com ↗
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…
Prediction No. 2 in Rob Toews' Forbes column '10 AI Predictions For 2026', about Ilya Sutskever's Safe Superintelligence.
History — append-only
Proof
2 hashes from this record to the anchored root
- 0x74ab311d0f4fc6c56084441aa601aa7617496c84810d14733963833dfa951ae5
- 0xb6c0d454ccea6d01ff28ea91e799cf76a200f4a3c2a2f06c911369f38cb13ee8
batch #104 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
0x0337d580…e3c0d4 on block explorer
view the canonical capture · the page as served to us, 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.
Related