Does AI Math Kill Crypto?GitHub / feedbackAnalysis / cascade riskUnified attack mapOld / new SOTA2^k comparisonsResource tablesReview / evidence
2026-10-07 · Attack-path map · English edition

How far are OpenAI Math’s results from “on-chain assets can be stolen”?

From the public mathematical results on the left, through the missing algorithmic and engineering conditions, to the concrete bad outcomes on the right.Arrows are not causal relationships that have already occurred; dashed boxes mark key links that have not yet been filled in.

Executive analysis and nonlinear cascade risk

Publication check: October 8, 2026. The live catalogue now lists 719 manuscripts across 372 families. The official revision history records three withdrawals outside the eight families selected here, plus other repairs. For #002 it records removal of an obsolete introductory citation. This report retains its pinned 722-manuscript source snapshot; it is not a new audit of every revised manuscript. The history also records 13 reference-only updates without listing every affected title; whether any of the ten selected manuscripts are included was not separately checked. All attack implications remain conditional on the stated theorems.

This analysis examines the path from a mathematical advance to someone stealing BTC/ETH keys, forging validator signatures, or defeating KZG and the ZK systems that depend on it.

The pinned October 7 source snapshot contains 722 manuscripts across 372 result families. The live repository may change after this snapshot. We selected 8 candidate families with plausible cryptographic connections and examined 10 manuscripts in more detail. This was a focused review, not an exhaustive audit of the entire collection.

Our conclusion: these reviewed results do not establish a practical, end-to-end attack-cost reduction against the blockchain targets we examined.

Some of the claimed theoretical advances are substantial. But the missing steps between those advances and a usable attack are substantial too. Here is what we found, assuming the stated theorems hold.

1) #142 — deterministic polynomial factoring over prime fields

This factors a polynomial over a known prime field. It does not factor an RSA modulus.

Randomized expected-polynomial-time algorithms for the polynomial task already existed. The new result removes randomness; it does not establish a speed advantage. A usable new reduction from RSA factoring or elliptic-curve key recovery to this task is still missing.

We cannot turn this theorem into “RSA-2048 is now cheaper to break.”

A follow-up question concerns the tools inside #142: Jacobian division and norm-equation methods might inspire other algorithms. Their stated settings involve restricted curve structure and divisibility promises. The paper’s discrete-log subroutine handles small-prime components; it is not a generic large-prime discrete-log solver. No effective reduction from these tools to extracting a deployed curve’s hidden scalar, with practical target-sized costs, is established here. This is a research direction, not a demonstrated attack.

2) #279 — exact quantum integer factoring

The ideal quantum circuit succeeds with probability exactly 1 over a fixed finite gate set, with polynomial worst-case resource bounds.

Shor already provided a quantum factoring route; candidates can be checked and success amplified through repetition. The new exactness guarantee is a theoretical improvement, but the paper establishes no lower practical qubit, gate-count or runtime requirement.

It also does not directly supply a new elliptic-curve discrete-log attack. The practical hardware gap remains.

3) #103 — L = RL = BPL

For the polynomial-time deterministic simulations compared here, the workspace bound improves from O(log² n) to O(log n). That is a major theoretical space improvement.

But the theorem needs an appropriate randomized log-space program as its input. It does not provide the program that solves secp256k1 key recovery. Finding such a target solver would itself already be a cryptanalytic breakthrough.

Less workspace for a simulation does not give us a new key-recovery work estimate.

4) #107 — faster dense matrix multiplication

This is the candidate with the most direct-looking connection to an existing attack component: linear algebra in NFS/TNFS attacks on finite-field discrete logarithms.

The field matters. The reported bounds are ω ≤ 2.25 over the complex numbers; ω < 2.258 outside an uncomputed finite exceptional-characteristic set; and ω < 2.371054886006746 over every fixed field.

Cryptanalytic relation matrices are sparse. Common solvers exploit that sparsity, with a rough cost around w·N² field operations, where w is row weight. A better dense-multiplication exponent does not by itself establish a faster sparse solve or a cheaper complete attack.

The striking complex-field bound cannot simply be inserted into a BLS/KZG security estimate.

5) #109 — integer multiplication below n log n

The reported asymptotic bound is O(n(lg n)^(1−κ)), with κ = 2^−182, in a fixed multitape Turing-machine model.

The paper describes extremely large constants and thresholds, and uses schoolbook multiplication below its cutoff. It establishes no speed gain at cryptographic sizes.

Substituting 256 or 2048 into the asymptotic expression would not establish an implementation speedup.

6) #029 — the proof input behind #142

The relevant connection is its uniform Hecke zero-free theorem, not the primitive-root count itself. It supports #142’s proof chain. It does not supply an independent RSA or curve-key recovery algorithm.

7) #002 — an exact BSD formula under stated conditions

This concerns global arithmetic of elliptic curves. No effective algorithm is supplied for extracting the hidden scalar d from a finite-field public key Q = dG.

8) #030 — modularity over imaginary quadratic fields

The structural theorem becomes more general. But the natural j=0 CM lifts of the blockchain curves discussed already had classical modularity results. A usable bridge from the new theorem to target discrete logs remains missing.

How big is the demonstrated security drop?

For secp256k1, roughly 2^128 group operations remains a representative generic classical attack scale, with existing constant-factor improvements. This is not a security lower bound.

These results supply no established new end-to-end figure such as 2^100 or 2^80. For BLS/KZG, the cost also depends on the curve, target instance and precomputation model; there is no single honest number covering every system.

We also separated illustrative function values from attack costs. For example, changing c from 2.371177 to 2.25 makes the normalized function m^c about 5.33× smaller at m = 10^6. That is not a measured speedup, 81% fewer attack operations, or a loss of 2.415 security bits.

The actual consequences, if the missing bridges were built, would differ:

• secp256k1 key recovery → ECDSA/Schnorr forgery → control of assets whose public keys and spending conditions permit it.
• Relevant BLS key recovery → forged validator messages; consensus impact depends on stake and protocol conditions.
• Relevant KZG trapdoor recovery → false openings; matching ZK systems and applications need separate analysis.
• RSA factoring → RSA-dependent systems; it is not the native BTC/ETH signature route.

That is what the diagrams show: reported results, existing algorithms, missing attack bridges, practical resource gaps, and conditional on-chain consequences.

Cryptanalytic progress can be nonlinear.

A reusable mathematical method could resolve several missing bridges at once. A practical attack on an affected discrete-log group could spread across the schemes using that group. In finite-field DLP attacks, substantial precomputation can be reused across targets in the same field; each target still requires further work. And recovering one KZG setup trapdoor can undermine many commitments using that setup, without recovering a fresh trapdoor for each commitment.

Ethereum’s KZG commitments and validator BLS signatures both use BLS12-381. A practical discrete-log algorithm applicable to the relevant groups could undermine both systems. By contrast, leaking one KZG setup’s τ defeats binding for commitments under that SRS without itself recovering validator keys. A solver for a relevant pairing target field would not automatically attack secp256k1. Consensus impact depends on the effective validator stake and messages an attacker can forge, not simply on recovering one BLS key.

Those are real amplification mechanisms. Our dependency diagrams are not a timeline: the number of missing arrows is not a measure of remaining research effort. The review does not establish that these eight results have triggered such a cascade, or that future progress will be slow or incremental.

Conclusion: the public evidence in these eight candidate families does not establish that practical blockchain key theft or proof forgery has become substantially cheaper.

This is an assessment of demonstrated attacks. It does not establish future safety, a probability of a break, or a percentage of “progress toward breaking crypto.”

The underlying source-statement and arithmetic analysis went through three review rounds with Claude Opus 5.5, with the displayed arithmetic separately recomputed. The nonlinear scenarios above are conditional extrapolations, not demonstrated attacks. We did not verify the original mathematical proofs; model agreement is not a correctness certificate.

Source collection: https://github.com/openai/math
Snapshot examined: October 7, 2026.

Primary references for the shared-curve facts: Ethereum KZG specification and validator BLS public-key specification. The cascading attack implications above are conditional inferences, not demonstrated attacks.

2026-10-07 · Standalone conclusions table accompanying the route map

Which attack cost did the mathematical breakthroughs change?

Compare, item by item, the work, space, hardware and success guarantees of old algorithms and new results, then judge whether these changes can lower the complete attack cost and what would ultimately be endangered.

The 2^k scale: full attacks and mathematical function examples

For a specified attack and operation unit, k=log₂(W). A full-attack speedup of S reduces the work exponent by log₂S: 1,024× saves 10; 2²⁰⁰ to 2¹⁸⁰ is about a million-fold gain. A subtask’s asymptotic exponent change cannot be deducted directly from cryptographic security.

1. Full attacks: what is established

