KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesAtkin-Morain Elliptic Curve Primality ProvingEngineering · Engineering MathematicsLesson 864/883← PrevNext →
GuidePublished 7 Aug 2026Updated 13 Aug 20267 min readBy Kevin JoginECPPAtkin Moraincomplex multiplicationHilbert class polynomial
On this page

Ask about this page

KEVOS AIAtkin-Morain Elliptic Curve Primality Proving

KEVOS knowledge first · trusted web sources when needed

Modern Primality Tests

Atkin-Morain Elliptic Curve Primality Proving

ECPP: using complex multiplication to construct curves of known order, avoiding point counting entirely.

Engineering / MathematicsModern Primality Tests8 min readKV-MATH-0663

Atkin-Morain primality proving replaces point counting with curve construction. Curves with complex multiplication have orders given by a formula, so a suitable order can be sought before any curve is built.

The reversal

ECPP inverts the search
Goldwasser-KilianAtkin-Morain
Choose a curveChoose a discriminant
Count its points — expensiveCompute the order from a formula — cheap
Hope the order is suitableTest suitability before building anything
Repeat with a new curveRepeat with a new discriminant

Key point

The reversal is the whole idea. Testing an order costs a factorisation attempt; counting points costs a full run of Schoof's algorithm. Moving the test before the expensive step changes the economics completely.

The order formula

If the candidate is represented by the principal form of a discriminant, the curve orders with complex multiplication by that discriminant are given directly in terms of that representation.

4n = u^2 + |D| v^2 => curve order n + 1 - u, for suitable sign choicesSeveral orders arise from the twists; each is tested.

The algorithm

Atkin-Morain ECPP

  1. Choose a discriminantSmall absolute value and small class number, tried in increasing order.
  2. Represent the candidateSolve the norm equation — this succeeds only for suitable discriminants.
  3. Compute candidate ordersFrom the representation.
  4. Test for a suitable factorisationA small part times a large probable prime.
  5. Build the curveVia the Hilbert class polynomial, finding a root modulo the candidate.
  6. Find a point and recurseAs in Goldwasser-Kilian.

Why the curve is built last

Cost

Constructing the curve requires the Hilbert class polynomial, which is expensive for large class numbers. Building it only after a suitable order has been found means it is built once per recursion level rather than once per attempt.

Class invariants

Key point

The Hilbert class polynomial has enormous coefficients. Weber and other class invariants give much smaller polynomials generating the same field, and converting back is a simple algebraic step. Every practical implementation uses them.

Discriminant ordering

Discriminants are tried in order of class number, since small class number means a small class polynomial. Most candidates are settled by one of the first few discriminants tried.

Practical performance

Note

ECPP has proved primality for numbers of tens of thousands of digits. Its running time is variable, depending on how quickly a suitable discriminant and order are found, which makes it less predictable than the Jacobi sum test even where it is faster on average.

The certificate

The certificate is a chain of curve, point, discriminant and order factorisation at each level, verifiable independently and cheaply.

Source. Henri Cohen, A Course in Computational Algebraic Number Theory, Springer GTM 138 — 9.2.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

  • Complex Multiplication and Class Numbers
  • Modular Equations and the j-Invariant
  • The Goldwasser-Kilian Primality Test
  • Primality Certificates and Independent Verification

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 Atkin-Morain Elliptic Curve Primality Proving. 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 Atkin-Morain Elliptic Curve Primality Proving as a network of definitions and implications, not as a list of formulas. The working vocabulary on this page—curve, primality, proving, ecpp, complex—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 Atkin-Morain Elliptic Curve Primality Proving?

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 curve 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 Goldwasser-Kilian Primality TestGuide · Engineering MathematicsNEXT LESSON →Primality Certificates and Independent VerificationGuide · Engineering MathematicsImplementing the Jacobi Sum TestGuide · Engineering MathematicsSmoothness and Sub-exponential ComplexityGuide · Engineering Mathematics
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®