KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesSmooth NumbersEngineering · Engineering MathematicsLesson 629/883← PrevNext →
GuidePublished 7 Aug 2026Updated 13 Aug 20268 min readBy Kevin Jogin
On this page

Ask about this page

KEVOS AISmooth Numbers

KEVOS knowledge first · trusted web sources when needed

Engineering  /  Mathematics  — Discrete Logarithms and Factoring

Smooth Numbers

Smooth numbers, their density, and why they are the raw material of subexponential factoring and index calculus.

Page KV-MATH-0402Reading time 3 minReviewed 2026-08-07Author Kevin Jogin

Executive summary

An integer is smooth if all its prime factors are small. Smooth numbers factor easily over a fixed set of primes, which is what makes them useful in relation-collecting algorithms.

Their density governs the running time of every subexponential factoring and discrete logarithm method.

Learning objectives

  1. Define smoothness and state the density estimate.
  2. Explain the role of smooth numbers in relation collection.
  3. Derive the optimal smoothness bound.

01Definition and density

Definition

Smooth number

An integer is y-smooth if every prime factor is at most y.

Ψ(x, y) denotes the count of y-smooth integers up to x.

Theorem

Density estimate

With u = ln x / ln y,

Ψ(x, y) / x ≈ u^{−u} = ρ(u),

where ρ is the Dickman function.

The estimate says smoothness becomes rare quickly as the ratio u grows. For u = 2 about a quarter of integers are smooth; for u = 10 the proportion is around 10^{−10}.

02Why smooth numbers are useful

A y-smooth number factors completely over the primes below y, so it can be recorded as an exponent vector over that fixed basis. Relations between such vectors are what the sieve algorithms collect.

  1. Fix a factor base

    All primes up to the smoothness bound y.

  2. Generate candidates

    Values whose smoothness can be tested cheaply, typically by sieving.

  3. Keep the smooth ones

    Each smooth value gives an exponent vector over the factor base.

  4. Solve a linear system

    Enough vectors give a linear dependence modulo 2, which yields a congruence of squares and hence a factorisation.

Note
The same structure serves both factoring and discrete logarithms. In factoring, the dependence yields a congruence of squares; in index calculus, the relations form a linear system whose solution gives the logarithms of the factor base elements. The relation-collection machinery is shared.

03Choosing the smoothness bound

Two costs oppose each other. A small bound makes smooth numbers rare, so relation collection is slow. A large bound makes the factor base big, so the linear algebra is slow.

  1. Small yRelations rareCollection dominates; many candidates needed per relation
  2. Large yFactor base largeLinear algebra dominates; the matrix grows
  3. Optimal yL(1/2) or L(1/3)Balances the two; derived by differentiating the total cost
L_n(α, c) = exp((c + o(1))(ln n)^α (ln ln n)^{1−α})

Balancing the two costs with the Dickman estimate gives the optimum, and the resulting total is subexponential — of the form L(1/2) for the quadratic sieve and L(1/3) for the number field sieve. That expression is the reason RSA moduli must be thousands of bits rather than hundreds.

04Frequently asked questions

Why is the density u^{−u} rather than something simpler?

It comes from a recursive count of integers whose largest prime factor is bounded, which produces the Dickman differential-delay equation. The u^{−u} form is its asymptotic behaviour and is accurate over the range that matters.

How is smoothness tested efficiently?

By sieving rather than by trial dividing each candidate. Sieving marks multiples of each factor base prime across an interval, so the cost is amortised over all candidates simultaneously.

Does the optimum depend on the algorithm?

Yes. The quadratic sieve and the number field sieve have different relation-generation costs, so their optimal bounds and resulting complexities differ — L(1/2) versus L(1/3).

Related pages

  • Mertens' Theorem
  • Generating a Random Factored Number
  • The Diffie-Hellman Key Establishment Protocol
  • Subexponential Discrete Logarithm Algorithms

Sources and method

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

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 Smooth Numbers. 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 Smooth Numbers as a network of definitions and implications, not as a list of formulas. The working vocabulary on this page—smooth, numbers, density, material, subexponential—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 Smooth Numbers?

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 smooth 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 Diffie-Hellman Key Establishment ProtocolGuide · Engineering MathematicsNEXT LESSON →Subexponential Discrete Logarithm AlgorithmsGuide · Engineering MathematicsDiscrete Logarithms in the Full Group Modulo pGuide · Engineering MathematicsSubexponential Integer FactoringGuide · Engineering Mathematics
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®