TargetExisting public baselineNew cost supplied by these eight results
BTC / ETH: secp256k1 key recoveryGeneric classical search costs roughly 2¹²⁸ group operations; existing automorphisms and constant-factor optimizations slightly reduce the exponent. This is a representative attack scale, not a security lower bound.No lower new target-work scale is established. A change from 2¹²⁸ to 2¹⁰⁰ or 2⁸⁰ cannot be reported.
BLS / KZG / pairing proofsCosts depend on the curve, SRS, target instance and precomputation model. No single exponent covers all targets.No verifiable new full-attack exponent or security-level reduction is established.
RSAClassical GNFS has a heuristic subexponential estimate; quantum factoring was already known theoretically.No new practical RSA-2048 attack or lower quantum-resource requirement is demonstrated by these results.

2. Separate arithmetic examples: not attack operation counts or measured performance

The table below defines φ(m)=m^c and evaluates that function only. Actual algorithmic bounds are O_ε(m^(c+ε)); ε, constants and crossover sizes are not accounted for in these examples. Writing φ as 2^k shows a logarithmic function scale only.

Mathematical objectNormalized function-value exampleWhat follows / what does not
#107: complex field, m=10⁶c: 2.371177 → 2.25; φ: 2^47.261 → 2^44.846; log₂φ differs by about 2.415.The function-value ratio is about 5.33. This is not 81.3% fewer actual operations or 2.415 bits less cryptographic security.
#107: finite-exception bound, m=10⁶A separate c=2.258 result gives φ=2^45.005. Exceptional characteristics are uncomputed.Cryptanalytic sparse linear algebra is typically modulo subgroup order r. Whether r is exceptional is unverified; this bound cannot be assumed applicable.
#107: every-fixed-field bound, m=10⁶c=2.371054886006746 gives φ=2^47.259; log₂φ differs from the prior function by about 0.002434.The function-value ratio is about 1.00169. This finely resolved number is not a measurable attack gain.
#109: asymptotic expressions onlyAt lg n=8, the expression ratio is about 1+3.39×10⁻⁵⁵, with log₂ ratio about 4.89×10⁻⁵⁵.The cutoff is huge and the paper uses schoolbook multiplication below it. This substitution does not establish even a tiny cryptographic-size speed gain.
#103: memory functions onlyAt illustrative n=256: (log₂n)²=64 and log₂n=8. The actual space-bound improvement is O(log²n) → O(log n).Machine-dependent constants are uncompared. This is not 64 or 8 work bits, and not three bits saved in an attack.
#142 / #279 / #029 / #002 / #030No full-target-attack resource comparison of 2^a → 2^b is established.Determinism, exactness or structural theorems improve; speed ratios do not follow from those conclusions.
Scale example: even a 16× full-attack speedup changes 2¹²⁸ only to 2¹²⁴. This is not an estimated benefit from these results. Practicality still depends on per-step cost, hardware, parallel efficiency, memory and the attack window.

Ranked by “making target attacks more practical”: currently no entries qualify

Scope: the 8 candidates reviewed on this page and their public materials. None has yet established a large drop in complete attack cost at the security parameters of current on-chain targets, or demonstrated a key-recovery/forgery attack that was previously infeasible and is now feasible. This conclusion does not mean future risk is zero, nor is it an exhaustive judgment on all 722 manuscripts.

Research triage, not a threat ranking:Follow-up on #107 should first identify cryptanalytic cost models that genuinely depend on dense exponent ω, check domain conditions modulo r, and seek competitive finite-size implementations. No gain mechanism for sparse NFS/TNFS is supplied. #109 has a huge cutoff and schoolbook fallback. The word “factoring” does not make #142 or #279 the two greatest practical threats.

Conclusions first: theoretical progress and target attack cost are booked separately

#103 · Spacelog² n → log n

Among polynomial-time deterministic simulations, the workspace bound improves. The polynomial-time randomized log-space program solving the target cryptographic problem is still missing.

#109 / #107 · WorkAsymptotic bounds improved

The model, target field, sizes and attack bottleneck must be verified before this can be carried over to a complete attack.

#142 / #279 · GuaranteesDeterminism / exactness strengthened

Not proven faster, or more economical in space or hardware, than the old schemes.

The 8 candidates assessed in this tableNo new practical break demonstrated

No demonstrated new practical attack on on-chain targets; this does not mean the probability of a future breakthrough is zero.

Uniform notation: attack resources are a vector R=(W, T, M, H, ε). W is total work, T is actual running time, M is working memory, H is the hardware requirement, and ε is the failure/error probability. Time complexity is usually also one dimension of computational complexity, so the two should not be added as independent scores. Compare only old/new values for the same task, the same model, the same parameters and the same success criterion.

This table is conditional on the conclusions of the respective papers holding; the complete proofs were not independently re-verified. The repository states that different results are at different verification stages. “Not established” below means that the public materials do not give that conclusion; it does not amount to a proof that it is impossible in the future.

How much improvement? First the numbers, then whether they can be used for an attack

All numerical ratios are normalized-function examples only:We define and compare values of φ(m)=m^c; actual O_ε bounds also depend on ε and constants. These are not bound values at that size, measured speeds or real resource ratios. Without a target algorithm, full-attack cost cannot be calculated.
ResultMagnitude, examples and complete-attack assessment
#107Exponent bounds improve; function examples are not realized attack speedups

Complex field: ω<2.371177 → ω≤2.25. For normalized φ(m)=m^c at m=10⁶: 2^47.261 → 2^44.846; the log₂φ difference is about 2.415.
Fields outside a finite exceptional set: A separate ω<2.258 bound gives normalized value 2^45.005 at that size. Exceptional characteristics are uncomputed; applicability to cryptographic fields is not assumed.
Every fixed field: ω<2.371054886006746 gives normalized value 2^47.259; the log₂φ difference from the prior function is about 0.002434.
Complete BLS / KZG attack: No target-attack resource ratio or security-bit reduction is established. Sparse systems cost about w·N² operations; dense bounds cannot directly replace that cost.

φ(m) is an illustration function, not an operation count or runtime prediction. Actual bounds are O_ε(m^(c+ε)), with unknown constants and crossover sizes. Differences in log₂φ are not cryptographic security-bit reductions.

#103One log n factor saved in the space bound; no new attack-work bound

Theoretical comparison: With polynomial time retained: deterministic space O(log² n) → O(log n). Constants differ; an actual memory ratio does not follow.
Function values only: At n=256, (log₂ n)²=64 and log₂ n=8. These are function values, not 64 or 8 work bits required by a program, and not three bits saved in an attack.
Cryptanalytic gap: The target BPL program is missing. Such a program would itself already provide a randomized polynomial-time attack.

n is the bit length of the whole program instance. The O(log n) constant is machine dependent; the input is read-only accessible. It does not imply an inability to handle a fixed 256-bit element.

#109Asymptotic theorem advances; no cryptographic-size speed gain established by the paper

Construction in the paper: On a fixed multitape Turing machine: O(n lg n) → O(n(lg n)^(1−κ)), κ=2⁻¹⁸². The cutoff is extremely large; schoolbook multiplication is used below it.
Normalized functions, not performance: At lg n=8 the expression ratio is about 1+3.39×10⁻⁵⁵, with log₂ ratio about 4.89×10⁻⁵⁵. This is not a saving in 256-bit multiplication operations.
Complete cryptographic attack: No target-attack cost reduction or measured speed advantage is established. Generic search counts are not reduced.

The paper defines lg n=max{⌈log₂ n⌉,1}, with n the operand bit length. Theorem 1 and Section 9.8 explicitly note huge constants, cutoffs and a schoolbook fallback. Substituted asymptotic expressions are not finite-size costs.

#142Need for randomness removed; no provable improvement factor in speed / space

Old randomized factoring → new deterministic factoring: The new algorithm needs no random bits. The old algorithms could already factor, in expected polynomial time; no speed percentage can be computed from this.
Running work and memory: No speed or space advantage is proved. Here ℓ=(d+1)⌈log₂p⌉; O(ℓ^(10^12)) is an extremely loose bound. Unconditionality depends on #029’s uniform Hecke zero-free theorem, whose proof was not checked here.
Complete RSA / curve attack: No effective attack reduction, hence no reportable speedup factor.

“Cannot be quantified as faster” is itself the conclusion; no fictitious percentage is used to fill the gap. Derandomization does not reduce the old algorithms’ error rate from some fixed value to zero.

#279Exact worst-case guarantee on an ideal fixed gate set; no resource saving claimed

Prior baseline: Shor-type methods can verify factors and retry. Timed runs can reduce failure probability; unlimited retries need not have polynomial worst-case time.
New guarantee: A fixed finite gate set, ideal success probability exactly one, and polynomial worst-case gate and qubit bounds.
Practical attack resources: No lower RSA-2048 resources are claimed. This is not a classical attack and does not directly replace a curve-DLP algorithm.

