KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesThe Quadratic Residuosity AssumptionEngineering · Engineering MathematicsLesson 648/887← PrevNext →
GuidePublished 7 Aug 2026Updated 13 Aug 20268 min readBy Kevin Jogin
On this page

Ask about this page

KEVOS AIThe Quadratic Residuosity Assumption

KEVOS knowledge first · trusted web sources when needed

Engineering  /  Mathematics  — Quadratic Residues

The Quadratic Residuosity Assumption

The quadratic residuosity assumption, its use in probabilistic encryption, and its relationship to factoring.

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

Executive summary

The quadratic residuosity assumption states that residues and pseudo-residues with Jacobi symbol plus one cannot be distinguished efficiently without the factorisation.

It supports Goldwasser-Micali encryption, the first scheme to achieve semantic security, at the cost of extreme ciphertext expansion.

Learning objectives

  1. State the assumption precisely.
  2. Describe Goldwasser-Micali encryption.
  3. Situate the assumption relative to factoring.

01The assumption

Definition

Quadratic residuosity assumption

Let n = pq with distinct odd primes and let J₁ be the set of units with Jacobi symbol +1. No efficient algorithm, given only n, distinguishes a random quadratic residue from a random element of J₁ that is not a residue, with advantage better than negligible.

The set J₁ splits exactly in half between the two classes, so guessing achieves advantage zero and the assumption says nothing does better.

Partition of the unit group modulo pq
SetSize relative to Z_n*Efficiently recognisable?
Jacobi symbol −11/2Yes — compute the symbol
Quadratic residues1/4Believed not, without the factorisation
Pseudo-residues in J₁1/4Believed not, without the factorisation

02Goldwasser-Micali encryption

  1. Key generation

    Choose n = pq and a fixed pseudo-residue y with Jacobi symbol +1. Publish (n, y); keep p and q.

  2. Encrypt a zero bit

    Send r² mod n for random r — a genuine quadratic residue.

  3. Encrypt a one bit

    Send y · r² mod n — a pseudo-residue, since y is one.

  4. Decrypt

    Using p and q, test residuosity by Legendre symbols. Residue means 0, non-residue means 1.

The scheme encrypts a single bit per ciphertext, and each ciphertext is a full-size group element. For a 2048-bit modulus that is a 2048-fold expansion, which is why the scheme is of theoretical rather than practical importance.

Note
Its significance is historical and conceptual: it was the first encryption scheme proved semantically secure, establishing that encryption should be randomised and that security should be defined as indistinguishability rather than as difficulty of full recovery. That framework became standard.

03Relationship to factoring and other properties

  1. FactoringHardestSolving it breaks the residuosity assumption
  2. Quadratic residuosityNo harder than factoringNot known to be equivalent
  3. Jacobi symbolEasyPolynomial time, no factorisation needed

The assumption is formally weaker than the factoring assumption, since a factoring algorithm decides residuosity but no reduction is known in the other direction. In practice the best attack is to factor.

  • Homomorphic structure

    Multiplying two ciphertexts XORs the underlying bits, making the scheme additively homomorphic over one bit — a property later schemes generalised.

  • Semantic security

    Randomised encryption means identical plaintexts give different ciphertexts, defeating the dictionary attacks that deterministic schemes permit.

  • Descendants

    Paillier and other schemes retained the homomorphic property with far better expansion, and the lineage runs to modern homomorphic encryption.

04Frequently asked questions

Why must y be a pseudo-residue rather than any non-residue?

Because a non-residue with Jacobi symbol −1 would make ciphertexts for one-bits publicly distinguishable — anyone could compute the symbol. The whole scheme rests on both classes sharing the same computable symbol.

Is the ciphertext expansion improvable?

Not within this scheme, which is inherently bit-by-bit. Paillier and related constructions achieve constant expansion while keeping a homomorphic property, and are what practical applications use.

Does the homomorphic property weaken security?

It rules out non-malleability, since ciphertexts can be combined meaningfully. That is a deliberate trade — the property is useful for computing on encrypted data, and applications requiring non-malleability need a different scheme.

Related pages

  • The Diffie-Hellman Key Establishment Protocol
  • Computing Modular Square Roots: Composite Modulus

Sources and method

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

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 Quadratic Residuosity Assumption. 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 Quadratic Residuosity Assumption as a network of definitions and implications, not as a list of formulas. The working vocabulary on this page—assumption, quadratic, residuosity, encryption, relationship—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 Quadratic Residuosity Assumption?

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

Computing Modular Square Roots: Composite ModulusGuide · Engineering MathematicsNEXT LESSON →Modules: Definitions, Properties and ExamplesGuide · Engineering MathematicsComputing Modular Square Roots: Prime Power ModulusGuide · Engineering MathematicsSubmodules and Quotient ModulesGuide · Engineering Mathematics
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®