NEWS 7 min read

AI Labs Say They Refuted a 20-Year-Old Math Proof. Here's the Catch

Three labs say their models refuted the Exponential Time Hypothesis. The claim is enormous, and nobody has verified it yet. Here is what it actually means.

By EgoistAI ·
AI Labs Say They Refuted a 20-Year-Old Math Proof. Here's the Catch

The claim, stripped of hype

Official image for AI Labs Claim Their Models Refuted a 20-Year-Old Math Proof—Here's the Catch
Official image via techcrunch.com — source checked 2026-10-28.
Official image for AI Labs Claim Their Models Refuted a 20-Year-Old Math Proof—Here's the Catch
Official image via techcrunch.com — source checked 2026-10-28.

On October 27, 2026, TechCrunch reported that frontier AI labs are claiming their models refuted the Exponential Time Hypothesis (ETH). ETH is not a theorem—it’s a conjecture that 3-SAT can’t be solved in subexponential time. If it falls, a lot of complexity-theory results built on it get shaky.

The labs’ framing matters. A model “refuting” ETH is not the same as a human writing a proof. It means a model produced a candidate argument that, if verified, breaks the conjecture. Verification is the whole ballgame.

It is worth being precise about the direction of the claim, because “refuted” is a word that travels badly. ETH asserts a lower bound: that no algorithm solves 3-SAT in time meaningfully below exponential. To refute it you do not need to build a faster solver and benchmark it. You need to exhibit an algorithm and prove—on paper, with an argument that survives line-by-line reading—that its running time is subexponential. The model’s output, then, is not a number or a benchmark result. It is a piece of mathematics, and like any piece of mathematics it stands or falls on whether the steps hold.

That distinction is why the story is less dramatic, and more interesting, than the headline suggests. The labs are not claiming their models out-computed the theorists. They are claiming their models wrote something a theorist would have written, and that the something appears to be correct.

What ETH actually is, and why anyone cares

ETH underpins fine-grained complexity—the branch that says “this problem is hard, and here’s exactly how hard.” It’s why researchers believe problems like edit distance and certain graph problems can’t be solved dramatically faster than the naive approach.

The mechanism is worth spelling out, because it explains why a single conjecture carries so much weight. Fine-grained complexity works by reduction: you assume ETH, then show that if some other problem had a much faster algorithm, you could use it to solve 3-SAT faster than ETH permits. The faster algorithm becomes impossible by contradiction. The result is a web of conditional lower bounds—statements of the form “this problem is hard unless ETH is false.” Each strand of that web is only as strong as the conjecture at its root, which is exactly why a credible refutation would ripple outward rather than stay contained.

For builders, ETH is the invisible reason some algorithms are considered “good enough.” If ETH is false, the theoretical floor on those problems shifts. That doesn’t change your code tomorrow, but it changes which optimizations are worth chasing.

Concretely, the practical reading is about where research effort goes. A conditional lower bound tells a practitioner, in effect, not to bother looking for a dramatically better algorithm, because the search has been ruled out relative to a widely believed assumption. If the assumption weakens, the ruling-out weakens with it, and problems that were written off as settled become open again. Nobody’s production system changes overnight, but the map of what is worth investigating gets redrawn, and maps shape where people dig.

The verification problem

A refutation is only as good as its proof. The labs say their models generated arguments; the math community now has to check them. History is not kind here—AI-generated proofs have a habit of looking airtight until a human spots the gap on page 14.

That habit is not a knock on the models so much as a description of what proof-checking actually is. A proof is a social object as much as a logical one: it becomes accepted when enough qualified people have read it closely enough, in enough different ways, that the remaining doubt is negligible. A model can produce a plausible chain of reasoning; what it cannot do is supply the community’s collective scrutiny. The gap on page 14 is usually not a howler. It is a step that looks like it follows and doesn’t, and it tends to sit exactly where the author—human or machine—was most confident.

There is a counter-argument worth taking seriously, though. Verification is not purely social anymore. Proof assistants and formal checkers can, in principle, take a candidate argument and confirm it mechanically, step by step, with no room for a persuasive-sounding error to slip through. If the labs’ candidate refutations are formalizable, the checking could be far more decisive than the usual years-long refereeing cycle. The catch is that formalization is itself work: someone has to translate the informal argument into a machine-checkable form, and that translation can fail or distort. A proof that resists formalization is not thereby wrong, but it is not thereby confirmed either.

So the honest headline is: models produced candidate refutations. Whether ETH is actually dead depends on peer review, not a press release.

There is also a subtler failure mode than outright error, and it deserves naming. A candidate refutation might be correct but not new—a rediscovery of an argument the field already knows, dressed in fresh notation. Or it might be correct and new but narrow, refuting a variant of ETH rather than the conjecture as stated. Neither outcome would make the models useless; both would make the press release premature. The distance between “a model wrote a true thing” and “the field’s foundational assumption has fallen” is where most of the real story lives.

What builders should take away

First, don’t rewrite your infrastructure because of this. Second, do notice the pattern: frontier models are being pointed at formal reasoning, not just code completion. That’s a different evaluation regime, and it’s one where “the model said so” is not evidence.

That last point is the one worth internalizing. Code completion is easy to evaluate because the code either runs or it doesn’t; the feedback loop is short and brutal. Formal reasoning has no such loop. A proof compiles in the sense that it parses, but parsing is not truth, and the distance between a well-formed argument and a correct one is precisely the space where verification lives. Teams that adopt these models for anything reasoning-adjacent should expect to spend their effort on checking, not generating—and should budget for it accordingly.

If the claim survives scrutiny, it’s a genuine milestone—AI contributing to theoretical computer science, not just shipping PRs. If it doesn’t, it’s still a useful signal about where model capability is heading.

Either way, the useful posture for a reader is neither credulity nor dismissal. Watch the verification. The claim is on the record as of October 27, 2026; the mathematics is not settled until the people who check such things have checked it. That is not a disappointing ending—it is how the field has always worked, and the fact that a model’s output is now subject to the same gauntlet is, in its quiet way, the actual news.

Share this article

> Want more like this?

Get the best AI insights delivered weekly.

By subscribing, you agree to our Privacy Policy. You can unsubscribe at any time.

> Related Articles