KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesThe Miller-Rabin Primality TestEngineering · Engineering MathematicsLesson 618/887← PrevNext →
GuidePublished 7 Aug 2026Updated 13 Aug 20268 min readBy Kevin Jogin
On this page

Ask about this page

KEVOS AIThe Miller-Rabin Primality Test

KEVOS knowledge first · trusted web sources when needed

Engineering  /  Mathematics  — Primality Testing

The Miller-Rabin Primality Test

The Miller-Rabin test, the witness structure, the one-quarter bound, and why it is the practical standard.

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

Executive summary

Miller-Rabin strengthens the Fermat test by tracking the square roots of unity encountered during exponentiation. No composite passes for more than a quarter of bases.

That bound is worst case and unconditional, which makes the test reliable even on adversarially chosen candidates.

Learning objectives

  1. State the algorithm and the witness condition.
  2. State and interpret the one-quarter bound.
  3. Choose the number of rounds for a target error.

01The algorithm

Algorithm

Miller-Rabin test

Inputodd candidate n > 3, random base a
Outputcomposite (certain), or probably prime
  1. Write n − 1 = 2^s · d with d odd.
  2. Choose a base a uniformly from {2, ..., n−2}.
  3. Compute x = a^d mod n.
  4. If x = 1 or x = n−1, report probably prime.
  5. Repeat s−1 times: set x = x² mod n; if x = n−1, report probably prime.
  6. Report composite.
Cost  one modular exponentiation, O(len(n)³)

The logic: if n is prime then a^{n−1} = 1, and the sequence of squarings reaching it must pass through −1 if it does not start at 1, because ±1 are the only square roots of unity modulo a prime. Failing to observe this proves compositeness.

02The witness bound

Theorem

Witness density

If n is an odd composite greater than 3, then at least three quarters of the bases in {2, ..., n−2} are witnesses to its compositeness.

Consequently a single round errs with probability at most 1/4, and k independent rounds err with probability at most 4^{−k}.

The proof shows that the non-witnesses are contained in a proper subgroup of Z_n*, and a proper subgroup of a finite group contains at most half its elements — with a more careful argument tightening this to a quarter.

  1. 1 round≤ 2^{−2}Insufficient alone
  2. 10 rounds≤ 2^{−20}Adequate for non-adversarial input
  3. 40 rounds≤ 2^{−80}Standard for cryptographic use
  4. 64 rounds≤ 2^{−128}Conservative; cost is negligible in context
Note
The bound is worst case over all composites. For a randomly generated candidate the true error is vastly smaller — the probability that a random odd composite passes even one round is far below 1/4 — which is why fewer rounds suffice when the candidate was generated locally rather than supplied.

03Deterministic variants

If the base is not chosen randomly but from a fixed set, the test becomes deterministic and the probabilistic bound no longer applies.

Deterministic base sets
Bound on nSufficient fixed basesStatus
< 3,215,031,7512, 3, 5, 7Verified exhaustively
< 3.3 × 10²⁴First 13 primesVerified exhaustively
All n, under GRHBases up to 2(ln n)²Conditional on the generalised Riemann hypothesis
Caution
Fixed-base testing is safe only for candidates within the verified range or generated locally. For attacker-supplied candidates it is unsafe: composites can be constructed that pass any specific published base set, and such constructions have been demonstrated. Use random bases when the input is not your own.

04Frequently asked questions

Why is the bound one quarter rather than one half?

The subgroup argument gives one half directly. Tightening to one quarter requires a finer analysis of the possible structures of the non-witness set, and the improvement matters because it halves the rounds needed for a target error.

Is 40 rounds excessive?

For locally generated candidates, yes by a wide margin — a handful suffices in practice. It is retained because the cost is trivial relative to key generation as a whole and it covers the adversarial case without further thought.

Can Miller-Rabin prove primality?

No. Passing establishes only a probability bound. Proving primality requires a different method such as elliptic curve primality proving or AKS, both far more expensive.

Related pages

  • Reducing the Error Probability
  • Modular Exponentiation by Repeated Squaring
  • The Fermat Test and Carmichael Numbers
  • Generating a Random Prime Between 2 and M

Sources and method

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

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 Miller-Rabin Primality Test. 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 Miller-Rabin Primality Test as a network of definitions and implications, not as a list of formulas. The working vocabulary on this page—miller-rabin, test, witness, bound, primality—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 Miller-Rabin Primality Test?

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 miller-rabin 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 — Algebra I — Massachusetts Institute of Technology. Used for groups, vector spaces, linear transformations and linear groups. Accessed 2026-08-13.
  • The Stacks Project — table of contents — The Stacks Project. Used for commutative algebra, homological algebra, modules and derived categories. Accessed 2026-08-13.

Continue learning

The Fermat Test and Carmichael NumbersGuide · Engineering MathematicsNEXT LESSON →Generating a Random Prime Between 2 and MGuide · Engineering MathematicsThe Structure of the Group of Units Modulo nGuide · Engineering MathematicsTrial Division up to a Small BoundGuide · Engineering Mathematics
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®