Backend
AuditFL: A Contract-Backed Clearing Layer for Open Federated Learning
arXiv cs.DC0 views
arXiv:2610.41278v1 Announce Type: new Abstract: Federated learning (FL) keeps raw data local, but most deployments still rely on a trusted coordinator for client admission, checkpoint distribution, update collection, aggregation, and rewards. This paper presents AuditFL, a contract-backed clearing layer for auditable FL in open settings. AuditFL keeps training and aggregation off chain, stores model artifacts in an assumed reliable off-chain artifact store, and records only content identifiers and economic state on chain. Clients reserve update tickets with deposits, publish update identifiers, and later claim refunds or rewards; the task coordinator publishes global checkpoints and finalizes rounds through deterministic settlement rules. The design does not remove the aggregator, but makes its on-chain round decisions attributable, replayable, auditable, and economically constrained. We implement AuditFL as both a deterministic state-machine prototype and a Solidity contract on a local Ethereum-compatible Anvil chain. On full MNIST with Dirichlet non-IID splits, 12 rounds, and up to 200 clients, AuditFL preserves the Plain FL learning trajectory while its overhead follows closed-form control-plane models. At 200 clients, the contract run issues 5,026 transactions, stores 2,413 off-chain artifacts (144.9 MiB), and consumes 829.7M EVM gas, dominated by per-client reserve and publish calls. Controlled dropout, invalid-update, and artifact-unavailability stress tests reduce inclusion nearly linearly but still finalize rounds, with final-accuracy changes remaining within a few tenths of an accuracy percentage point even under high injected failure rates.
Source:https://arxiv.org/abs/2610.41278PreviousFalcons: Pushing the Speed-Ratio Limits of Lossy Compression for Parallel Scientific ApplicationsNextMigrating a Legacy Scientific Application with an AI Coding Agent: NICAM from Fortran to Kokkos
Related posts

When "Not Found" Doesn't Mean "Never Happened"
0dev.to
Blameless Postmortems: A Leader’s Guide to Learning From Incidents
0dev.to

The Model Predicts Itself
0dev.to
Designing Clean REST APIs: Common Anti-Patterns and How to Fix Them
0dev.to

Dengan osFoundry Operator, agen menjalankan aplikasi dan setiap aksinya tercatat
0dev.to
Hold-Out Self-Validation Cannot Certify the Accuracy of Photogrammetric Reconstructions
0arXiv cs.RO