Urgent.News

What's breaking now, across thousands of outlets.

AI

Anthropic scientist claims proof of math’s most famous problem, with AI help

The hypothesis, named for German mathematician Georg Bernhard Riemann who first proposed it in 1859, concerns the distribution of prime numbers, which are the building blocks of all whole numbers

Anthropic scientist claims proof of math’s most famous problem, with AI help

Anthropic's mathematician Levent Alpöge declared on November 20, 2026, that he had discovered a proof of the Riemann hypothesis, using the assistance of Anthropic's AI model Claude. The Riemann hypothesis, originally proposed by Riemann in 1859, revolves around the distribution of prime numbers, which are fundamental to whole numbers.

Mathematicians have been striving to prove this hypothesis for over 160 years, leading to advancements in various fields such as algebraic geometry, probability theory, quantum physics, and dynamical systems. The Clay Mathematics Institute has offered a $1-million prize for a solution. In his announcement, Alpöge provided over 1.7 crore lines of code, claiming to have the complete proof, and also asserted that he had proven a stronger result known as the generalized Riemann hypothesis.

Nevertheless, he refrained from presenting a conventional paper on his work and admitted that he does not fully comprehend all the arguments employed by Claude in arriving at the result. Several independent mathematicians, including Andrew Sutherland from the Massachusetts Institute of Technology, have verified that Alpöge's code, along with the proof, meets rigorous checks, and two distinct proof-checking systems have accepted the result.

Written by urgent.news from The Hindu - Sci-Tech's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Also reported by 1 other outlet

Every outlet that reported this, and when →

Read the original at thehindu.com →

More in AI

AI Image Generation Pipeline: 5 Queue Tests for 429 Object Storage Upload Retry Backoff

Short answer: Put generated report images in private object storage, but make generation and upload separate queue states; persist the generated bytes before upload, retry a 429 with bounded backoff…

  • Pipeline divides generation and upload into separate queue states
  • Persist generated bytes before retrying 429 upload attempts
  • Use exponential backoff with jitter and fixed attempt limit for retries

Stop regex-ing the LLM's prose

Ask an LLM a question and it hands you back prose. Lovely to read, miserable to program against. You wanted the one number buried in the middle of it, and now you're writing a regular expression to…

  • Ask LLM for structured data instead of paragraphs
  • Define Go struct with specific fields like severity and fix
  • Model response is automatically unmarshalled into struct

More from Saturday 21 November →