Foundry's 30%+ Hashrate Share Turns BIP-110 Vote Into One-Pool Decision

The Signal

Foundry Digital commands approximately 30%+ of global Bitcoin hashrate (CoinGlass). Soft fork activation under Speedy Trial precedent requires 90% of blocks over a 2,016-block difficulty window to signal readiness. A unanimous yes vote from Foundry's client base alone does not cross that threshold — but it accounts for roughly one-third of the signalling runway. In a contested vote where the remaining 70% of hashrate is fragmented across Antpool, F2Pool, ViaBTC, and smaller pools, Foundry's bloc is not a plurality. It is a structural veto in either direction. The pool that controls the margin controls the outcome.

On-Chain Context

As of the July 11–17 weekly on-chain snapshot, hashrate distribution remains historically concentrated. Foundry has held the top pool position by block production for multiple consecutive quarters (CoinGlass). The BIP-110 signalling mechanism — delegated to individual miners via hashrate-weighted ballot — introduces a layer of client democracy, but the aggregation point remains Foundry's pool infrastructure. Votes are weighted by contributed hashrate, meaning large industrial clients with multi-exahash deployments carry disproportionate influence within the pool's own internal tally. A handful of top-ten Foundry clients could constitute a majority of the pool's hashrate signal before the broader network registers a single block.

Historical Precedent

The last time pool concentration became a governance pressure point at this scale was the SegWit activation cycle. The mechanics differ — BIP-110 uses a client-vote abstraction rather than direct pool signalling — but the centralisation fault line is identical: when one pool controls a blocking or enabling share of hashrate, the governance model shifts from distributed consensus to delegated consent. The June 2022 miner capitulation event, when hashrate dropped 17% (Glassnode), demonstrated that even large pools are exposed to client attrition under margin pressure. A contested BIP-110 outcome that overrides a meaningful minority of client votes risks exactly that dynamic: hashrate migration to pools perceived as neutral arbiters.

The April 2024 halving (block 840,000) also concentrated miner economics, compressing margins and accelerating consolidation toward larger, more efficient pools — the same pools now positioned to dominate any hashrate-weighted governance event.

What to Watch

If Foundry's internal client tally reports above 75% yes while network-wide block signalling sits below 60% at the 1,008-block midpoint — the halfway mark of the 2,016-block Speedy Trial difficulty window, the point at which trajectory becomes statistically fixed — that divergence is the activation pressure event. At that spread, Foundry's client base is carrying the signal load that the rest of the network is not, and any final threshold crossing above 90% is arithmetically attributable to one pool's internal vote count. Track block template coinbase fields via mempool.space for pool-level signalling granularity; if Foundry blocks show consistent BIP-110 version bits while Antpool and F2Pool blocks do not, the decentralisation audit is no longer theoretical — it is written into the chain (mempool.space).