KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesThe Quadratic Sieve AlgorithmEngineering · Engineering MathematicsLesson 633/883← PrevNext →
GuidePublished 7 Aug 2026Updated 13 Aug 20268 min readBy Kevin Jogin
On this page

Ask about this page

KEVOS AIThe Quadratic Sieve Algorithm

KEVOS knowledge first · trusted web sources when needed

Engineering  /  Mathematics  — Discrete Logarithms and Factoring

The Quadratic Sieve Algorithm

The quadratic sieve: candidate generation near the square root, sieving for smoothness, and its practical range.

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

Executive summary

The quadratic sieve generates candidates as values of a quadratic polynomial near the square root of n, so their residues are small and therefore more likely to be smooth.

Sieving detects smoothness across an interval at amortised low cost, which is the algorithmic advance that makes the method practical.

Learning objectives

  1. State the candidate polynomial and why it is chosen.
  2. Explain the sieving procedure.
  3. State the algorithm's practical range.

01Candidate generation

Take Q(x) = (x + ⌈√n⌉)² − n. For x small, Q(x) is small relative to n — of order √n — and is automatically congruent to a square modulo n.

Q(x) = (x + ⌈√n⌉)² − n ≡ (x + ⌈√n⌉)² (mod n)

Smallness is the whole point: smaller values are far more likely to be smooth, and the density estimate is highly sensitive to size. Generating candidates near the square root rather than at random is what makes the method work.

Note
The number field sieve extends exactly this idea. It constructs candidates in an algebraic number field where the relevant values are smaller still, which is what improves the exponent from 1/2 to 1/3.

02Sieving

Testing each candidate for smoothness by trial division would be far too slow. Sieving inverts the loop: for each factor base prime, mark all the candidates it divides.

Algorithm

Quadratic sieve, sieving phase

Inputmodulus n, factor base, sieve interval
Outputsmooth values of Q with their factorisations
  1. Allocate an array of approximate logarithms over the sieve interval, initialised to zero.
  2. For each factor base prime p:
  3.   Solve Q(x) ≡ 0 (mod p) for the two roots modulo p.
  4.   For each root, step through the interval adding log p at every position divisible by p.
  5. Report positions whose accumulated total is close to log|Q(x)| as smooth candidates.
  6. Verify each reported candidate by trial division over the factor base.
Cost  amortised O(log log y) per candidate

Working with approximate logarithms rather than exact division is the practical trick: additions replace divisions, and single-byte precision suffices because a verification pass catches the few false positives.

03Practical range and variants

Quadratic sieve variants
VariantImprovementEffect
Basic quadratic sieve—Baseline
Multiple polynomial QSMany polynomials, short intervals eachKeeps values small throughout; large gain
Large prime variationAllows one prime above the boundPartial relations combine; more relations per unit work
Double large primeAllows twoFurther gains at the cost of more bookkeeping

The multiple polynomial variant is the important one. A single polynomial produces values that grow as x moves away from zero, so the smoothness rate degrades along the interval. Switching polynomials frequently keeps every candidate small.

  1. Quadratic sieveL(1/2, 1)Best method up to roughly 100 digits
  2. Number field sieveL(1/3, 1.92)Better beyond; all records use it

The quadratic sieve remains the method of choice for moduli in the range where the number field sieve's much larger setup overhead is not yet amortised — roughly up to a hundred digits, which is well below cryptographic sizes but covers many practical factorisation tasks.

04Frequently asked questions

Why does Q(x) ≡ 0 (mod p) have exactly two roots?

Because it is a quadratic congruence modulo a prime, and n must be a quadratic residue modulo p for roots to exist at all. The factor base is restricted to primes for which that holds, which halves its size for free.

Why are approximate logarithms adequate?

Because the test only needs to identify candidates whose accumulated log total is near the expected value. Small errors produce a few false positives, which the verification pass removes cheaply.

When is the number field sieve preferable?

Above roughly 100 to 120 digits. Below that its substantial setup cost — particularly polynomial selection — outweighs its better asymptotic behaviour.

Related pages

  • Subexponential Integer Factoring
  • Better Smoothness Density Estimates
  • The Number Field Sieve and Factoring Records

Sources and method

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

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 The Quadratic Sieve Algorithm. 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 Quadratic Sieve Algorithm as a network of definitions and implications, not as a list of formulas. The working vocabulary on this page—quadratic, sieve, sieving, candidate, generation—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 Quadratic Sieve Algorithm?

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 quadratic 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.

  • NIST Digital Library of Mathematical Functions — National Institute of Standards and Technology. Used for mathematical notation, numerical methods, asymptotics and special functions. Accessed 2026-08-13.
  • MIT OpenCourseWare — Number Theory I — Massachusetts Institute of Technology. Used for algebraic and analytic number theory. Accessed 2026-08-13.

Continue learning

Better Smoothness Density EstimatesGuide · Engineering MathematicsNEXT LESSON →The Number Field Sieve and Factoring RecordsGuide · Engineering MathematicsSubexponential Integer FactoringGuide · Engineering MathematicsQuadratic ResiduesGuide · Engineering Mathematics
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®