KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesTrial Division and Lehman's MethodEngineering · Engineering MathematicsLesson 853/883← PrevNext →
GuidePublished 7 Aug 2026Updated 13 Aug 20267 min readBy Kevin Jogintrial divisionFermat methodLehman methodsmall factors
On this page

Ask about this page

KEVOS AITrial Division and Lehman's Method

KEVOS knowledge first · trusted web sources when needed

Classical Primality and Factoring

Trial Division and Lehman's Method

Trial division as the first factoring step, its cost, and Lehman's improvement on Fermat's method.

Engineering / MathematicsClassical Primality and Factoring8 min readKV-MATH-0652

Trial division is the first step of every factoring attempt and it handles the great majority of numbers encountered in practice. Knowing when to stop is what matters.

Trial division

Divide by successive small primes up to a chosen bound. Any factor below the bound is found; nothing above it is.

Trial division bounds
BoundCostFinds
A few hundredNegligibleMost factors of random numbers
A millionFastClears the vast majority of composites
BeyondDiminishing returnsBetter handled by ECM

Key point

Trial division should always run first, but only to a modest bound. Beyond roughly a million, ECM finds small factors far more efficiently, so extending trial division further is wasted effort.

Implementation

Cost

Use a precomputed prime table rather than testing every odd number, and stop as soon as the square of the current divisor exceeds the remaining cofactor — at that point the cofactor is prime. Both are elementary and both are frequently omitted.

Fermat's method

Fermat's method searches for a representation of the number as a difference of two squares, which immediately gives a factorisation.

n = x^2 - y^2 = (x-y)(x+y)Search x upward from the ceiling of the square root.

Note

The method is fast when the two factors are close together and hopeless otherwise. Since a number with close factors is exactly what a careless key generator produces, the method retains practical importance as an attack.

Lehman's method

Lehman generalises Fermat by searching for a difference of squares after multiplying by a small integer, which handles unbalanced factors much better.

Search over small k for x^2 - y^2 = 4 k nRecovers factors in a bounded range of ratios.
Elementary factoring methods compared
MethodCostBest for
Trial divisionProportional to the smaller factorSmall factors
FermatProportional to the gap between the factorsNearly equal factors
LehmanCube root of the numberGuaranteed bound; small numbers
Pollard rhoFourth root of the numberModerate factors

Key point

Lehman's method gives a deterministic cube-root bound, which is better than trial division's worst case of a square root. It is primarily of theoretical interest, since Pollard rho does better in practice.

Practical sequencing

Factoring strategy

  1. Trial divideTo a modest bound.
  2. Test the cofactor for primalityUsing Baillie-PSW.
  3. Check for perfect powersSee perfect powers.
  4. Apply rho or ECMFor moderate factors.
  5. Apply a sieveFor the hard remaining cases.

Source. Henri Cohen, A Course in Computational Algebraic Number Theory, Springer GTM 138 — 8.5.1-8.5.2. Structural reference unverified: the source file was not available during authoring; chapter and section numbers are taken from the published edition and have not been checked against a physical copy.

Related pages

  • Integer Square Root and Perfect Power Detection
  • N+1 Tests and the Lucas-Lehmer Test
  • The Pollard Rho Factoring Method

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 Trial Division and Lehman's Method. 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 Trial Division and Lehman's Method as a network of definitions and implications, not as a list of formulas. The working vocabulary on this page—method, trial, division, lehman's, 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 Trial Division and Lehman's Method?

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

N+1 Tests and the Lucas-Lehmer TestGuide · Engineering MathematicsNEXT LESSON →The Pollard Rho Factoring MethodGuide · Engineering MathematicsThe Pocklington-Lehmer N-1 Primality TestGuide · Engineering MathematicsThe Pollard p-1 MethodGuide · Engineering Mathematics
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®