KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesSubexponential Integer FactoringEngineering · Engineering MathematicsLesson 631/883← PrevNext →
GuidePublished 7 Aug 2026Updated 13 Aug 20268 min readBy Kevin Jogin
On this page

Ask about this page

KEVOS AISubexponential Integer Factoring

KEVOS knowledge first · trusted web sources when needed

Engineering  /  Mathematics  — Discrete Logarithms and Factoring

Subexponential Integer Factoring

Factoring by congruences of squares, the relation collection and linear algebra phases, and the resulting subexponential cost.

Page KV-MATH-0404Reading time 4 minReviewed 2026-08-07Author Kevin Jogin

Executive summary

Modern factoring algorithms all work by finding two numbers whose squares are congruent modulo n but which are not themselves congruent. A gcd then splits the modulus.

Finding such a pair is done by collecting smooth relations and solving a linear system over the field of two elements.

Learning objectives

  1. State the congruence of squares principle.
  2. Describe relation collection and the linear algebra step.
  3. State the success probability per dependency.

01Congruences of squares

Theorem

Splitting by a congruence of squares

If x² ≡ y² (mod n) but x ≢ ±y (mod n), then gcd(x − y, n) is a proper factor of n.

Reason. n divides (x−y)(x+y) but divides neither factor, so its prime factors are distributed between them.

The condition x ≢ ±y is essential and is where the probabilistic element enters. For a modulus with two distinct prime factors, a random square root of a square is congruent to ±y half the time, so each dependency succeeds with probability at least one half.

Note
This is exactly the structure underlying Miller-Rabin: composites have extra square roots of unity, and finding one splits the modulus. Factoring and primality testing exploit the same structural fact in opposite directions.

02Relation collection

The problem becomes constructing such a pair. The approach is to find many values whose squares reduce to smooth numbers modulo n, then combine them so the product is a perfect square.

  1. Fix a factor base

    Primes up to a smoothness bound, chosen from the density analysis.

  2. Generate candidates

    Values near √n whose squares reduce to small residues, tested for smoothness by sieving.

  3. Record exponent vectors

    Each smooth relation gives a vector of prime exponents, reduced modulo 2.

  4. Find a dependency

    Once there are more relations than factor base primes, a linear dependence over GF(2) exists.

  5. Form the congruence

    Multiplying the relations in a dependency gives a product where every exponent is even — a perfect square.

Reducing exponents modulo 2 is the key simplification: only the parity matters, because a product is a square exactly when every exponent is even. The linear algebra is therefore over the two-element field, which makes it fast despite the matrix size.

03Cost and the two bottlenecks

  1. Relation collectionDominant, highly parallelEach candidate independent; scales across machines
  2. Linear algebraLarge sparse system over GF(2)Hard to parallelise; often the practical bottleneck
  3. Square root and gcdNegligibleOne square root computation and a gcd per dependency
Subexponential factoring methods
AlgorithmComplexityPractical range
Quadratic sieveL(1/2, 1)Best up to about 100 digits
Number field sieveL(1/3, 1.92)Best beyond that; used for all records

Relation collection parallelises almost perfectly, which is why factoring records are set by large distributed efforts. The linear algebra phase does not, and it typically requires a single large machine with substantial memory, making it the harder half to scale.

Each dependency yields a factorisation with probability at least one half, so collecting a few extra relations beyond the minimum ensures success without materially increasing cost.

04Frequently asked questions

Why reduce exponents modulo 2?

Because the goal is a perfect square, which requires only that every exponent be even. Working modulo 2 discards irrelevant information and reduces the linear algebra to the smallest possible field.

What if a dependency gives x ≡ ±y?

The attempt fails and another dependency is tried. Since each succeeds with probability at least one half, a handful of extra relations makes overall failure negligible.

Why is the number field sieve better?

It generates relations from algebraic number fields where the values involved are much smaller, so smooth values are far more common. That improves the exponent from 1/2 to 1/3, which is an enormous gain at large sizes.

Related pages

  • The RSA Cryptosystem
  • Subexponential Discrete Logarithm Algorithms
  • Better Smoothness Density Estimates

Sources and method

Structural reference: Victor Shoup, A Computational Introduction to Number Theory and Algebra, Version 1, Cambridge University Press, 2005 — book pages 344-352.

This page carries the durable method layer only: definitions, constructions, algorithms, complexity results and selection criteria, authored originally for KEVOS. No text is transcribed or paraphrased from the source, and no numeric tables or benchmark data are reproduced — these are routed to live authoritative sources instead.

Author: Kevin Jogin. Last reviewed 2026-08-07.

Handbook application: from concept to controlled practice

Purpose. This expanded section turns the original page into a practical handbook. It preserves the supplied material and adds a repeatable way to apply, check and review Subexponential Integer Factoring. It does not replace a contract, legislation, a controlled standard, competent engineering judgement or specialist advice.

The operating aim is to turn a compact mathematical statement into a usable chain of definitions, claims, examples and checks. Read the original explanation first, then use the workflow and checks below to convert knowledge into evidence.

