conv.

All stories
ScienceActive today · day 8

Mathematicians Rebut OpenAI's Navier-Stokes Proof as Solving the Wrong Problem

A new proof shows OpenAI's forced-fluid loophole can never be extended to the real Millennium Prize problem, reviving a dispute over AI-generated math.

What to know

  • OpenAI's headline claim of solving Navier-Stokes rests on a version of the problem that includes an external force, which most mathematicians consider outside the scope of the real Millennium Prize question.
  • Independent formal verification by 8Braid confirmed OpenAI's Lean proof checks pass, but stressed that passing formal checks does not settle whether the result addresses the intended physical problem.
  • A newly posted proof by three mathematicians shows OpenAI's forced-fluid method can never be extended to the unforced case, closing off the loophole permanently absent a new approach.
  • The dispute has sharpened tension between the mathematicians who built the underlying forced-blowup method and OpenAI, which released its result less than a day after their preprint.

OpenAI AI companyLuis Silvestre Mathematician, University of ChicagoDiego Córdoba MathematicianLuis Martínez-Zoroa Mathematician8Braid Independent verification team

Mathematicians Rebut OpenAI's Navier-Stokes Proof as Solving the Wrong Problem
scientificamerican.com

How it unfolded 3 developments, newest first · click a bar or a number to jump articlesposts