Exactness improves a theoretical guarantee; an arbitrarily selected prior failure probability is not attack progress. Physical noise, error correction and runtime still need separate accounting.

#029Proof-chain contribution; no independent attack-speedup figure

#029 → #142: Supports the proof chain for deterministic factoring; the improvement of #142 is not counted a second time.
Complete target attack: No new attack algorithm or resource bound is given; a factor is not applicable.

A target reduction must exist before attack cost ratios can be discussed.

#002Structural theorem strengthened; no comparable old / new key algorithms yet

Time, memory and speed ratio: Not applicable: there is no algorithm solving the target that follows from this result.
Complete target attack: No effective reduction established; no speedup percentage can be filled in.

A theorem’s importance and attack speed are different metrics; without an algorithm, progress toward a break cannot be computed from the theorem’s scope.

#030General modularity scope strengthened; a speed ratio for target key recovery is not applicable

Target CM curves: The relevant modularity was already known; no new key-extraction step.
Complete target attack: No new algorithm or resource bound is given; a speedup factor cannot be computed.

Covering more curves cannot be converted into how much faster private-key recovery is.

Master table: which item changed, and does the complete attack get cheaper as a result?

Green marks the actual theoretical advance claimed by the paper; the “complete attack cost” column is judged separately. Where a structural theorem has no attack algorithm, “not applicable / reduction missing” is stated explicitly and no fictitious complexity is filled in.

Resource changes of candidate results and impact on the complete attack: old → new (conditional on the papers’ conclusions holding)
Result / actual object acted onComputational work W / theoretical time boundSpace M / hardware HWhat clearly changedDoes it carry over to complete attack cost?Potential consequences / remaining key gaps
#103Derandomization / BPL simulationSee corresponding route map ↗Old: Deterministic poly(n) time.
New: Still poly(n); no lower degree or constant proven.
Old: O(log² n) work space.
New: O(log n).
Basis: general simulations that also retain polynomial time.
Major space improvement
Yields L=RL=BPL; the input must still be a randomized polynomial-time, logarithmic-space program. Actual speed not established.
A new target attack cost cannot yet be written down.
A BPL program for target private-key bits is missing; once one exists, it is itself already a randomized polynomial-time attack.
If the target algorithm, reconstruction method and practical cost were all supplied: private keys might be recovered and authorizations forged. What is currently missing is the core cryptanalytic algorithm.
#109Integer multiplication / arithmetic subroutineSee corresponding route map ↗Old: O(n lg n).
New: O(n(lg n)^(1−κ)).
κ=2^−182; fixed multitape Turing-machine asymptotics, with schoolbook multiplication below a huge cutoff.
No lower space bound for a target attack, and no lower memory requirement at secure sizes, is established.Asymptotic work improvement
The normalized function ratio is (lg n)^κ. The construction uses schoolbook multiplication below its cutoff and establishes no cryptographic-size speed advantage.
No new cost bound or measured gain for a complete attack is established.
secp256k1 still needs about √r group operations; the other stages of GNFS / NFS remain.
May affect several arithmetic steps; applicable implementations, crossover sizes and end-to-end gains must be proven before this can be carried over to key or trapdoor recovery.
#107Dense matrix multiplication / companion finite-field resultsSee corresponding route map ↗Old: The paper uses ω<2.371177 as the comparison baseline.
New: Over ℂ, ω≤2.25; outside an uncomputed finite exceptional-characteristic set, ω<2.258; over every fixed field, ω<2.371054886006746.
ω≤c means that for any ε>0, O(m^(c+ε)) field operations are achievable.
No lower memory bound for the target NFS sparse solve is established. Storage depends on the matrix nonzeros, blocking and communication.Dense-operation exponent improvement
Exponent bounds improve; finite-size competitiveness is unestablished. The exceptional set for ω<2.258 is uncomputed; the cryptanalytic modulus r must be checked.
The old sparse solver cannot simply be swapped out.
The commonly used Wiedemann / Lanczos exploit sparsity; no argument is given for lowering the complete NFS/TNFS cost.
Potentially related to BLS / KZG / pairing proofs and some factoring routes. Missing: verification of applicable fields, a gain for sparse solving, and end-to-end accounting.
#142Dense polynomial factoring over prime fieldsSee corresponding route map ↗Old: Randomized expected poly(ℓ).
New: A loose deterministic O(ℓ^(10^12)) bound.
Here ℓ=(d+1)⌈log₂p⌉; this bound establishes no speed advantage. Unconditionality depends on #029’s uniform Hecke zero-free theorem, whose proof was not checked here.
Old and new both have polynomial space upper bounds; it is not established that the new algorithm uses less memory.Determinism guarantee strengthened
The same subtask no longer needs randomness; the old task did not go from unsolvable to solvable.
There is as yet no effective new reduction from a target attack to this task.
This upper bound cannot be written as a new attack cost for RSA / ECDLP.
Only with a separate reduction, secret extraction and feasible cost would signatures or commitments be affected. These attack bridges were also missing in the era of the old randomized algorithms.
#279Exact quantum integer factoringSee corresponding route map ↗Old: Shor-type quantum gate count poly(n).
New: Still poly(n).
No lower gate count, gate depth or runtime established.
Old/New: Qubit counts both have poly(n) upper bounds.
The new scheme is not proven to use fewer logical or physical qubits; error correction and gate speed must be costed separately.
Exact success guarantee strengthened
Old: bounded error that can be amplified; new: fixed finite gate set, ideal-circuit success rate exactly 1.
A theoretical route already exists for the same quantum factoring task.
No real-hardware RSA-2048 attack or practical resource advantage is shown; it cannot be used on this basis to replace the ECC quantum DLP algorithm.
The direct endpoint is RSA factors and private keys; it affects RSA-dependent systems. Commonly used BTC / ETH account signatures use curve cryptography.
#029Primitive-root result / proof input to #142See corresponding route map ↗The uniform Hecke zero-free theorem in #029 (Theorem 1.2), rather than its primitive-root count, is the input to the proof of #142; no old/new operation bounds for a target key algorithm are given.No new space bound or hardware saving for a target cryptographic attack is given.Structural and proof-chain contribution
Explains the theoretical origin of #142; it is not counted separately as an independent attack speedup.
No new bound on attack resources is established.
It still inherits the problems of #142: missing reduction, secret extraction and executable cost.
Potential endpoints depend on reductions established in the future; at present there is no standalone RSA, ECDLP or KZG attack.
#002Exact BSD formula under low Selmer corankSee corresponding route map ↗Old and new compare global arithmetic theorems; there is no pair of comparable old/new finite-field DLP attack workloads.Not a cryptographic solving algorithm; no time or space bound for key recovery can be filled in.Structural theorem strengthened under stated conditions
No algorithm that outputs the hidden scalar d from given G and Q.
Resource comparison not applicable; target reduction missing.
An effective connection from global information to the DLP of a specified point over a finite field must be established.
If a practical DLP algorithm were obtained in the future, curve signatures or pairing systems could be affected; this result has not shown such a route.
#030General modularity over imaginary quadratic fieldsSee corresponding route map ↗The scope of a general structural theorem is extended; no new finite-field DLP operation bound.No key-recovery algorithm with a space bound is given, nor is a lower hardware requirement for a target attack proven.More general structural conclusion
The j=0 CM modularity of the natural lifts of secp256k1 / BLS12-381 / BN254 was already an old result.
No new cost bound for a target attack is established.
An effective algorithm that extracts the specified hidden scalar from modularity information must be given separately.
The generalization adds no demonstrated private-key recovery step for the target curves; an actual cryptanalytic reduction is still missing.

Filters indicate possible research relevance, not an existing effective attack. For #103, n is the program input bit length. For #109, n is the operand bit length and lg n=max{⌈log₂n⌉,1}; for #107, m is matrix dimension; for #142, d is degree and p is a known prime; for #279, the paper uses n=max{128,⌊log₂N⌋+1}. Polynomial bounds in different parameters cannot be used as a speed ranking.

Starting from the final target: the attack-resource baselines that can be written down today

These are representative public routes; they are not claimed to be the optimal implementation for every target and every kind of hardware. The existence of a theoretical algorithm also does not mean it can run at target security sizes in usable time.

