KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesThe Number Field Sieve and Factoring RecordsEngineering · Engineering MathematicsLesson 634/883← PrevNext →
GuidePublished 7 Aug 2026Updated 13 Aug 20268 min readBy Kevin Jogin
On this page

Ask about this page

KEVOS AIThe Number Field Sieve and Factoring Records

KEVOS knowledge first · trusted web sources when needed

Engineering  /  Mathematics  — Discrete Logarithms and Factoring

The Number Field Sieve and Factoring Records

The number field sieve, the current state of factoring records, and how key size recommendations follow from them.

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

Executive summary

The number field sieve is the fastest known general factoring algorithm and the basis of every record. It generates relations in an algebraic number field where the relevant values are much smaller.

Records and key size recommendations move over time, so this page routes to live authoritative sources rather than reproducing figures with a shelf life.

Learning objectives

  1. Describe the structure of the number field sieve.
  2. Explain how key size recommendations are derived.
  3. Locate current authoritative figures.

01Structure of the algorithm

  1. Polynomial selection

    Search for a polynomial with a root modulo n and good smoothness properties. A substantial share of total effort.

  2. Sieving

    Collect relations that are smooth on both the rational and algebraic sides simultaneously.

  3. Filtering

    Reduce the relation set, merging partial relations and removing singletons before the linear algebra.

  4. Linear algebra

    Find dependencies in a very large sparse matrix over GF(2), using block Lanczos or block Wiedemann.

  5. Square root

    Compute an algebraic square root and derive the congruence of squares, then take a gcd.

The gain over the quadratic sieve comes from the values being sieved being much smaller, which raises the smoothness rate enough to improve the exponent from 1/2 to 1/3.

L_n(1/3, 1.92) = exp((1.92 + o(1))(ln n)^{1/3}(ln ln n)^{2/3})

02From records to key sizes

Key size recommendations are extrapolations from record computations, adjusted for expected improvements in hardware and algorithms over the intended lifetime of the key.

  1. Measure a record

    A completed factorisation gives a concrete effort figure in core-years for a specific modulus size.

  2. Extrapolate by the complexity formula

    The L(1/3) expression predicts effort at other sizes.

  3. Add a margin

    Allow for hardware improvement and possible algorithmic advances over the key's lifetime.

  4. Publish a recommendation

    Standards bodies convert this into minimum key sizes by protection period.

Caution
Extrapolation assumes no algorithmic breakthrough. A materially better factoring algorithm would invalidate the recommendations immediately, and a sufficiently large quantum computer would break the assumption entirely via Shor's algorithm.

03Live sources rather than transcribed figures

Caution
This page deliberately does not reproduce current record sizes, effort figures or recommended key lengths. Such data is revised as records fall and guidance is updated, and a static page carrying stale figures is worse than one carrying none.
  • Standards bodies

    National and international standards organisations publish key length recommendations by protection period and revise them periodically.

  • Key length comparison sites

    Several maintained services aggregate the recommendations of different bodies side by side.

  • Record announcements

    Factoring records are announced by the teams involved with full effort accounting, which is the primary source for extrapolation.

  • Post-quantum guidance

    Migration timelines are published separately and are moving faster than classical key size guidance.

The durable content is the method: how the algorithm works, why the complexity has the form it does, and how a recommendation is derived from a record. Those do not change. The numbers do, and should be read from a maintained source at the time of use.

04Frequently asked questions

Why is polynomial selection so important?

Because the polynomial determines the size and smoothness behaviour of every value sieved afterwards. A better polynomial improves the yield across the entire sieving phase, so a large search up front pays back many times over.

Is the linear algebra step the bottleneck?

Often, in practice. Sieving parallelises across many machines; the sparse linear algebra does not parallelise nearly as well and typically requires a single large machine with substantial memory.

Would a quantum computer change this?

Fundamentally. Shor's algorithm factors in polynomial time on a sufficiently large fault-tolerant quantum computer, which would break RSA outright rather than merely requiring larger keys. This is what drives post-quantum migration.

Related pages

  • The RSA Cryptosystem
  • The Quadratic Sieve Algorithm

Sources and method

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

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.

Forward reference: this page extends beyond the source text and is flagged as post-source.

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 The Number Field Sieve and Factoring Records. 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 The Number Field Sieve and Factoring Records as a network of definitions and implications, not as a list of formulas. The working vocabulary on this page—records, number, field, sieve, factoring—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 The Number Field Sieve and Factoring Records?

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 records 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

The Quadratic Sieve AlgorithmGuide · Engineering MathematicsNEXT LESSON →Quadratic ResiduesGuide · Engineering MathematicsBetter Smoothness Density EstimatesGuide · Engineering MathematicsThe Legendre SymbolGuide · Engineering Mathematics
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®