Peak 5 pieces in two hours at Sep 22, 2 PM; 40 pieces over 8 days (5 articles · 11 posts · 24 comments) Sep 16, 12 PM — 1 piece · 1 post — Hacker News 1Sep 16, 2 PM — quietSep 16, 4 PM — quietSep 16, 6 PM — quietSep 16, 8 PM — quietSep 16, 10 PM — quietSep 17, 12 AM — quietSep 17, 2 AM — quietSep 17, 4 AM — quietSep 17, 6 AM — quietSep 17, 8 AM — 1 piece · 1 article — Google News 1Sep 17, 10 AM — quietSep 17, 12 PM — quietSep 17, 2 PM — quietSep 17, 4 PM — quietSep 17, 6 PM — quietSep 17, 8 PM — quietSep 17, 10 PM — quietSep 18, 12 AM — quietSep 18, 2 AM — quietSep 18, 4 AM — quietSep 18, 6 AM — quietSep 18, 8 AM — quietSep 18, 10 AM — quietSep 18, 12 PM — quietSep 18, 2 PM — quietSep 18, 4 PM — quietSep 18, 6 PM — quietSep 18, 8 PM — quietSep 18, 10 PM — quietSep 19, 12 AM — quietSep 19, 2 AM — quietSep 19, 4 AM — 1 piece · 1 article — Google News 1Sep 19, 6 AM — quietSep 19, 8 AM — quietSep 19, 10 AM — quietSep 19, 12 PM — quietSep 19, 2 PM — quietSep 19, 4 PM — quietSep 19, 6 PM — quietSep 19, 8 PM — quietSep 19, 10 PM — quietSep 20, 12 AM — quietSep 20, 2 AM — quietSep 20, 4 AM — quietSep 20, 6 AM — quietSep 20, 8 AM — quietSep 20, 10 AM — quietSep 20, 12 PM — quietSep 20, 2 PM — quietSep 20, 4 PM — quietSep 20, 6 PM — quietSep 20, 8 PM — quietSep 20, 10 PM — quietSep 21, 12 AM — quietSep 21, 2 AM — quietSep 21, 4 AM — quietSep 21, 6 AM — quietSep 21, 8 AM — quietSep 21, 10 AM — 2 pieces · 1 article · 1 post — Mastodon 2Sep 21, 12 PM — quietSep 21, 2 PM — 1 piece · 1 article — Google News 1Sep 21, 4 PM — quietSep 21, 6 PM — 1 piece · 1 post — Hacker News 1Sep 21, 8 PM — quietSep 21, 10 PM — 2 pieces · 1 article · 1 post — Mastodon 1, Newswires 1Sep 22, 12 AM — quietSep 22, 2 AM — 1 piece · 1 post — Mastodon 1Sep 22, 4 AM — 4 pieces · 2 posts · 2 comments — Hacker News 2, Reddit 2Sep 22, 6 AM — quietSep 22, 8 AM — 1 piece · 1 post — Bluesky 1Sep 22, 10 AM — quietSep 22, 12 PM — 1 piece · 1 post — Lobsters 1Sep 22, 2 PM — 5 pieces · 1 post · 4 comments — Lobsters 3, Hacker News 1, Mastodon 1Sep 22, 4 PM — 5 pieces · 1 post · 4 comments — Hacker News 4, Mastodon 1Sep 22, 6 PM — 5 pieces · 5 comments — Hacker News 4, Lobsters 1Sep 22, 8 PM — quietSep 22, 10 PM — 1 piece · 1 comment — Lobsters 1Yesterday, 12 AM — 1 piece · 1 comment — Hacker News 1Yesterday, 2 AM — 1 piece · 1 comment — Lobsters 1Yesterday, 4 AM — 1 piece · 1 comment — Lobsters 1Yesterday, 6 AM — 2 pieces · 2 comments — Lobsters 2Yesterday, 8 AM — 1 piece · 1 comment — Reddit 1Yesterday, 10 AM — quietYesterday, 12 PM — 1 piece · 1 comment — Lobsters 1Yesterday, 2 PM — quietYesterday, 4 PM — quietYesterday, 6 PM — quietYesterday, 8 PM — 1 piece · 1 comment — Hacker News 1Yesterday, 10 PM — quietToday, 12 AM — quiet ◂ 1 earlier23
Sep 17Sep 18Sep 19Sep 20Sep 21Sep 22yesterdaynow · 2:58 AM ET
  1. 3

    Scientific American asks whether OpenAI solved the wrong problem

    The outlet reported that OpenAI's proof solves a forced variant of Navier-Stokes that most experts consider disconnected from the real, unforced problem mathematicians care about, quoting several mathematicians who argue the core question remains open.

    “The most important problem is unsolved. The Clay problem is settled, but the main problem for the Navier-Stokes equations is not.”
    — Luis Silvestre
    1. first by Scientific American, 2d ago

    • > In a sense, the LLM found and exploited a loophole in the framing of the question. they tend to be very good at that.

      lakemath,vibecoding1d ago12▲view on Lobsters ↗
    2 more of the top 3 · 27 posts in this stretch
    • clarinette@mastodon.online

      «In yet another sign of # AI ’s surging dominance over human minds, # OpenAI recently claimed to solve one of math’s biggest questions: the Navier-Stokes problem. But now three mathematicians have showed OpenAI’s work dodges the question rather than solving it. » https://www. scientificamerican.com/article…

      clarinette@mastodon.onlineMastodon1d ago1▲view on Mastodon ↗
    • No, OpenAI did not solve the "wrong" Navier-Stokes problem. OpenAI did not solve the hardest version of the problem (unforced blow-up), but did give a solution to the Clay Millennium Prize Problem as written and understood, choosing the explicitly allowed forced option.SciAm writes "in a sense, the LLM found and exploited a loophole in the framing…

      jonlongHacker News1d agoview on Hacker News ↗
    all of them →
  2. 2 days quiet
  3. 2

    Three mathematicians prove OpenAI's method cannot be extended

    Three mathematicians posted a proof showing that OpenAI's forced-fluid approach can never be extended to solve the full, unforced Navier-Stokes problem — meaning the loophole OpenAI exploited is a dead end barring an entirely new idea.

  4. 1 day quiet
  5. 1

    Independent team verifies OpenAI's formal proof checks

    Researchers at 8Braid reproduced OpenAI's submitted Lean formal checks, confirmed both the Nanoda and default Lean kernels accepted the proof, and derived an explicit stability bound for one algebraic step, while noting that formal verification does not settle whether the result matches the intended physical problem.

    “We reproduced the formal checks, proved an explicit bound for one construction step, and tested how 8DB handles its evidence.”
    — 8Braid
  6. background

    OpenAI announces an AI-generated Navier-Stokes blowup proof — Less than a day after the mathematicians' step, OpenAI released a proof of finite-time breakdown for the Navier-Stokes equations, generated by an internal LLM together with a Lean formalization, claiming eligibility for the Clay Mathematics Institute's $1 million Millennium Prize.

  7. background

    Mathematicians produce a forced blowup using Córdoba–Martínez-Zoroa method — Two mathematicians used a program developed by Diego Córdoba and Luis Martínez-Zoroa, aided by AI, to produce a finite-time blowup for a frictionless fluid under a specific external force — a step widely seen as a major advance toward the Navier-Stokes problem.

Also covered reported alongside — the timeline has no entry for these yet

  1. first by dars.gov.et, 6d ago · also The Conversation

    1 more headline

and 1 smaller piece

What people are saying 21 voices from 5 sites · best of 27 · verbatim