Federated Learning

last updated 2026-08-31 · +7 sources in last 30d
Assessment draft · unreviewed
Viability
3/5
Drivers
3/5
Novelty
3/5
Diffusion
2/5
Impact
3/5

Timing Soon (2-5yr) · Read Fairly rated

Federated learning trains a shared model across devices that keep their raw data local, exchanging only model updates; it now works well enough to beat centralised baselines in specific edge tasks, but its privacy and robustness guarantees depend on cryptography and hardware that are still being built.

Summary

Federated learning (FL) inverts the usual machine learning pipeline. Instead of pooling data in a central store and training there, each participating device trains on its own data locally and sends only model updates to a server, which averages them into a global model. Federated Averaging (FedAvg) is the canonical aggregation rule. The claimed benefit is that raw data never leaves the device, so the approach fits domains where pooling is illegal, commercially impossible or physically impractical: patient signals, handset radio measurements, vehicle sensor streams, industrial telemetry.

The mechanism creates three new problems in place of the one it solves. First, model updates are not private by construction: gradients can be inverted to recover training data, which is why deployments layer on differential privacy, secure aggregation or secure multiparty computation. Second, those defences cost bandwidth and latency that edge devices often do not have; secure multiparty computation in particular imposes communication overhead described as prohibitive against IoT latency and energy budgets. Third, the system trusts its clients. Because the server sees only updates, a malicious participant can poison the global model, and recent work shows that in the quantum FL setting a single malicious client can cut accuracy by up to 50% under FedAvg even with popular Byzantine-robust defences in place.

The parameters that decide whether FL is the right choice are therefore: how heterogeneous and non-IID the client data is, how much communication per round the network can afford, whether the privacy claim needs to be enforceable rather than asserted, and how many clients can be assumed honest. A recurring theme in the current literature is that the answers are being pushed into hardware. Proposals include a hardware mechanism that guarantees only differentially private results can leave a device, removing the need to trust a third-party FL application that today is given full access to sensitive data, a TrustZone-based framework that moves cryptographic setup into idle windows and cuts active-phase latency by up to 74% versus synchronous secure aggregation, and a 65-nm neuromorphic encoder that supports federated learning at 357.32 nJ per training update.

A longer-standing framing places FL inside the wider privacy-enhancing technology (PET) stack alongside multiparty computation, homomorphic encryption and zero-knowledge proofs, on the thesis that securing data during processing unlocks a new market in confidential data collaboration ref. Practitioners in that stack caution that decentralisation is not automatically privacy: there is no general principle that distributed computing is more private than centralised computing, and it depends on system configuration, application requirements and the specific threat ref.

Evidence base

Open questions


Assessment drafted 2026-08-31 from up to 18 KB sources using the technology-scorecard framework; scores are a draft read pending review.

Recent mentions

Frontier questions