Final attack taskOld baseline / workSpace, hardware and timeEstablished changes after these candidate resultsConsequences on success
secp256k1 private-key recovery
Classical route
Generic Pollard rho takes about √r group operations; r is about 2²⁵⁶, so the order is about 2¹²⁸, allowing existing constant-factor optimizations. This is not an unconditional security lower bound.SourcesThe bit cost of each group operation must be recorded; rho can be implemented with low storage, and distributed versions must further distinguish point storage and communication. Runtime depends on parallel throughput and cannot be converted directly from operation counts into GPU-days.No new, lower target cost bound is established. #109 changes an asymptotic arithmetic bound, not a demonstrated cryptographic-size cost; its construction uses schoolbook multiplication below a huge cutoff; #142 / #103 and others lack a target reduction or program.The corresponding ECDSA / Schnorr authorizations can be forged. BTC spending rights and ETH EOA control tied to public or recoverable public keys may be lost.
BLS / KZG / pairing proofs
Classical route
One can examine generic search for the source-group DLP, or NFS/TNFS after transferring to the target extension field. The specific curve, field structure and attack instance determine the cost; a single generic number cannot be written for all of them.Parameters · NFSIncludes relation collection, sparse solving at about w·N² field operations (row weight w), descent, storage and communication. Precomputation and per-instance costs must be accounted for separately.#107 has not established a gain for the complete sparse attack; the other candidates give no new practical bound for target keys, the SRS trapdoor or forgery algorithms.Recovering the corresponding signing key allows BLS messages to be forged; recovering the τ of the corresponding SRS can break KZG binding; the impact on a specific ZK system depends on its assumptions and verifier.
RSA integer factoring
Classical route
For general, properly generated large semiprimes, the representative heuristic GNFS bound is used: L_N[1/3,(64/9)^(1/3)]. It is not a proven optimal lower bound.Original GNFS analysis · ImplementationL_N[α,c]=exp((c+o(1))(ln N)^α(ln ln N)^(1−α)). Sieving, sparse solving, disk and communication costs must be accounted for with concrete parameters.#142 gives no new effective reduction for integer factoring; #109 / #107 show no end-to-end practical breakthrough on RSA-2048.Once the factors are recovered, the RSA private key can be computed, breaking RSA-dependent signature/encryption systems; on-chain consequences depend on the specific components that use RSA.
RSA / curve DLP
Quantum routes
Shor-type algorithms have long provided a poly(n) quantum-time theoretical route; the circuit resources for integer factoring and for curve DLP are computed separately.SourcesLogical qubits, physical qubits, gate count, gate depth, gate speed, error correction and failure budget must all be distinguished. poly(n) cannot be converted directly into real-world executability.What #279 strengthens is the exactness of integer factoring; it shows no resource savings and cannot be used directly as a new resource estimate for curve DLP.If a practical quantum attack at target sizes were realized, the corresponding private keys or trapdoors could be recovered; concrete on-chain consequences are still judged per primitive and protocol.

Why can’t a+b+c be used directly to measure the size of an advance?

First break the same attack into its computational steps

W_total = W_reduction + W_subroutine + W_secret-extraction + W_other-stages

These W must be converted to comparable units of work. If an effective reduction already exists, one of the subroutines can be replaced and the sum recomputed. If the reduction does not exist, the other terms are not known constants, and it cannot be assumed that only a few small engineering steps remain.

In sequential execution, peak memory is usually the maximum over the stages, counting data retained at the same time; in parallel execution, concurrent storage and coordination overhead must also be added. Hence M cannot be added directly to W or T.

A large speedup of a substep may also affect the whole only slightly

T_new / T_old ≈ (1−f) + f/s

Assuming the same route and the same hardware, if a step that originally took 10% of the time is sped up 100×, the whole is sped up only about 1.11×; if it originally took 90%, the whole is sped up about 9.17×.

This is a hypothetical example illustrating how bottlenecks propagate, not a measured figure from the papers above. When only memory is reduced, a speedup cannot be derived automatically from this formula; it may improve deployability, or it may trade more time for space.

The accurate conclusion for #103: The space-saving aspect is a major theoretical advance; there is no new conclusion on the work or actual time of a complete break, because the target BPL solver has not been given. The gap here is the core algorithm, not “most of the break is done and only deployment remains”.

Final impact: what could break, and what cannot be derived directly?

Account signatures → asset control

Actually recovering a secp256k1 private key allows forging that key’s ECDSA / Schnorr signatures. EOA takeover or spending BTC assets further requires that the corresponding public key be obtainable, that the assets still be spendable, and that the other conditions of the script or wallet be satisfied.

BLS → authenticity of consensus messages

Actually recovering validator signing keys, or achieving a valid forgery, can threaten message authenticity. Whether finality/safety is affected depends on the stake weight that can be forged and on the specific protocol conditions.

KZG → commitment binding and related proofs

Recovering the corresponding SRS trapdoor, or constructing a valid false opening, may break blob commitment binding and the verification that depends on it.EIP-4844 uses KZG; concrete consensus or asset consequences further require an upper-layer exploitation path.

ZK / RSA → judge each specific system individually

ZK is a class of protocols, not a single cryptographic assumption; pairing/KZG attacks cannot be generalized to all ZK. RSA private-key recovery affects services and protocols that use RSA and cannot be directly recast as recovery of commonly used curve account keys.

Sources and review scope

Mathematical statements come from the sources below; target-attack impact is this report’s analysis. For #107 we list three bounds, over ℂ, outside an uncomputed finite exceptional-characteristic set, and over every fixed field, with separate applicability conditions. Neither all 722 manuscripts nor full proofs were audited.

  1. OpenAI Math full catalog and repository notes. The repository states that the manuscripts have varying degrees of verification; this map discusses attack implications on the basis of “even if the stated theorems hold”.
  2. #142 finite-field polynomial factoring, original paper.
  3. #279 exact quantum factoring, original paper and formalization scope.
  4. #029 primitive roots, original paper.
  5. #107 finite-exception companion (Corollary 14.1); #107 matrix multiplication, main paper, companion paper for every fixed field and formalization scope.
  6. #109 integer multiplication, original paper.
  7. #103 derandomization, original paper.
  8. #002 BSD, original paper and #030 modularity, original paper.
  9. IETF pairing-friendly curves draft: G₁, G₂, Gₜ and finite-field parameters of BLS12-381.
  10. Guillevic: the four stages of finite-field discrete log with NFS-DL; linear algebra is only one of them.
  11. TNFS discrete-log research: sparse relation matrices and block Wiedemann; CADO-NFS official implementation.
  12. Practical ECC security analysis: Pollard rho and existing endomorphism constant-factor optimizations; Target security level of BIP-340.
  13. Shor’s original paper on quantum factoring and discrete-log algorithms.
  14. EIP-4844: blobs, KZG proofs and verification.
  15. BIP-340: secp256k1 Schnorr and BIP-341: Taproot rules.
  16. Nisan 1994: polynomial-time, O(log² n)-space deterministic simulation of BPL.
  17. OpenAI Math repository and verification-scope notes.

Overall map: different results feed into shared attack capabilities and shared consequences

Click any paper to see its connections; the “Old SOTA → new-result replacement map” below shows how the old algorithms actually proceed and at which step a new paper could plug in.Grey dotted lines mark only target associations for which no attack route is currently known.