Treat Subexponential Integer Factoring as a network of definitions and implications, not as a list of formulas. The working vocabulary on this page—subexponential, factoring, congruences, squares, relation—should be made explicit before any proof or computation begins. Record the ambient set or structure, the permitted operations and the equality or equivalence relation in use. A compact theorem often changes meaning when the base field, finiteness condition, commutativity assumption or direction of an action changes.

For a proof, write the hypotheses as a checklist and mark the line at which each one is used. For a computation, state the representation of the input, the arithmetic model, the termination condition and the output invariant. For a classification problem, distinguish existence from uniqueness and distinguish an object from its representation. These separations prevent a correct local calculation from being mistaken for the general result.

A useful worked example should be small enough to inspect completely but rich enough to exercise the main mechanism. Compute the result in two ways where practical: symbolically and by substitution, structurally and numerically, or directly and through a normal form. Then include one near-miss example in which a hypothesis fails. The contrast explains why the theorem is shaped as it is and gives the reader a diagnostic pattern for later problems.

Verification is part of the mathematics. Check domains and codomains, substitute proposed solutions, test identity and zero cases, compare dimensions or cardinalities, and confirm that maps respect the required operations. In numerical work, report precision, conditioning and a residual rather than digits alone. In algorithmic work, separate mathematical correctness from implementation complexity and resource limits.

Step-by-step operating method

  1. Fix the setting. State the objects, ambient structure, notation and assumptions before manipulating symbols.
  2. Separate claims. Distinguish definitions, hypotheses, conclusions, equivalent conditions and consequences.
  3. Choose a method. Select proof, construction, calculation or algorithm according to the question actually asked.
  4. Work a small case. Use the smallest non-trivial example to expose the mechanism and test edge behaviour.
  5. Verify independently. Substitute back, check invariants, test boundary cases or use an alternative derivation.

Worked-example protocol

Illustrative method—not a source theorem. Start with a small admissible input and list the definitions it must satisfy. Carry out each transformation on a separate line, citing the property that permits it. Preserve exact values until approximation is necessary. At the end, verify the output against the original definition and one invariant such as dimension, degree, determinant, order, norm or residual. Then alter one hypothesis and observe which step ceases to be valid. This protocol creates a reusable example without inventing a theorem-specific numerical answer.

StageRecordQuality check
InputObjects, domain, notation, assumptionsEvery symbol is defined
MethodPermitted operation or cited result at each stepAll hypotheses hold
OutputExact result and representationCorrect type, domain and form
VerificationSubstitution, invariant or alternative derivationIndependent agreement
Boundary testZero, identity, degenerate or failed hypothesisScope is understood

Common failure modes and recovery actions

1. Watch for

Using a theorem without checking every hypothesis.

Recovery: Return to the governing definition or requirement and restate the decision in one sentence.

2. Watch for

Treating a suggestive example as a proof of the general case.

Recovery: Separate evidence from assumption, assign an owner and set a date for validation.

3. Watch for

Changing notation or conventions part-way through an argument.

Recovery: Run a small counterexample, boundary test, pilot or independent check before proceeding.

4. Watch for

Hiding a division-by-zero, convergence, finiteness or commutativity assumption.

Recovery: Record the consequence, decision and rationale, then update the controlled baseline.

5. Watch for

Reporting a computed result without a residual, substitution or structural check.

Recovery: Escalate when the issue affects safety, compliance, acceptance, material value or an agreed tolerance.

Review checklist

  • Can every symbol be traced to a definition or prior result?
  • Which hypothesis does each major step use?
  • Does the method cover zero, identity, degenerate and boundary cases?
  • Can the conclusion be checked by a second representation or calculation?
  • Are mandatory requirements distinguished from recommendations and illustrative values?
  • Are sources, assumptions, units, dates and versions recorded closely enough to reproduce the decision?
  • Have safety, legal, ethical, stakeholder and operational consequences been considered at the appropriate level?
  • Is there a named owner and a trigger for review, escalation, change or retirement?

Questions for deeper application

What is the most important distinction a practitioner must preserve when applying Subexponential Integer Factoring?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

Which assumption about subexponential would change the result most if it proved false?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

What evidence would allow an independent reviewer to reproduce or challenge the conclusion?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

Which boundary, exception or failure case has not yet been tested?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

What must be handed over, monitored or reviewed after the immediate work is complete?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

Authoritative references and use notes

The sources below were selected as institutional or primary guidance for the broader practice. They support the handbook method; they do not imply that every statement or clause in a source applies to every project. Confirm the current edition, jurisdiction, contract and application before treating any requirement as mandatory.

  • MIT OpenCourseWare — Number Theory I — Massachusetts Institute of Technology. Used for algebraic and analytic number theory. Accessed 2026-08-13.
  • MIT OpenCourseWare — Algebra I — Massachusetts Institute of Technology. Used for groups, vector spaces, linear transformations and linear groups. Accessed 2026-08-13.

Continue learning

Subexponential Discrete Logarithm AlgorithmsGuide · Engineering MathematicsNEXT LESSON →Better Smoothness Density EstimatesGuide · Engineering MathematicsSmooth NumbersGuide · Engineering MathematicsThe Quadratic Sieve AlgorithmGuide · Engineering Mathematics
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®