

No. I don’t think you understand what GRH is.
If anything the proof helps cryptography.


No. I don’t think you understand what GRH is.
If anything the proof helps cryptography.


It’s incomprehensible as a whole but not in pieces.
It will be simplified, refactored, maybe rebuilt from the ground up. It won’t be incomprehensible for long.
The last I looked the size had already been reduced by 25% based on community efforts.
Kind of fun watching the Lean Prover Zulip chat play with it.


There are a bunch of ways that a proof written in Lean can be invalid.
The most obvious is that the problem statement is invalid or incomplete. This was not really a concern here as the proof used Mathlib’s built-in definitions rather than restating the problem, but nonetheless it has been verified.
Beyond that Lean proofs can contain custom axioms/assumptions, shortcuts, tricks, exploits. And there’s the possibility that the Lean compiler used in the proof had a bug.
Anyway all that has been tested and verified. The problem statement is valid. The proof doesn’t contain any tricks or assumptions. It compiles on every major Lean kernel.
Basically: it is almost certainly mathematically true. The next step is humans actually understanding it.


I don’t see any reason to think the official explanation isn’t truthful. It makes perfect sense.


SMART was being used in DC airspace in September.
They rolled it out nationwide on November 10th (not the 12th as you said): https://www.faa.gov/newsroom/statements/general-statements?hl=en-US
Does not seem likely to be related as SMART mostly reads from the SWIM data feed.
This is nonsense.
Humans simply have to validate the question. The whole point of Lean and formal proof is to validate everything downstream of that.
The proof is real, and validated.
The monumental human work is reducing it and then understanding it. Although honestly LLMs will do much of this work too.