WeWorkBuddy

Show HN: I solo-validated Fed learning at 10M nodes with 50% Byzantine tolerance

I just finished testing a federated learning system at 10 million nodes. It maintains 82% accuracy even when 5 million nodes are malicious. Here's what happened ↓ --- *The Test (Feb 24, 2026)* 10,000,000 nodes 4,000,000 - 5,000,000 malicious (Byzantine) nodes 59 minutes 41 seconds total runtime 100% success rate Results: • 40% Byzantine (4M bad): 83.3% accuracy • 50% Byzantine (5M bad): 82.2% accuracy --- *Why this matters* Google's federated learning papers max out at ~10K nodes in production.

Read original source
Source page screenshot: Show HN: I solo-validated Fed learning at 10M nodes with 50% Byzantine tolerance
Source page screenshot · news.ycombinator.com

Source record

Recorded metrics

points · 2 votes
2026-11-09 12:15:39.760Z
cumulative since publication

Research analysis

What changed

Source account: I just finished testing a federated learning system at 10 million nodes. It maintains 82% accuracy even when 5 million nodes are malicious. Here's what happened ↓ --- *The Test (Feb 24, 2026)* 10,000,000 nodes 4,000,000 - 5,000,000 malicious (Byzantine) nodes 59 minutes 41 seconds total runtime 100% success rate Results: • 40% Byzantine (4M bad): 83.3% accuracy • 50% Byzantine (5M bad): 82.2% accuracy --- *Why this matters* Google's federated learning papers max out at ~10K nodes in production.

Version & cost evidence

Source votes: 2 votes (Nov 9, 2026 UTC; cumulative since publication); previous same-scope observation: 2 (Oct 19, 2026 UTC). These observations do not establish demand growth.

Who is affected

Identify the existing workflow this change affects before recommending an upgrade. Launch attention does not establish improvement; an API, pricing or availability change may instead create migration work.

Missing comparison points

Missing checks: old versus new behavior, affected plans and regions, availability date, compatibility, rollback path and cost under the same workload.

Migration check

Save the release or policy notice, run the same task on the old and new option, and compare outputs and the full bill. For retirement notices, verify the deadline before scheduling migration.