Blue solid line: published connection / proof dependencyGrey dotted line: no known route yet; target association onlyOrange dashed line: cost / hardware gap of an existing algorithmGreen solid line: known sufficient implication once the premises hold
Download full-map SVGSee SOTA replacement routes ↓
Public results / old baselinesIntermediate links and primary gapsShared attack capabilities (not yet practically demonstrated)Affected cryptographic primitivesCommon endpoints: bad on-chain outcomesProof dependencyA primitive root generates the whole group, which is a different task from computing the discrete logarithm of a given public element. #029 provides proof support for #142; there is no standalone key-recovery algorithm for currently deployed curves. Nature of the gap: D4, a new attack reduction.#029 Primitive roots / zero-free regionMath proof input to #142Factors polynomials in 𝔽ₚ[x] that are given explicitly. No effective reduction to ECDLP, RSA or KZG forgery is provided. Attack-specific thresholds: 0/3; this does not mean the probability of a future break is 0%.#142 Finite-field polynomial factoringDeterministic; old randomized algos existThe complex-field bound is ω≤9/4. Separate bounds give ω<2.258 outside an uncomputed finite set of characteristics and ω<2.371054886006746 over every fixed field. NFS-DL usually solves a sparse system modulo r at about w·N² field operations (row weight w); no full-attack gain mechanism from the new dense bounds is established.#107 Matrix multiplicationComplex field 9/4; also all-field boundInteger arithmetic is a subroutine of curve operations, Pollard rho and NFS, but a faster single step does not reduce the number of search steps for the secret scalar. No practical attack on current security parameters has been demonstrated.#109 Integer multiplicationκ = 2⁻¹⁸²; asymptotic theoretical boundOne would first have to prove that tasks such as deciding bits of the target private key have a randomized small-space polynomial-time program. If that were done, the randomized program itself would already pose a threat; #103 does not provide it. Attack-specific thresholds: 0/3.#103 L = RL = BPLDerandomizes existing small-space programsFormulas for the global rank, L-function and Sha do not output the d in Q=dG in a finite group. An entirely new effective reduction is needed, controlling the heights of lifted points and the computation size. Attack-specific thresholds: 0/3.#002 BSD exact formulaRationals; low Selmer coranksecp256k1, BLS12-381 and BN254 are all CM curves with j=0, and the CM modularity of their natural characteristic-zero lifts is a classical case. The new general conclusion of #030 gives these curves no key-extraction increment; the bridge from the structural correspondence to an effective ECDLP is still missing.#030 Elliptic-curve modularityImag. quadratic fields; local-param matchOn a sufficiently large and accurate quantum computer, a theoretical path to computing elliptic-curve discrete logarithms has long existed. The theoretical algorithmic route existed before the release; practical fault-tolerant resources still have to be met.Existing Shor-type discrete logOld baseline; not a new #279 resultQuantum integer factoring with success probability 1 on an ideal circuit over a fixed finite gate set; the quantum theoretical attack on RSA has existed since Shor. This main theorem does not give ECC private-key recovery.#279 Exact quantum integer factoringNo practical resource reduction claimedD4: a new mathematical reduction is needed, and the explicit polynomial representation must not blow up exponentially. Even if such a reduction held, the old randomized factoring algorithms might already suffice, so the security increment of #142 would still need a separate argument.Gap: target attack → polynomial factoringReduction size / complexity must be boundedNFS/TNFS routes already exist, but #107 establishes no effective speedup. Block Wiedemann/Lanczos commonly solve the sparse system modulo r in about w·N² field operations (row weight w). Relation collection, individual descent, memory and full costs must also be counted.Old TNFS attack; new gain not establishedSparse linear algebra ≠ dense matrix mult.#109 can connect to existing attack subroutines, but actual speedup at target parameters and the end-to-end cost must be shown. The threshold of about √r group operations for generic curve discrete-log search has not been removed. No competitive finite-size mechanism is supplied; the construction uses schoolbook multiplication below its enormous cutoff. Usable constants and crossover sizes require further algorithmic work (D3–D4), not routine benchmarking. A devastating attack gain would additionally need a search/factoring breakthrough (D4).Known arithmetic link + practical-gain gapAsymptotic arithmetic gain; search size unchangedBPL⊆P was known before #103. If deciding bits of the target private key were in BPL and the private key could be recovered from it, old knowledge would already give a deterministic polynomial-time path; the novelty of #103 lies in space, not in supplying an algorithm that solves the target. There is no practical cost conclusion yet.Gap: target problem has a BPL programMust also recover key from decisions#002/#030 do not derive a solver for elliptic-curve discrete logarithms over finite fields from global number-theoretic correspondences. One would have to establish effective lifting, representation, control of point heights, and an algorithm and complexity for extracting d; this must not be conflated with NFS-DL for the multiplicative group of a finite field.Gap: global structure → effective ECDLPLift, representation, point height, computeThe theoretical algorithm exists; what is needed is enough logical/physical qubits, error correction, gate fidelity, depth and runtime. This is a large engineering and validation problem; a lowered threshold cannot be inferred from #279.Gap: usable fault-tolerant quantum resourcesReal-hardware validation on target curve DLP#279 does not claim to reduce the practical resources for targets such as RSA-2048. Factoring at actual security sizes would have to be demonstrated; the existence of an ideal circuit must not be treated as a real-world large-GPU-cluster attack.Gap: RSA fault-tolerant resources + hardware validationQuantum factoring already had an algorithmSeveral candidates converge here. Executable cost and reproducible experiments are required; at present these papers do not provide such a classical attack. Recovering d is a sufficient condition for breaking both ECDSA and Schnorr; protocol-specific forgeries may also be other routes.Practical secp256k1 private-key recoveryCapability node: Q=dG → dDiscrete logarithms in G₁/G₂ of a pairing curve can be transferred to the corresponding Gₜ. Being able to solve the target DLP at practical cost can recover keys or the hidden scalar in the public parameters. This must be checked curve by curve and system by system; one cannot generalize from one curve to all ZK.Practically solve target pairing-curve DLPPer curve: BLS12-381 / BN254, etc.Directly affects RSA-based systems. BTC / ETH native account signatures, BLS and KZG do not use RSA factoring as their security assumption.Practically factor target RSA modulusN → p, q → private keyRecovering the private key suffices to sign new valid authorizations. Ethereum EOA and Bitcoin ECDSA use cases are each affected; addresses, public-key exposure and the exploitable window determine the scope of victims.ECDSA authorization forgeableETH EOA / BTC ECDSA outputsThe same secp256k1 private-key recovery capability also suffices to break Schnorr signatures. Bitcoin Taproot uses Schnorr, so one cannot label only ECDSA.Schnorr authorization forgeableBTC Taproot, etc.When a validator’s secret scalar can be recovered, the corresponding signatures can be forged. The concrete impact on consensus depends on the effective stake weight that can be forged, message types, timing and protocol rules.BLS validator signatures forgeableTarget: Ethereum consensus BLSComputing τ from [τ]G in the SRS is one sufficient route to forging KZG point-evaluation proofs. DLP is not a necessary condition for all attacks; KZG security involves structural assumptions such as q-SDH, and the high powers in the SRS must also be included in the security analysis. The diagram draws this sufficient route.Recover KZG trapdoor; forge openingsSufficient route: recover SRS trapdoor τFor the corresponding trusted-setup systems, recovering the trapdoor is a known sufficient attack route, e.g. the relevant Groth16 / KZG-PLONK. The curve, SRS and verifier used must be specified; this cannot be generalized to all ZK, all curves or STARKs. Concrete on-chain losses still require system-level conditions.Related ZK soundness can failOnly same-curve / matching trusted-setup systemsKnowing the complete factorization of the modulus allows the RSA private key to be derived. It is listed separately here to avoid the misconception that it directly causes BTC/ETH native signatures to fail.RSA signature / decryption security failsSide branch: RSA-dependent systemsWhen signature authorizations for the relevant public key/address are forged, the account’s assets can be spent illegitimately. The victim conditions for contract wallets, multi-condition setups and accounts with unexposed public keys still need to be assessed separately.ETH EOA accounts can be taken overPubkey available; authorization conditions metWhen a signature for the corresponding spending path can be forged, the attacker can illegitimately spend that UTXO. Address type, whether the public key is public, additional script conditions and the time window affect the scope.Corresponding BTC UTXOs can be stolenPubkey available; spending conditions metForgery of validator signatures at sufficient scale can threaten consensus security. The failure of a single BLS key does not automatically equal network-wide consensus failure, nor does it directly equal the assets of arbitrary EOAs being transferred away.Ethereum consensus security impairedWith enough stake weight and protocol conditionsA false KZG opening may deceive blobs or applications that rely on point-evaluation proofs. Whether this further triggers consensus problems, data-availability failures or losses must be verified along the specific path.Trust in blob / commitment checks impairedData binding / point-evaluation proofs spoofableIf a specific on-chain verifier accepts a proof of an incorrect state transition, the rollups or bridges relying on it may accept illegitimate states or withdrawals; this consequence requires system-level exploitation conditions.Related rollups / bridges can be harmedFalse proof accepted and protocol exploitableAffects the corresponding identity, certificate or encryption services. This does not claim that all TLS uses RSA key exchange, nor is it a direct break of BTC/ETH native signatures.RSA-dependent services impersonated / decryptedNot the main BTC / ETH signature route
Select a starting point or a common endpoint

The original overall-map structure has been restored. After you click a paper, the replacement map below updates in sync to show its relationship to the old SOTA; a new mathematical result is not necessarily a replaceable node in an attack route.

Summary table: old resources → new resources → impact on the complete attack

A separate comparison of the 8 results’ computational work, space/hardware and success guarantees, and of whether subtask improvements can propagate to a final key-recovery or forgery attack.

Open the standalone complexity impact master table →

Old SOTA → new result: which step exactly is replaced?

Each result gets one diagram showing the relevant targets: old and new subroutines are shared, while the different baselines and consequences of RSA and curve attacks are kept separate. If a paper cannot yet be plugged into an attack route, the break point is drawn.

Known in theory / given by paper: an algorithm or theorem exists for the corresponding mathematical taskNot practically demonstrated / reduction missing: cannot yet be used to carry out the target attack

How to read “distance to the endpoint”

