OpenAI publishes an AI-generated Navier-Stokes solution with a Lean formalization
The company reports a finite-time singularity proof and releases a paper and formal code, while independent mathematical scrutiny remains decisive.
Key takeaways
OpenAI published an AI-generated proposed solution to the Navier-Stokes existence and smoothness Millennium Prize Problem on September 8. The company says its internal system constructed an initially smooth, finite-energy fluid flow that develops a singularity in finite time, and released both a mathematical write-up and a Lean formalization. OpenAI reports that the Navier-Stokes effort used a coordinated system on the order of 10,000 concurrent agents, producing about 2.7 million messages and roughly 130 billion output tokens. The agents reached the result after about 88 hours, followed by 17 hours of Lean formalization and verification using GPT-6 Astra. OpenAI says it does not intend to claim the prize. The result should therefore be treated as a major candidate proof whose significance depends on independent expert review, code inspection, and reproduction.
Direct answer
OpenAI published an AI-generated proposed solution to the Navier-Stokes existence and smoothness Millennium Prize Problem on September 8. The company says its internal system constructed an initially smooth, finite-energy fluid flow that develops a singularity in finite time, and released both a mathematical write-up and a Lean formalization. OpenAI reports that the Navier-Stokes effort used a coordinated system on the order of 10,000 concurrent agents, producing about 2.7 million messages and roughly 130 billion output tokens. The agents reached the result after about 88 hours, followed by 17 hours of Lean formalization and verification using GPT-6 Astra. OpenAI says it does not intend to claim the prize. The result should therefore be treated as a major candidate proof whose significance depends on independent expert review, code inspection, and reproduction.
Verified facts
OpenAI says its internal system constructed a three-dimensional incompressible flow that starts smoothly at rest, keeps finite energy, and develops a singularity in finite time.
The company links a paper and a Lean formalization. It reports that the main result arrived after about 88 hours and that Lean formalization and verification took another 17 hours using GPT-6 Astra.
OpenAI reports a coordinated system on the order of 10,000 concurrent agents. It records about 2.7 million messages and roughly 130 billion output tokens for the Navier-Stokes effort, and says it does not intend to claim the prize.
What changed
- Paper and Lean code released together
- Agent coordination reaches roughly ten thousand
- Research cost disclosed in messages and tokens
- Conclusion depends on external mathematical review
Impact for AI users
The announcement demonstrates a new scale for problem decomposition, parallel search, and formal verification in AI research systems. A publisher's claim alone does not establish community acceptance of a mathematical solution. Researchers need to inspect definitions, assumptions, critical lemmas, and consistency between the Lean code and written proof. Buyers of scientific agents should also measure reproducibility, compute cost, and independent review time rather than only the final answer.
Operating checklist
- Pin versions and hashes for the official paper and Lean repository so review targets do not drift.
- List key statements, assumptions, library dependencies, and any prose step outside the formalization.
- Commission independent mathematical and formal-methods reviews and publish a reproducible environment.
- Label the result as a publisher-proposed proof until external scrutiny is complete.
AI frontier news and analysis, AI software and model tools, AI skill tutorials and validation methods, and AI account and permission guidance
FAQ
Does this mean the problem is formally accepted as solved?
It confirms that OpenAI published a solution and formal materials. Acceptance still depends on independent review and the relevant institutional process.
Does Lean automatically prove every claim in the article?
No. Lean can verify encoded statements and proof steps, but reviewers must check that the formal statement matches the original problem and written assumptions.
Can an ordinary team reproduce ten thousand agents?
The cost is likely prohibitive. A practical first step is reproducing the released proof, toolchain, and critical local results.
Summary
The meaningful milestone is not an AI answer alone, but whether the paper, formal code, cost record, and independent scrutiny form a reproducible evidence chain.
This AI-assisted article is checked by ENHE AI automation for official sources, bilingual fields, media rights, page safety, and historical duplication before publication.
What this means for everyday users
The announcement demonstrates a new scale for problem decomposition, parallel search, and formal verification in AI research systems. A publisher's claim alone does not establish community acceptance of a mathematical solution. Researchers need to inspect definitions, assumptions, critical lemmas, and consistency between the Lean code and written proof. Buyers of scientific agents should also measure reproducibility, compute cost, and independent review time rather than only the final answer.
Tools you may use
Related tutorials
[[zh]][[/zh]][[en]]Review a public website[[/en]]
SearchScope SEO/GEO
[[zh]][[/zh]][[en]]Access and usage guide[[/en]]
AI Prompt Management System | 418 Bilingual Prompts for Writing, SEO and AI Creation
High-Frequency AI Prompts for Work, Learning, and Teaching guide
High-Frequency AI Prompts for Work, Learning, and Teaching
Related Tools And Tutorials
Use the following ENHE AI sections to continue from the news signal into tool selection, account-service guidance, or practical learning.
Related reading
NVIDIA Expands DGX Spark With 64GB: Evaluate a Local AI Workstation
On October 2, NVIDIA announced a 64GB unified-memory DGX Spark configuration and said partner availability would begin October 23 at a starting price of $4,999. NVIDIA says one unit can run models up to 100 billion parameters and that two systems can pool 128GB; it reports up to 1.7x performance in its own Qwen 3.8 27B test. Availability is forward-looking, and performance figures are vendor results. Model choice, quantization, context length, and concurrency change outcomes. This article offers a practical evaluation checklist for teams comparing local inference with cloud services. Teams should check applicability against their own environment, record assumptions, and validate decisions with representative operational evidence.
Microsoft’s 2026 Defense Report: AI Is Changing the Pace of Cybersecurity
In its October 1 commentary on the 2026 Microsoft Digital Defense Report, Microsoft says threat actors are using AI in parts of existing workflows, including reconnaissance and social engineering. The post does not claim that attacks have become fully autonomous; it highlights changes in speed and scale. Identity controls, least privilege, data protection, monitoring, testing, and secure development remain central. This article separates Microsoft’s observations from independent conclusions and turns the post into a practical checklist. Teams should compare the claims with their own telemetry and incident history before changing priorities. Teams should check applicability against their own environment, record assumptions, and validate decisions with representative operational evidence.
A One-Week AI Agent Security Review Using the OWASP Risk Framework
The OWASP Gen AI Security Project published its 2026 Top 10 for Agentic Applications in December 2025 as a risk framework for systems that plan, call tools, or act across services. It is a starting point for security discussion, not a certification, compliance attestation, or guarantee of safety. This article turns it into a one-week baseline review: inventory agent identities and tools, narrow permissions, treat external content as untrusted input, record consequential actions, test shutdown and revocation, and define approval and recovery for high-impact operations. Teams should extend the checklist to match their architecture and threat model. Teams should check applicability against their own environment, record assumptions, and validate decisions with representative operational evidence.
Microsoft Announces Streaming Transcription: Voice Agents Can Respond Earlier
On October 1, Microsoft AI announced MAI-Transcribe-2-Streaming, MAI-Voice-2.1, and a Flash variant. Microsoft says the streaming transcription model supports 60 languages with continuous language detection, and that initial partials can appear just over 100 milliseconds after audio arrives. Its speech-generation models are described as supporting 23 languages and 26 locales. Rankings, accuracy, speed, and price claims come from Microsoft’s announcement and do not predict results for every workload. This article explains the interaction changes and suggests tests for latency, revisions, accents, privacy, and total cost. Teams should check applicability against their own environment, record assumptions, and validate decisions with representative operational evidence.
A Banking Agent Writes Then Reverses: AWS Describes a Demo, Not Production Trading
An October 5 AWS post describes Texas Capital Bank’s Trust-Earned Autonomy pattern, in which reviewer agreement can inform an agent’s permissions and a prior write can be reversed if trust declines. AWS explicitly says the agent pattern is still a demonstration running on demo-scale Apache Fineract with synthetic data, not a production workload or real production transaction flow. The bank’s separate document-extraction capability is described as operating in production. This article focuses on revocable authority, auditability, and system boundaries, and avoids presenting the demonstration as an already deployed autonomous banking agent. Teams should check applicability against their own environment, record assumptions, and validate decisions with representative operational evidence.
OpenAI Updates Content Provenance: Extending the Work to EU Text
OpenAI's October 5 announcement sets out a phased approach to text watermarking, including API opt-in and a regional product rollout. The details are public and should be read alongside its broader media-provenance guidance. For publishers, the practical task is to distinguish which checks apply to text, images, and audio, and to keep evidence of how content was created and reviewed. A useful editorial record separates product coverage, source checks, permission to use materials, and AI disclosure. This article explains those distinctions and proposes a review workflow. A provenance signal is supporting evidence, not a substitute for factual verification or a conclusion about an author's identity or ownership.



