Mining Pool Centralization: Why It Matters and How to Spread Hash
Three mining pools control over 60% of Bitcoin’s hash rate. Two pools — Foundry USA and AntPool — collectively hold roughly half. This is a long-running concern in the Bitcoin community: theoretically, a coordinated subset of pools could censor transactions or attempt a 51% attack. This guide explains the centralization landscape, why it matters, and what individual miners can do about it.
The current landscape
Approximate Bitcoin pool hash share (consistently sourced from major pool dashboards):
| Pool | Approx share | Domicile |
|---|---|---|
| Foundry USA | 30% | USA |
| AntPool | 20% | Hong Kong (owned by Bitmain) |
| F2Pool | 10% | Asia |
| ViaBTC | 9% | Hong Kong |
| MARA Pool | 4% | USA (Marathon Digital) |
| Braiins Pool | 2% | Czech Republic |
| Other pools combined | 25% | Various |
The top 2 control 50%; the top 5 control roughly 73%. By comparison: the Lightning Network has thousands of routing nodes; the Tor network has thousands of relays. Bitcoin mining is more centralized at the pool layer than most decentralized networks would consider acceptable.
Why pool centralization matters
Three concrete risks:
1. Transaction censorship
Pools choose which transactions to include in blocks. A pool can refuse to mine specific transactions (sanctions compliance, legal pressure, political motivation). When 50%+ of hash share refuses to include certain transactions, those transactions wait longer for confirmation — sometimes never confirming.
This isn’t theoretical. In 2023, several US-based pools implemented transaction filtering to comply with OFAC sanctions list addresses. The sanctioned transactions still confirmed — but only because non-sanctioning pools (F2Pool, others) eventually included them. The fragility was visible.
2. 51% attack potential
A coordinated subset of pools controlling 51%+ of hash rate could theoretically rewrite recent blocks, double-spend transactions, or force protocol changes. The cost of a real attack is enormous (the attacking pools would destroy their own revenue stream), but the capability exists. Network security depends partly on pool operators choosing not to use it.
3. Single points of failure
If Foundry USA goes offline due to operational issues, regulatory action, or cyber attack, 30% of network hash rate is suddenly unable to mine. Hash rate would shift to other pools after a delay (typically hours), but during the transition, block production slows materially. Repeated incidents at large pools cause real network instability.
Why centralization keeps growing
Three structural drivers:
1. Variance economics favor large pools
Larger pools have lower variance in payouts because they find blocks more frequently. A miner choosing between Foundry (30% of network, finds blocks daily) and a smaller pool (1% of network, finds blocks weekly) sees Foundry as more “predictable” — and most operators value predictability.
The economics push hash rate toward the largest pools. Without explicit decentralization preference, the system naturally consolidates.
2. Pool operator infrastructure investments
Running a competitive pool requires substantial infrastructure: low-latency stratum servers globally, reliable payout rails, regulatory compliance, customer support. The capex and opex favor large operators — small pools struggle to compete on operational reliability.
3. Mining-as-a-service consolidation
Major pools increasingly offer integrated services: hosting, fleet management, firmware, hardware procurement. Operators using these services typically point their hash at the same pool that provides the services — convenient but reinforcing concentration.
What individual miners can do
Three practical actions:
1. Don’t default to the biggest pool
The marginal payout difference between Foundry (30% share) and a top-10 alternative (Braiins, MARA Pool, KuCoin Pool, etc.) is small — typically <0.5% in monthly returns. The decentralization benefit is real and free.
Recommended: pick a top-10 pool that isn’t in the top-3 by share. F2Pool, ViaBTC, Braiins, Luxor are all credible operations with full FPPS or PPLNS support.
2. Use multi-pool failover with diverse pools
Configure your hardware with 2–3 pools spanning different operators and jurisdictions. When primary goes down or implements policies you disagree with, your hash rate shifts to backups automatically.
Example diverse failover stack:
- Pool 1: F2Pool (Asia, FPPS)
- Pool 2: Braiins (Czech Republic, Score)
- Pool 3: Solo or P2Pool (no operator)
3. Run Stratum V2 if your pool supports it
Stratum V2 is a next-generation mining protocol that moves block template construction from the pool to the miner. Practical effect: even if your pool implements transaction filtering, you choose which transactions to include in your blocks. The pool still aggregates work and pays you; they don’t choose your transactions.
Adoption is rolling out. Braiins, Foundry, and several smaller pools support it. Hardware support requires firmware updates — see our firmware comparison for what currently supports SV2.
Solo and peer-to-peer alternatives
Two more aggressive decentralization options:
P2Pool
Peer-to-peer mining pool — no central operator, just miners running pool software that coordinates among themselves. Lower fees (typically 0%), no centralization concern, but operationally more complex. Total network hash share is small (~1%).
Reasonable for hobbyists and operators committed to decentralization. Not ideal for serious commercial operations where operational simplicity matters.
Solo mining
Each rig contributes individually to the network without any pool aggregation. See our solo vs pool guide. Maximum decentralization contribution, but high payout variance — not viable for most operators outside the lottery-style hobbyist case.
The honest summary
Pool centralization is a real concern that the Bitcoin community has been working on for years without fully solving. Individual miners can contribute to decentralization by avoiding the largest pools, configuring multi-pool failover with diverse operators, and adopting Stratum V2 when their pool supports it.
The economic cost of decentralization-conscious choices is small (under 1% of returns). The systemic benefit — a more resilient Bitcoin network — accrues to all holders, not just the operator making the choice.
For specific pool selection: mining pools guide. For solo as an extreme decentralization choice: solo vs pool guide. For setup including multi-pool failover: setup guide.