← Latest papers
💻 computer science

Verified Pythagorean Composition for Adaptive Cryptographic Games: Noise Flooding in Homomorphic Encryption

This paper presents a machine-checked proof using Rocq and SSProve that establishes a tight, square-root security bound for noise flooding in homomorphic encryption against adaptive decryption attacks by introducing a new relational program logic with a Pythagorean judgment that composes conditional KL costs without intermediate conversion to statistical distance.

Original authors: Yi Lee, Alexandru Cojocaru, Junyi Liu, Xiaodi Wu

Published 2026-08-17
📖 8 min read🧠 Deep dive

Original authors: Yi Lee, Alexandru Cojocaru, Junyi Liu, Xiaodi Wu

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are sending a secret message to a friend, but you have to send it through a post office run by a mischievous goblin who loves to peek at letters. In the old days, you'd lock the letter in a box, but once the goblin opened it to read the message, the secret was gone. Then, a magical invention called Homomorphic Encryption arrived. This is like a special lockbox that lets the goblin do math on the locked letters—adding them, multiplying them, sorting them—without ever unlocking them. When the goblin hands the result back, you unlock it, and it's the correct answer to the math problem, even though the goblin never saw the numbers inside.

However, there's a catch. In the most popular version of this magic, called CKKS, the math isn't perfect. Because the numbers are so complex, the result you get back is slightly "fuzzy" or approximate, like a blurry photo instead of a sharp one. Usually, this fuzziness is fine; it's just a tiny bit of static. But a sneaky goblin (an attacker) can ask for the answer to many different math problems, compare the blurry results with what they think the answer should be, and use those tiny differences to slowly reconstruct your secret key. It's like if the goblin could tell exactly how much your lockbox wobbled when you shook it, and used that wobble to figure out the combination. To stop this, cryptographers came up with a defense called Noise Flooding: they add a giant, random burst of static (noise) to the answer before sending it back, drowning out the tiny clues the goblin was trying to use.

The big question was: How much static do you need to add? If you add too little, the goblin can still hear the secret. If you add too much, the answer becomes so blurry it's useless. The tricky part is that the goblin can ask questions one by one, changing their strategy based on your previous answers. If you add static for each question separately, the "cost" of the static adds up quickly, forcing you to make the answers incredibly blurry. But a clever mathematical idea suggested that if you look at the whole game at once, the cost might grow much slower—like the square root of the number of questions, rather than the number itself. This paper is about proving that this clever idea actually works, and proving it in a way that a computer can check every single step to make sure no mistakes were made.


The Paper's Big Discovery: The "Pythagorean" Secret

This paper, titled "Verified Pythagorean Composition for Adaptive Cryptographic Games," is a massive achievement in formal verification, which is basically using a super-smart computer to check math proofs for errors. The authors, a team of researchers, took a famous security argument about noise flooding and translated it into a language the computer could understand. They then asked the computer to verify every single logical step, ensuring that the math holds up under the most intense scrutiny.

The core of their work is a new way of thinking about how errors add up when you have a sneaky attacker asking many questions.

The "Blurry Photo" Problem

Imagine you are trying to hide a secret by adding a little bit of static to a photo. If you add a tiny bit of static, the photo is still clear, but a sharp-eyed goblin might spot the secret. If you add a lot of static, the secret is safe, but the photo is now a mess.
In the world of encryption, the "static" is called noise. The paper looks at a scenario where an attacker asks for the decrypted result of a message up to qq times. Each time, the defender adds noise to hide the secret.

  • The Old Way (Linear Loss): If you treat each question as a separate event, you have to add enough noise to be safe for every single question. If the attacker asks 100 questions, you might need 100 times the noise, making the final result completely useless.
  • The New Way (Square-Root Loss): The paper confirms a smarter strategy. It shows that because the attacker's questions are connected (they are "adaptive"), the total amount of noise needed only grows by the square root of the number of questions (q\sqrt{q}). So, for 100 questions, you only need 10 times the noise, not 100. This is a huge win because it means you can keep the answers much clearer while still being safe.

The "Pythagorean" Analogy

Why do they call it "Pythagorean"? Think of a right-angled triangle. If you have two sides of length 3 and 4, the longest side (the hypotenuse) isn't 3+4=73 + 4 = 7. It's 32+42=5\sqrt{3^2 + 4^2} = 5. The total length is shorter than just adding the sides up.
In this paper, the "sides" are the tiny bits of risk (or "cost") from each of the attacker's questions.

  • The Mistake: If you just add the risks together (3+43 + 4), you get a huge, scary number.
  • The Reality: The authors prove that these risks combine like the sides of a triangle. They "cancel out" a bit because they are related. The total risk is the square root of the sum of the squares.
    The paper proves that you can keep track of these risks separately (as "Conditional Kullback-Leibler costs," which is a fancy math way of saying "how different the answers look") and only convert them into a final "safety score" at the very end. This allows the math to stay efficient and the noise to stay low.

The Computer's Role: The "Robot Lawyer"

You might wonder, "Why do we need a computer to check this? Isn't math just math?"
The problem is that these proofs are incredibly complex. They involve thousands of steps, dealing with probabilities, random numbers, and the behavior of a sneaky attacker who changes their mind. It's easy for a human to miss a tiny detail or make a small assumption that breaks the whole argument.
The authors used a tool called Rocq (a proof assistant) and a library called SSProve. They didn't just write the proof on paper; they built a digital model of the encryption game.

  1. The Logic: They created a new set of rules (a "program logic") that tells the computer how to handle these "Pythagorean" risk combinations.
  2. The Compiler: They built a "trace compiler," which is like a robot that watches the attacker's program. It can pause the attacker, peek at their next move, and then let them continue, all while keeping the secret safe.
  3. The Verification: The computer checked every single line of code and every mathematical step. It confirmed that if the underlying encryption is secure, then adding this noise flooding defense makes it secure against these specific types of attacks, with the "square-root" efficiency.

What This Means for You

The paper doesn't invent a new encryption method or a new attack. Instead, it takes a known defense (noise flooding) and proves, with absolute mathematical certainty, that it works exactly as the clever "Pythagorean" theory predicted.

  • It rules out the idea that you need to add a massive amount of noise (linear growth) to stay safe against adaptive attackers.
  • It proves that the "square-root" growth is real and safe, provided the underlying encryption is already secure.
  • It confirms that the complex math behind this defense doesn't have hidden holes.

The authors are very careful to say that this is a verified proof of the logic, not a guarantee that every specific encryption software in the world is perfect. They proved that if you have a good encryption scheme and you apply this noise flooding correctly, the math says you are safe. They also noted that they didn't check the specific details of the most popular encryption scheme (CKKS) itself, just the logic of the noise defense. But for the defenders of digital privacy, this is a massive step forward: it means we can trust the math that keeps our secrets safe, even when the attackers are smart and persistent.

In short, the paper is like a master architect who, after years of debate, finally brings in a team of robot inspectors to confirm that the bridge's design is sound. They proved that the bridge doesn't need to be built with twice as much steel as we thought; the clever geometry of the design (the Pythagorean rule) is enough to hold the weight, keeping the path clear and the secrets hidden.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →