A widely shared Kaspa mining post says HumPool is shutting down its pool services on June 27 and currently represents about 105 PH, or roughly 26% of Kaspa network hashrate. [1]
HumPool's own announcement confirms the key date: mining pool services are scheduled to cease on June 27, 2026 at 00:00 UTC, with final payouts of mining rewards scheduled for June 28 at 00:00 UTC. [2]
If that figure is accurate, the story is not just that one pool is leaving. It is that a large share of Kaspa hashrate may need to move somewhere else in a short window.
Mining pool movement matters because proof-of-work security is not only about total hashrate. Distribution matters too. When too much hashrate sits behind one pool, the network becomes more dependent on that pool’s uptime, policy, and operator behaviour. When miners spread across pools or solo mine where practical, the network becomes healthier.
The post urged HumPool users to switch to solo mining or another pool before the shutdown date. [1]
That makes this a story to watch carefully rather than overstate. The shutdown date is confirmed by HumPool, while the 105 PH / 26% figure should still be treated as a community-reported estimate unless matched against a live mining dashboard.
If confirmed, the interesting follow-up is where the hashrate goes. A migration into several smaller pools would be a decentralization win. A migration into one dominant replacement pool would just move the same concentration problem somewhere else.
For miners, the practical message is simple: check your pool status before June 27, confirm payout settings, and avoid waiting until the last day if your hashrate depends on HumPool.
For the wider Kaspa ecosystem, this is a useful reminder that mining infrastructure is part of the network story. Protocol upgrades get the headlines, but pool distribution is where decentralization either shows up in practice or does not.
