safety security
Local Data Did Not Prove Compliant Training
PoCoFL separates federation topology, admission policy and cryptographic proof.
Summary
PoCoFL separates federation topology, admission policy and cryptographic proof.
PoCoFL uses commitments and zero-knowledge proofs to check client contributions and whether aggregation follows a selected policy. Four proof-of-concept instantiations cover vanilla, continual, personalized and threshold-encrypted federated learning. The framework addresses compliance beyond keeping raw training data local.
Why it matters
PoCoFL separates federation topology, admission policy and cryptographic proof.
Limits and context
No additional limitation was separately recorded.
Key claims
PoCoFL separates federation topology, admission policy and cryptographic proof.
Evidence: source-2026-10-04-017
Sources
- arXiv preprint 2610.03650, original v1arXiv / submitting research authors · primary research
Corrections
: Publication note: This October 4 edition was reconstructed on October 5 after the workstation was offline. It uses original October 2 submissions from the standard Sunday-evening arXiv release, rather than claiming those papers were available for the missed 9 AM run. The date and 9 AM publication slot preserve archive chronology; October 5 developments are excluded. The September 27 Invention Desk is carried over because its replacement was generated October 5.