AuditFL: A Contract-Backed Clearing Layer for Open Federated Learning
READ THE ORIGINAL SOURCEOpen original sourcehuggingface.co · Opens in a new tabAuditFL is a contract-backed clearing layer for open federated learning. Training and aggregation stay off chain, model artifacts sit in an assumed reliable off-chain store, and only content identifiers and economic state are recorded on chain. Clients reserve deposited update tickets and later claim refunds or rewards, while the task coordinator finalizes rounds through deterministic settlement rules. Prototypes in Python and Solidity on a local Anvil chain were evaluated on non-IID MNIST with up to 200 clients over 12 rounds. At 200 clients, the contract run issued 5,026 transactions and consumed 829.7M EVM gas. Dropout, invalid-update, and artifact-unavailability stress tests reduced inclusion but still finalized rounds.
One primary source; other links are context, not independent corroboration.
- Primary sourceHugging Face Daily Papers
- Discovery linkHugging Face
The paper page is linked. Peer review and findings have not been independently checked by AINewsIQ.
Open full article view →- Original paper+45
- Fetched source page+30
- No editor link review+0
- Original non-discussion link+5
This measures the stored source trail and editorial steps. It does not certify accuracy, peer review, or independent corroboration. Popularity adds no points.
View full scoring →Read the scoring rubric →What the source says
AuditFL is a contract-backed clearing layer for open federated learning. Training and aggregation stay off chain, model artifacts sit in an assumed reliable off-chain store, and only content identifiers and economic state are recorded on chain. Clients reserve deposited update tickets and later claim refunds or rewards, while the task coordinator finalizes rounds through deterministic settlement rules. Prototypes in Python and Solidity on a local Anvil chain were evaluated on non-IID MNIST with up to 200 clients over 12 rounds. At 200 clients, the contract run issued 5,026 transactions and consumed 829.7M EVM gas. Dropout, invalid-update, and artifact-unavailability stress tests reduced inclusion but still finalized rounds.
A READER'S EVIDENCE CHECKHow to read this signalSix questions about claims, sources, risks, and open checks
This is a signal-level guide until claim-level evidence is available. “Not recorded” means the evidence has not been assessed here; it does not mean a result is false. How we check AI news →
- 01Who is making each claim?
The claimant and whether each claim was measured or asserted are not recorded in this public brief.
- 02What was actually tested?
Not recorded per claim. Check the source for sample size, tasks, model and benchmark versions, and reproducibility.
- 03Where are the sources?
Original link: huggingface.co. Brief basis: fetched source page. Primary page date and quote locations are not established in this panel.
- 04What could mislead?
Evaluation is limited to a local Anvil chain, full MNIST with Dirichlet non-IID splits, and 12 rounds; source claims not independently checked.
- 05What is at risk if wrong?
Not assessed per claim. Consider safety, privacy, cost, and adoption decisions before relying on the result.
- 06What would change the view?
No claim-specific check is recorded. An inspectable primary method or independent replication could change the assessment.
Key findings from the stored brief
- Training and aggregation remain off chain; only content identifiers and economic state are recorded on chain.
- At 200 clients, the contract run issued 5,026 transactions, stored 2,413 off-chain artifacts (144.9 MiB), and used 829.7M EVM gas.
- Under high injected failure rates, final-accuracy changes stayed within a few tenths of an accuracy percentage point.
- Dropout, invalid-update, and unavailability stress tests reduced inclusion nearly linearly but still finalized rounds.
Evaluation is limited to a local Anvil chain, full MNIST with Dirichlet non-IID splits, and 12 rounds; source claims not independently checked.
This is a source-based abstract, not independent validation of the source's claims.
Evidence & sources
These links show where the signal came from and what the source page linked to. A linked page is context, not independent corroboration.
The paper page is linked. Peer review and findings have not been independently checked by AINewsIQ.
Timeline & updates
- Signal dated by source or discovery feed
This timestamp places the signal in the radar. It may be the discovery post date rather than the primary page's first publication date.
- Shared brief stored
AINewsIQ prepared one abstract from fetched source page.
A publication revision history is not stored for this signal. New engagement snapshots do not mean the source itself changed.
Why this may matter
Most federated learning deployments rely on a trusted coordinator for admission, aggregation, and rewards. AuditFL proposes making those on-chain round decisions attributable, replayable, and economically constrained, which may matter for open participation settings.
Limits and open questions
Evaluation is limited to a local Anvil chain, full MNIST with Dirichlet non-IID splits, and 12 rounds; source claims not independently checked.
Organization-specific financial, security, and operational effects require the organization's own context and review.
Discussion
Comments are reviewed before publication. Discuss the evidence, not the person.
No published comments yet.
Reader discussion opens with accounts. You can read the original source and published comments now.