0 / 3 thresholds#142 → current BTC/ETH signatures, BLS, KZG: the count of closed attack-specific key gaps is 0/3.
Old theoretical route already existedShor-type quantum algorithms → RSA / elliptic-curve discrete log: the theoretical path has long existed; practical hardware and cost must be judged separately.
No new practical attack demonstratedOn the thresholds below, #142 and #279 have not demonstrated any newly added executable attack path against current on-chain primitives.
Distance is expressed by threshold status; each hop is not converted into a probability of a break or a remaining research workload.Here “a new attack algorithm usable against the target primitive appears”, “executable cost at the target security parameters is reached” and “a reproducible attack instance is given” are treated as three thresholds. Showing 0/3 only says that this batch of papers has not yet crossed any of them; it cannot be inferred that the probability of a future breakthrough is 0%. The first threshold is usually the hardest; the three thresholds are not equally weighted and cannot be converted into remaining workload or probability of a break.
Hypothetical future eventChecklist scaleCorrect reading
Only papers like #142; no reduction for a target attack yet0 / 3 thresholdsNot even the first bridge toward an executable on-chain attack exists.
Someone proves an effective reduction from target DLP / KZG forgery to the new algorithm1 / 3 thresholdsOnly one of the three formal thresholds has been passed; the remaining cost may still be astronomical.
Cost at secure sizes also reaches a usable range2 / 3 thresholdsA real danger; assumptions, code and attack models need to be re-examined immediately.
Forgery or key recovery reproduced under real rules3 / 3 thresholdsAn executable attack on that target has been demonstrated; the scope of victims still depends on the target protocol.

Item-by-item evidence: each result’s contribution, gaps and difficulty

Each row is a conditional path. Blue boxes mark public results or known connections; dashed boxes are links not yet filled in. Existing attack algorithms may also be non-executable because their cost is too high. The red endpoints require every condition along the chain to hold and have not been demonstrated by these papers.

Published mathematical resultMissing major breakthroughExecutable attackBad on-chain outcome

Path A · #142 → Bitcoin / Ethereum account signatures

Attack gaps: 0 / 3 thresholds No target-attack gain over existing randomized factoring is shown for #142

#142: factoring polynomials in 𝔽ₚ[x]

The input is a known prime p and an explicitly given polynomial; the novelty is determinism.

→
Gap 1: a new reduction

Turn computing d from a secp256k1 public key Q=dG into a polynomial factoring problem of controllable size. None exists at present.

→
Gap 2: practical complexity

For a 256-bit target, compute d within available hardware and time; the theoretical upper bound of #142 is far from enough.

→
Bad outcome: forged account authorization

Whoever holds d can sign for ETH EOAs / BTC ECDSA or Taproot Schnorr outputs with exposed public keys and move the spendable assets.

Gap 3: Public, reproducible verification of a secp256k1 attack, including concrete memory and runtime.Difficulty: Gap 1 is a major breakthrough that would rewrite the state of classical elliptic-curve discrete logarithms; Gaps 2 and 3 each still have engineering/validation thresholds.Key counterfactual: Even if someone found Gap 1, the existing randomized algorithms for factoring polynomials in 𝔽ₚ[x] already exist, so the discovery could not automatically be credited to #142.
Where we stand today: 0/3; “#142 has been proved” cannot be counted as one completed hop of an ECDSA attack.

Path B · #142 → Ethereum consensus BLS signatures

Attack gaps: 0 / 3 thresholds

#142: finite-field polynomial factoring

There is no theorem that takes a BLS public key as input and outputs a signature or private key.

→
Gap 1: attack BLS12-381

Solve the discrete log from public validator keys, or find another effective BLS forgery algorithm.

→
Gap 2: executable cost

Recover keys / forge signatures in bulk within a time window exploitable on the network.

→
Bad outcome: forged validator messages

May undermine vote authenticity, finality and consensus security; the actual consequences depend on the effective stake weight compromised and on protocol conditions.

Gap 3: Show a forged message accepted under the real verification rules.Difficulty: The first hurdle is likewise a major mathematical breakthrough and cannot be derived directly from the words “elliptic curve” or “finite field”.
Where we stand today: 0/3; BLS being broken also does not mean ETH at arbitrary addresses is taken directly.

Path C · #142 → KZG → Ethereum blobs / KZG-dependent ZK

Attack gaps: 0 / 3 thresholds

#142: finite-field polynomial factoring

“Polynomial” shares its name with KZG polynomial commitments, but the tasks are different.

→
Gap 1: break commitment binding

For example, recover the trapdoor τ from the KZG public parameters, or directly construct an incorrect opening that passes verification.

→
Gap 2: actually forge a proof

Feasible on BLS12-381, current parameters and a concrete verifier.

→
Bad outcome: commitments can be spoofed

The binding between blob data and commitments, and point-evaluation proofs, may fail; KZG-dependent applications and certain proof systems can be affected.

Gap 3: Show a false claim being accepted in the real verification path of EIP-4844 / the target ZK system.Difficulty: There is currently no effective bridge from #142 to the trapdoor τ or to a fake opening.Consequence boundary: A KZG failure does not automatically equal “the entire Ethereum consensus collapses”, still less all assets being stolen; it depends on how the broken verification step is used by upper-layer protocols.
Where we stand today: 0/3; EIP-4844 does use KZG, but #142 provides no proof that could deceive it.

Path D · #279 → RSA (side branch, not the main BTC/ETH signature)

Quantum theoretical algorithm: existed before release → still an existing route after release Large-scale practical attack: fault-tolerant hardware and resource validation still missing

#279: exact quantum integer factoring

Fixed finite gate set, ideal circuit, success probability 1; claims no practical resource reduction.

→
Gap 1: a large enough fault-tolerant quantum machine

The logical gates, error correction and runtime required to reach target RSA parameters.

→
Gap 2: real-hardware demonstration

Successfully and reproducibly factor a key of real security size.

→
Bad outcome: RSA keys fail

Directly affects RSA-dependent systems; BTC / ETH native account signatures do not rely on RSA.

Key counterfactual: Shor long ago provided quantum polynomial-time factoring. #279 is a strengthening of the theoretical form; it does not move RSA from “quantum-theoretically secure” to “quantum-theoretically insecure”, nor does it give classical factoring.
Where we stand today: Quantum factoring was already known; #279 shows no practical attack-resource reduction. No credible research-progress percentage is available.

Path E · Quantum computing → ECDSA / Schnorr / BLS / KZG (as a comparison baseline)

The starting point is the existing Shor-type algorithm, not an ECC main theorem of #279

Existing quantum discrete-log algorithm

On a sufficiently large ideal quantum computer, elliptic-curve discrete logarithms can be computed.

→
Gap: actual fault-tolerant scale

The required physical qubits, error correction, gate fidelity and runtime must all meet the target.

→
Recover private key / trapdoor, or forge

Targeting secp256k1 signatures, BLS keys and KZG parameters respectively.

→
Corresponding bad on-chain outcomes

Account theft via forged signatures, forged consensus messages, impaired commitment integrity; each depends on its own attack conditions.

Logic: The quantum theoretical threat is real, pre-existing knowledge; #279 discusses integer factoring and must not be mis-drawn in the diagram as a new starting point for ECC attacks.Reality: A theoretical algorithm being valid and its being runnable on available hardware today are two different questions.
Where we stand today: The theoretical route already exists; a real-world large-scale attack is not demonstrated by #279.

Path F · #029 Hecke zero-free theorem → #142 → account signatures / BLS / KZG

Proof dependency exists; attack bridge missing

#029: primitive roots and zero-free regions of Hecke L-functions

Proves that qualifying integers a generate the entire multiplicative group modulo infinitely many primes; its zero-free region theorem is cited by #142.

→
Known link: supports the proof of #142

This step is a mathematical dependency of the paper. What results is deterministic finite-field polynomial factoring, not computing a private key from a public key.

→
Gap: from target key to a solvable problem

An effective attack reduction against secp256k1 / BLS12-381 still has to be established, and the total cost made executable.

→
Conditional endpoint: forged signing / fake votes / fake openings

These bad outcomes are reached only by crossing the same attack thresholds as Paths A–C.

Why it is stuck: Intuition: knowing what generates a group is not the same as being able to write a given element as a particular power of the generator. Cryptographic protocols publish the generator anyway. Even finding primes with smooth p−1 cannot change the already fixed prime-order subgroup r of current curves; conflating the base field p, p−1 and the subgroup order r leads to a wrong attack route.
Gap difficulty: Primary gap D4: a new mathematical algorithm that solves the target DLP or forgery is needed; the difficulty of making it practical afterwards depends on that algorithm.
Original paper: Theorems 1.1, 1.2; the citation relationship with #142.
Where we stand today: Attack-specific thresholds: 0/3; the solid line #029 → #142 does not count as key-attack progress.

Path G · #107 matrix multiplication → finite-field DLP → BLS / KZG / pairing-based ZK

