KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesThe Refutation of Euler's ConjectureEngineering · Engineering MathematicsLesson 48/883← PrevNext →
GuidePublished 12 Aug 2026Updated 13 Aug 20268 min readBy Kevin Jogin
On this page

Ask about this page

KEVOS AIThe Refutation of Euler's Conjecture

KEVOS knowledge first · trusted web sources when needed

Selected Topics and Applications

The Refutation of Euler's Conjecture

The 1959–60 disproof of Euler's conjecture by Bose, Shrikhande and Parker, and the algebraic construction that produced the counterexamples.

Category Engineering / MathematicsSource III.3Pages 115-118Reading 2 minReviewed 2026-08-07

Learning objectives

  • Describe the counterexample of order 10 and the general result
  • Follow the algebraic strategy behind the construction
  • Assess what the episode shows about applied universal algebra
On this page
  1. The result
  2. The strategy
  3. What the algebraic view contributed
  4. Assessment

The result

Bose–Shrikhande–Parker

A pair of orthogonal Latin squares of order n exists for every n except n = 2 and n = 6.

Euler's conjecture is therefore false for every order congruent to 2 mod 4 beyond 6. The first counterexample, of order 10, was found by Parker; Bose and Shrikhande produced order 22 and then, jointly with Parker, the general result.

The two genuine exceptions

Orders 2 and 6 are the only failures, and both are verifiable by finite search — order 2 trivially, order 6 by Tarry's 1901 enumeration. Every other order admits an orthogonal pair. The conjecture was wrong everywhere it made a non-trivial claim.

The strategy

Small ingredientsFind orthogonal pairs on small sets, including some with prescribed subsquares
Product constructionCombine them coordinatewise to build larger orders
PatchingReplace a subsquare of the product by a different orthogonal pair of the same order
ResultOrders inaccessible to the product construction alone

The product construction alone cannot reach orders congruent to 2 mod 4, because such an order has exactly one factor of 2 and order 2 admits no orthogonal pair. The essential new ingredient is the patching step, which allows a block of the constructed square to be replaced independently.

Pairwise balanced designs

The formal setting for the patching argument is the theory of pairwise balanced designs, developed by Bose and Shrikhande for exactly this purpose. It provides a systematic bookkeeping for which orders can be assembled from which ingredients.

What the algebraic view contributed

Products

The coordinatewise construction is immediate once orthogonality is stated as a condition on operations. Combinatorially it requires explicit verification.

Subsquares as subalgebras

The patching step replaces a subquasigroup by another of the same order. Framing subsquares as subalgebras makes the legitimacy of the replacement clear.

Systematic search

Reformulating the problem algebraically turned an apparently unstructured search into a construction problem with known building blocks.

The source presents this episode as evidence for its claim that applied universal algebra would grow in importance. The claim was that algebraic framing is not decoration but the thing that makes the construction visible.

Assessment

The algebra did not do all the work

It would overstate the case to say universal algebra solved the problem. The decisive ingredients were combinatorial designs and substantial explicit construction. What the algebraic framing supplied was the product and substitution operations, and a language in which the pieces compose.

The honest summary is that the algebraic viewpoint made the composition structure of the problem visible, and that composition structure is what the eventual proof exploits. That is a real contribution without being the whole of the proof.

The general lesson

When a combinatorial class is closed under products and admits substructures, recasting it as a variety supplies constructions for free. Steiner systems, Latin squares, and finite automata in the next pages all follow this pattern.

Frequently asked questions

Why did the conjecture survive 177 years?

Because the two smallest cases both failed, no construction was known for any order congruent to 2 mod 4, and Tarry's exhaustive verification of order 6 gave the pattern strong empirical support. The counterexamples require constructions considerably more elaborate than anything available in Euler's time.

Are there three mutually orthogonal Latin squares of order 10?

Yes. Whether there are nine — the maximum, equivalent to a projective plane of order 10 — was settled negatively by a large computer search in 1989.

Related pages

  • Orthogonal Latin Squares and Euler's Conjecture
  • Finite State Acceptors and Recognisable Languages

Source. S. Burris and H. P. Sankappanavar, A Course in Universal Algebra, The Millennium Edition — a corrected re-typesetting of Springer-Verlag Graduate Texts in Mathematics 78 (1981). Section III.3, book pages 115-118.

This page is an original exposition prepared for the KEVOS® knowledge library. It restates and reorganises mathematical results; it is not a reproduction of the source text.

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 Refutation of Euler's Conjecture. 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 Refutation of Euler's Conjecture as a network of definitions and implications, not as a list of formulas. The working vocabulary on this page—euler's, conjecture, algebraic, refutation, disproof—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 Refutation of Euler's Conjecture?

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 euler's 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

Relations, Functions and Ordinals: a Working ReferenceGuide · Engineering MathematicsSublattices and Lattice IsomorphismGuide · Engineering MathematicsSubalgebras and Algebra IsomorphismGuide · Engineering MathematicsClass Operators H, S, P and their CompositionGuide · Engineering Mathematics
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®