Urgent.News

What's breaking now, across hundreds of outlets.

Tech

Riemann Hypothesis Lean proof: what the checkers actually check

The Riemann Hypothesis Lean proof that Levent Alpöge posted on November 20, 2026 is 17.4 million lines of code in 175,187 files, and it compiles. Strangers have built it, several independently written checkers accept the exported proof, and one check was still running when I last looked on Saturday afternoon (GMT+7). This post explains what each of those checks covers, what it leaves open, and…

On November 20th, 2026, a breakthrough in mathematics was announced that has sent shockwaves through the scientific community. According to the report, Anthropic's AI models have reportedly proven the Generalized Riemann Hypothesis, generating an astonishing 17.4 million lines of Lean code in the process.

The Riemann Hypothesis, a conjecture first proposed by Bernhard Riemann in 1859, suggests that all nontrivial zeros of the Riemann zeta function are located on the critical line with a real part of 1/2. This hypothesis has profound implications for number theory and has been a subject of intense study for over a century.

In recent months, there have been multiple breakthroughs related to the Riemann Hypothesis. Just a few days ago, my wife and I discussed how the smartest people she knows believe that recursive self-improvement and the end of the world are imminent within the next 12-18 months. This revelation has led me to question the longevity of certain mathematical concepts we currently take for granted.

The news of Anthropic's AI models proving the Generalized Riemann Hypothesis came as a surprise to many. While some are skeptical of the proof's validity due to potential issues with the Lean formal verification system, there have been no retractions of AI results with Lean certificates thus far. This has led me to believe that the proof may stand, although it will likely take years for mathematicians to fully understand and distill the ideas presented.

Rewritten by urgent.news; may contain errors — check the original.

This story

This is one outlet's version. Read the fullest account.

Every outlet that reported this, and when →

Read the original at dev.to →

Report a problem with this story

More in Tech

Headless UI for Beginners: Accessible Components Without the Styling

Building a dropdown or a modal sounds simple until you try to do it properly. Keyboard navigation, focus trapping, screen reader announcements, closing on Escape — accessibility is a long checklist.

  • Headless UI provides accessible components without styling.
  • Implement dropdown using Menu, Menu.Button, Menu.Items, Menu.Item components.
  • Headless UI handles keyboard interactions automatically.

I let a script audit my own product copy — it caught three lies

I run a small store that sells digital kits for people running LLM agents — eval suites, ops runbooks, prompt libraries. Every product page makes claims: "62 prompts," "10 skills," "12 runbooks." Last…

  • Store owner wrote script to audit product copy
  • Found three instances of false claims in descriptions
  • Audit process compares numbers in copy to actual files

No Algorithm Lock-In: Why a Chronological On-Chain Feed Is Regulation-Proof by Design

Governments are moving to force social platforms to offer a chronological, non-algorithmic feed option. On iBird, chronology is not a compliance setting — it is the substrate.

  • iBird platform on Hedera offers chronological feed unaltered by algorithms
  • Each post includes consensus timestamp and immutable sequence number
  • Consensus layer ensures publicly verifiable, non-revocable chronological feed

Large log records in Dynatrace: limits, native support and best practices

A ticket lands: « the partner call is cut off halfway through in the logs ». You open the record and it simply stops. The payload crossed a limit somewhere.

  • Default log entry body limit is 10 MB for Grail path, 512 kB for Classic pipeline
  • API requests limited to 10 MB, batch over 16 MB after preprocessing results in HTTP 413 error
  • OpenPipeline expands record size limit to 16 MB, 50,000 attributes per log with 32 kB cap

More from Saturday 21 November →