Old NFS route exists; attack gain from #107 not established

#107: faster matrix arithmetic

Main complex-field bound ω≤9/4; in addition, outside finitely many unspecified exceptional characteristics, ω<2.258; and for every fixed field, ω<2.371054886006746. The latter improves on the old bound 2.371177 cited by the paper by about 1.2×10⁻⁴.

→
Known link: linear algebra of finite-field DLP

The old pairing and NFS/TNFS attack routes exist, but there is as yet no effective gain mechanism by which the dense multiplication bound of #107 would help their sparse solving stage.

→
Gap: end-to-end cost actually goes down

One must verify applicability to the target field, sparse-matrix/memory overhead, and the costs of relation collection and individual-target descent, and show that current parameters are attackable.

→
Conditional endpoint: recover keys / trapdoor

If the target-group DLP were executable, BLS keys or the KZG trapdoor could be recovered, in turn threatening consensus signatures, commitments and the corresponding proof systems.

Why it is stuck: NFS-DL solves a sparse system modulo r. Wiedemann/Lanczos commonly cost about w·N² field operations (row weight w). An exponent comparison alone does not settle finite-size cost: comparing N^c with w·N² requires N, w, ε, constants, crossover sizes and storage costs. The relevant theorem must apply modulo r; the complex-field 2.25 bound cannot simply be transferred. No gain for this stage is established, and this does not rule out future sparse, dense or hybrid solvers. Full attacks still require relation collection, descent, memory and finite-size costs. The low-embedding-degree pairing route does not directly apply to secp256k1.
Gap difficulty: No practical gain mechanism is known yet: one would first have to find a new algorithm applicable to sparse solving or to another critical stage, and then estimate the end-to-end cost; progress on the dense exponent cannot be counted as attack progress.
Original paper: main paper Theorem 1.1; all-field companion paper Theorem 1.1; formalization scope.Pairing specification · Four stages of NFS-DL · Sparse solvers
Where we stand today: Existing attack routes remain; #107 shows no new executable attack at current parameters or measured end-to-end speedup.

Path H · #109 integer multiplication → existing cryptanalysis → BTC / ETH / BLS / KZG

Arithmetic link exists; the critical search size is unchanged

#109: integer multiplication below n log n

The model is a fixed multitape Turing machine, κ=2⁻¹⁸². Improves the asymptotic upper bound for n-bit multiplication; no practical crossover point is given.

→
Known link: finite-field arithmetic in every step

Curve group operations, Pollard rho, NFS and so on use integer/finite-field arithmetic; the subroutine connection was always there.

→
Gap: actual savings large enough to cross the security threshold

A somewhat faster single step does not reduce the roughly √r group operations of Pollard rho, nor does it automatically eliminate costs such as relation collection in NFS.

→
Conditional endpoint: actually recover keys / forge

Only if the end-to-end cost drops into a usable range could account theft via forged signatures, BLS forgery or a KZG break result.

Why it is stuck: Theorem 1 states that constants and cutoffs are extremely large; Section 9.8 uses schoolbook multiplication below the cutoff. No cryptographic-size speed gain is established. Substituting n=2048 gives an expression ratio of about 1+3.9×10⁻⁵⁵: a function-value ratio, not an improvement factor or performance measurement. Generic curve-search counts are not reduced.
Gap difficulty: Gap: no competitive finite-size mechanism is supplied. Routine benchmarking cannot turn this asymptotic construction into a practical speedup. A usable algorithm would require further work on constants and crossover sizes (D3–D4); a devastating attack gain would also require a substantive search/factoring breakthrough (D4). These difficulty labels are qualitative research judgments.
Original paper: abstract, §1, §9.8; the fixed model and the range of κ.
Where we stand today: The arithmetic subroutine is relevant, but no practical speedup or new executable attack at target security parameters is shown.

Path I · #103 derandomization → assume the target DLP is already solvable in small space → signature failure

No algorithm solving the target; if the gap were filled, the old randomized algorithm would already be a threat

#103: L = RL = BPL

Turns existing polynomial-time, logarithmic-work-space randomized decision programs into deterministic ones.

→
Gap 1: first find a small-space program solving the target

For example, prove that the decision problem for each bit of the private key lies in BPL and that the private key can be reconstructed from the decisions. #103 gives no such cryptanalysis.

→
Gap 2: executable cost at target parameters

Deterministic polynomial time does not guarantee practicality; runtime, the precision parameter and the constants of the specific program must be checked.

→
Conditional endpoint: recover private key and forge signatures

Only if solving the specified target and practicality both hold, and it then passes real verification, does it lead to the failure of account or BLS keys.

Why it is stuck: Key counterfactual: if Gap 1 were filled, BPL⊆P was already known before #103; the original BPL program would already imply deterministic polynomial-time solvability. The novelty of #103 lies in the space bound; the breakthrough in the target algorithm would not come from it. #103 does not prove P=NP, nor does it make all hard problems solvable in small space. The paper’s precision parameter q generally brings 2^O(q) time; one cannot ignore the parameter and then claim general fast exact solving.
Gap difficulty: Primary gap D4: proving that secure-curve DLP / private-key-bit decision lies in this algorithmic class amounts to first finding a breakthrough cryptanalysis.
Original paper: Theorems 1.1, 1.2; the model and time bounds of §1.
Where we stand today: Target-attack thresholds via #103: 0/3. The missing target BPL program is itself the core attack algorithm.

Path J · #002 BSD formula → [missing effective DLP algorithm] → curve signatures

Objects are related; the bridge from global structure to finite-group private keys is missing

#002: BSD under low Selmer corank

Gives the rank, finiteness of Sha and the exact leading-term formula for elliptic curves over the rationals, under a low-corank condition.

→
Gap 1: derive a target private-key algorithm from the formula

d must be extracted from G and Q=dG in the finite field. Knowing the rank, L-values or the global formula does not directly give d.

→
Gap 2: lifting and computation size under control

If lifting to a rational curve is used, one must control the point heights, the representation, the amount of computation and the step back to the finite-field solution.

→
Conditional endpoint: corresponding signatures / commitments fail

Only if the target curve DLP can really be solved at practical cost would ECDSA, Schnorr, BLS or KZG be further threatened.

Why it is stuck: “Curve rank” describes the global structure of the group of rational points; the hard problem behind on-chain public keys is the scalar d in a specified finite group. Lifting a finite-field public key to some rational curve does not, for free, express it as a known combination of small-height generators. The paper has no such reduction, no algorithm at target security parameters and no running cost. The low Selmer corank hypothesis concerns the lifted curve over the rationals; even if the hypothesis is satisfied, an algorithm that effectively lifts G and Q and extracts d is still missing.
Gap difficulty: Primary gap D4: the global arithmetic structure would have to be turned into an effective finite-field DLP solver, with a complexity proof.
Original paper: Theorem 1.1; the low Selmer corank hypothesis and the scope of the formula.
Where we stand today: Attack-specific thresholds: 0/3; a proven structural formula does not mean key solving has completed one hop.

Path K · #030 modularity → [missing effective DLP algorithm] → curve signatures

Structural correspondence holds; it does not output the hidden scalar

#030: modularity of elliptic curves over imaginary quadratic fields

Establishes a correspondence with automorphic representations, matching data such as local parameters and L-functions.

→
Gap 1: make the structural correspondence solve for d

One would need to prove that the correspondence can efficiently extract d from the finite-field target Q=dG, rather than merely yield curve-level information.

→
Gap 2: target curve and algorithm executable

Representation, lifting and computational cost must also be controlled, and validated at secp256k1 / BLS12-381 parameters.

→
Conditional endpoint: corresponding key recovery / forgery

Only if an executable DLP attack is actually obtained would the on-chain damage on the right occur.

Why it is stuck: The Frobenius or local point counts appearing in the paper describe the curve. secp256k1, BLS12-381 and BN254 are CM curves with j=0, and the CM modularity of their natural lifts is a classical case. Knowing #E(𝔽ₚ), the group order or the modularity correspondence is not the same as knowing the discrete logarithm of some public key with respect to the generator. Curve point counts could always be computed with existing algorithms such as Schoof’s; the new modularity conclusion gives no additional key-extraction step.
Gap difficulty: Primary gap D4: deriving a practical DLP algorithm from the modularity correspondence is a major breakthrough not yet provided, not a direct application of the theorem.
Original paper: Theorem 1.1; local parameter / L-function correspondence.
Where we stand today: Attack-specific thresholds: 0/3; there is currently no quantifiable key-recovery increment.

Side-by-side comparison of candidate results

Six additional candidates beyond #142 and #279 are included, for eight results in total. This compares current evidence, not future break probabilities.

