← Latest papers
🤖 machine learning

Privacy-Preserving and Verifiable Approximate Distributed Coded Computing

This paper proposes a model-agnostic framework that unifies privacy-preserving coded computing (GPBACC) with robust aggregation and verification techniques to simultaneously defend against privacy leakage and malicious behavior in both federated and decentralized machine learning settings.

Original authors: Xavier Martínez-Luaña, Alba Gude-Santos, Manuel Fernández-Veiga, Rebeca P. Díaz-Redondo

Published 2026-07-03
📖 5 min read🧠 Deep dive

Original authors: Xavier Martínez-Luaña, Alba Gude-Santos, Manuel Fernández-Veiga, Rebeca P. Díaz-Redondo

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 a group of people trying to solve a giant puzzle together. They want to build a smart computer brain (a machine learning model) without ever showing each other their private puzzle pieces (their personal data). This is the goal of Distributed Machine Learning.

However, there are two big problems with this group effort:

  1. Privacy Leaks: Even if they don't show the pieces, a sneaky person might be able to guess what your piece looks like just by watching how you move them.
  2. Bad Actors: Someone might try to sabotage the puzzle by throwing in fake pieces or shouting wrong instructions to confuse the group.

Most existing solutions try to fix either the privacy problem or the sabotage problem, but rarely both at the same time. They also often only work for specific types of groups.

This paper introduces a new, flexible system called GPBACC (Generalized Privacy-aware Berrut Approximated Coded Computing) that fixes both problems for two different types of groups: Federated Learning (where a boss collects answers) and Decentralized Learning (where everyone talks to everyone without a boss).

Here is how it works, using simple analogies:

1. The Magic "Scramble" (Privacy)

Imagine you have a secret recipe. Instead of sending the recipe, you send a scrambled smoothie made from your recipe mixed with a bunch of random, invisible ingredients (noise).

  • The Trick: You send this smoothie to several friends. They taste it and do some math on it.
  • The Result: When the boss (or the group) mixes all the smoothies back together, the random noise cancels out, and the original recipe is revealed perfectly.
  • The Privacy: If a sneaky friend tries to taste just one smoothie, they only get a taste of random noise. They can't figure out your secret recipe. This is the Privacy part of the system.

2. The "Group Detective" (Stopping Saboteurs)

Now, imagine one of your friends is a saboteur. They try to send a smoothie that tastes like garbage to ruin the final mix.

Scenario A: The Group with a Boss (Federated Learning)
In this setup, everyone sends their smoothies to a central "Boss."

  • The Defense: The Boss uses a Smart Filter. Instead of just averaging all the smoothies (which would let the bad one ruin the mix), the Boss uses a "Median" or "Trimmed Mean" strategy.
  • The Analogy: Imagine asking 10 people for the temperature. If one person says "1000 degrees" (a lie), the Boss ignores the highest and lowest numbers and takes the average of the middle ones. The paper shows that even with the "scrambled smoothie" (privacy), this filter still works perfectly to stop the saboteur.

Scenario B: The Group without a Boss (Decentralized Learning)
Here, there is no Boss to filter the answers. Everyone talks to everyone. This is harder because there's no referee.

  • The Defense: The group uses a Detective Game called "Approximate Decode-and-Compare" combined with "Group Testing."
  • The Analogy: Imagine the group splits into small teams to taste-test the smoothies.
    1. Compare: They check if the results from different teams match. If two teams get the same result, they are likely honest.
    2. Group Testing: They mix and match groups of friends. If a specific group's result is weird, they know the saboteur is inside that group. By testing different combinations, they can pinpoint exactly who the saboteur is without needing to taste every single smoothie individually.
    3. The Prune: Once they identify the saboteur, they throw out their smoothie and re-mix the rest.

What the Paper Actually Found

The authors didn't just dream this up; they built it and tested it with real computer models (like those used to recognize images of cats or handwritten numbers).

  • Privacy Works: They tried to "hack" the system to steal data (using attacks like "Membership Inference," which tries to guess if a specific person's photo was in the training set). The system successfully blocked these attacks, making the data look like random noise to the hackers.
  • Sabotage Works: They tried to poison the system by adding fake data or flipping labels (telling the computer a picture of a dog is a cat).
    • In the Boss scenario, the system resisted the attacks almost as well as if there were no privacy scrambling at all.
    • In the No-Boss scenario, the "Detective Game" successfully found and removed the saboteurs, allowing the group to finish the puzzle correctly.
  • Speed and Accuracy: The system didn't slow things down too much. The "scrambled smoothies" were accurate enough that the final computer brain learned just as well as it would have without the security measures.

The Bottom Line

This paper presents a "Swiss Army Knife" for secure AI. It combines a privacy scrambler (so no one sees your data) with anti-sabotage tools (so bad actors can't ruin the work). It works whether you have a central boss or a free-for-all group, and it does so without needing heavy, slow encryption that usually slows down computers. The authors proved through experiments that you can have both privacy and security at the same time.

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 →