ResultReal connection to cryptographic attacksBiggest unsolved problemCurrent assessment
#029 Primitive-root theoremProof dependency exists; attack bridge missingPrimary gap D4: a new mathematical algorithm that solves the target DLP or forgery is needed; the difficulty of making it practical afterwards depends on that algorithm.Attack-specific thresholds: 0/3; the solid line #029 → #142 does not count as key-attack progress.
#107 Matrix multiplicationOld NFS route exists; attack gain from #107 not establishedNo practical gain mechanism is known yet: one would first have to find a new algorithm applicable to sparse solving or to another critical stage, and then estimate the end-to-end cost; progress on the dense exponent cannot be counted as attack progress.Existing attack routes remain; #107 shows no new executable attack at current parameters or measured end-to-end speedup.
#109 Integer multiplicationArithmetic link exists; the critical search size is unchangedGap: no competitive finite-size mechanism is supplied. Routine benchmarking cannot turn this asymptotic construction into a practical speedup. A usable algorithm would require further work on constants and crossover sizes (D3–D4); a devastating attack gain would also require a substantive search/factoring breakthrough (D4). These difficulty labels are qualitative research judgments.The arithmetic subroutine is relevant, but no practical speedup or new executable attack at target security parameters is shown.
#103 DerandomizationNo algorithm solving the target; if the gap were filled, the old randomized algorithm would already be a threatPrimary gap D4: proving that secure-curve DLP / private-key-bit decision lies in this algorithmic class amounts to first finding a breakthrough cryptanalysis.Target-attack thresholds via #103: 0/3. The missing target BPL program is itself the core attack algorithm.
#002 BSD formula → [missing effective DLP algorithm] → curve signaturesObjects are related; the bridge from global structure to finite-group private keys is missingPrimary gap D4: the global arithmetic structure would have to be turned into an effective finite-field DLP solver, with a complexity proof.Attack-specific thresholds: 0/3; a proven structural formula does not mean key solving has completed one hop.
#030 modularity → [missing effective DLP algorithm] → curve signaturesStructural correspondence holds; it does not output the hidden scalarPrimary gap D4: deriving a practical DLP algorithm from the modularity correspondence is a major breakthrough not yet provided, not a direct application of the theorem.Attack-specific thresholds: 0/3; there is currently no quantifiable key-recovery increment.
#107 also has no established attack gain: Dense matrix multiplication and sparse NFS solving have different complexities. An effective algorithmic connection should be seen first, before discussing any impact on the security cost of target curves. Among the other candidates, #109 is an improvement to basic arithmetic, #029 is a proof input to #142, and #103 / #002 / #030 still lack an algorithm for a target attack.

D1 = integration of known steps; D2 = routine engineering and measurement; D3 = algorithmic or engineering improvement of research-level difficulty; D4 = requires a major new mathematical/cryptanalytic breakthrough. This grades the nature of the work; it is not an estimate of time, success probability or workload.

What exactly does a “bad outcome” on the right mean?

Primitive brokenSufficiently clear attack demonstrationDirect consequences and limits
secp256k1 ECDSA / SchnorrRecover the private key from a published public key, or construct an unauthorized but valid signatureThe corresponding account/UTXO can be spent illegitimately; BTC’s Taproot uses Schnorr, and legacy paths may use ECDSA. Whether the public key is exposed, the address type and the transaction window affect the scope of victims.Sources
Ethereum consensus BLSForge validator signatures / aggregate signatures accepted under the current rulesVote authenticity and finality can be impaired; arbitrary ETH is not automatically transferred merely because one BLS signature fails. The impact depends on the stake weight that can be forged.
KZGGive mutually contradictory openings for the same commitment that nevertheless pass verification; or deceive blob verificationCommitment binding, blob data integrity and KZG-dependent applications are impaired; whether this develops into a consensus failure depends on the specific checks and exploitable paths.Sources
Soundness of a particular ZK systemProduce a proof of an incorrect state transition that is nevertheless accepted by its on-chain verifierThe related rollup / bridge may accept illegitimate states or withdrawals; the system and circuit must be specified, and “all ZK is broken” cannot be derived directly from “KZG is broken”.
RSAFactor the target public-key modulus and compute the private keyAffects systems that use RSA; BTC / ETH native account signatures and Ethereum consensus do not use RSA as their main signature scheme.
The most important point when reading the diagrams: To get from a mathematics paper to a bad outcome on the right, one must cross at least target-problem reduction → feasibility at secure sizes → demonstration under real verification rules. So far the new papers have not built the first bridge from #142 to breaking current on-chain systems; the quantum-theoretical bridge corresponding to #279 already existed before publication.

Primary materials and scope

  1. OpenAI Math full catalog and repository notes. The repository states that the manuscripts have varying degrees of verification; this map discusses attack implications on the basis of “even if the stated theorems hold”.
  2. #142 finite-field polynomial factoring, original paper.
  3. #279 exact quantum factoring, original paper and formalization scope.
  4. #029 primitive roots, original paper.
  5. #107 finite-exception companion (Corollary 14.1); #107 matrix multiplication, main paper, companion paper for every fixed field and formalization scope.
  6. #109 integer multiplication, original paper.
  7. #103 derandomization, original paper.
  8. #002 BSD, original paper and #030 modularity, original paper.
  9. IETF pairing-friendly curves draft: G₁, G₂, Gₜ and finite-field parameters of BLS12-381.
  10. Guillevic: the four stages of finite-field discrete log with NFS-DL; linear algebra is only one of them.
  11. TNFS discrete-log research: sparse relation matrices and block Wiedemann; CADO-NFS official implementation.
  12. Practical ECC security analysis: Pollard rho and existing endomorphism constant-factor optimizations; Target security level of BIP-340.
  13. Shor’s original paper on quantum factoring and discrete-log algorithms.
  14. EIP-4844: blobs, KZG proofs and verification.
  15. BIP-340: secp256k1 Schnorr and BIP-341: Taproot rules.

Source statements and arithmetic were reviewed by Claude Opus 5.5 against local paper extracts. This is not a proof check, a certification, or an estimate of future attack probability. The implications shown here are conditional on the stated results and protocol assumptions. Resource comparisons and calculation examples are in the current complexity impact summary.

English edition · October 7, 2026

Review record and evidence boundaries

Source-statement review, independent arithmetic checks and browser verification.

Historical round-3 verdict: no remaining numerical or logical blockers in two earlier standalone English reports.

Those three rounds covered the earlier standalone attack-map and resource-table reports. They predate this combined page, its executive/cascade section, the repository README and the two PNG figures. The separate repository audit found three publication blockers; its corrections and follow-up scope are recorded in the repository review record.

This is a scoped review, not a correctness certificate.

The original mathematical proofs were not verified. Agreement between AI models does not establish their correctness. The report asks what follows even if the stated theorems hold; it does not estimate attack probability or claim that no future attack mechanism can exist.

Who reviewed what

What changed after discussion

Function values versus attack costsNormalized φ(m)=m^c examples are explicitly separated from complete attacks. They are not operation counts, actual speedups, values of finite-size complexity bounds, or cryptographic security-bit reductions.
#107: arithmetic and domainsCorrected the finite-exception example to 2^45.005. Separately identified the complex-field 2.25 bound, the 2.258 bound outside an uncomputed exceptional-characteristic set, and the 2.371054886006746 every-fixed-field bound. Added row weight w to the approximate sparse-solve cost w·N².
#109: finite sizesIncluded the extremely large constants and cutoff, and the schoolbook fallback below it. Substitution into the asymptotic expressions is not evidence of a finite-size speed gain.
#103: memory and a missing solverBoth old and new simulations have polynomial-time guarantees. The space comparison is O(log²n) to O(log n), with unmatched machine-dependent constants. The target BPL solver is not supplied.
#142 and #029: actual proof inputDistinguished finite-field polynomial factoring from RSA integer factoring. Defined the report’s input-size proxy ℓ separately from the manuscript’s symbols. Identified #029’s uniform Hecke zero-free theorem (Theorem 1.2), rather than its primitive-root count, as the proof input.
#279: exactness and hardwareDistinguished an ideal exact-success, worst-case polynomial guarantee from Shor-style bounded-error factoring with verification and repetition. Corrected the padded size parameter to n=max{128,⌊log₂N⌋+1}. No lower practical quantum-resource requirement is inferred.
Scope and wordingRemoved links to the superseded progress-score report. Corrected a garbled English scorecard sentence and shortened diagram labels while retaining full wording in tooltips and prose. Eight selected candidates are not an exhaustive audit of the repository.

What remains outside the review

Reproducible checks and source snapshot

GitHub paper citations in the English report are pinned to repository commit adc7f1241b42e322a6451854ab7e4b4c146bf78a. The local source manifest records the ten PDF hashes.