How to Switch From HumPool to Kat Pool: A Step-by-Step Migration Guide

Switching from HumPool to Kat Pool is a configuration change, not a migration in the scary sense. You point your miner at a new stratum address, keep using the same Kaspa wallet address you already mine to, save, and restart. There is no on-chain transaction, no new wallet, and nothing to move. The whole process takes a few minutes per rig, and you can keep your old pool configured as a failover if you want a safety net. Here is exactly how to do it.

Why are miners moving to Kat Pool?

Two reasons come up most often. The first is that miners want a pool they can audit: Kat Pool is 100% open source, so its payout logic, fee handling and reward scheme are inspectable rather than something you have to take on trust. The second is economics. Kat Pool charges a 0.75% topline fee but rebates 33% of it as NACHO, for an effective fee around 0.5% — and 0% for holders of NACHO tokens, Nacho Kats NFTs or KATCLAIM NFTs. The minimum payout is a low 10 KAS on a transparent PROP (proportional) reward scheme, so earnings reach your wallet sooner. If HumPool is winding down or you simply want lower effective fees and open-source transparency, the move is straightforward.

If you want the full side-by-side before committing, the Kat Pool vs HumPool breakdown shows exactly what changes, and the pool comparison puts Kat Pool next to the rest of the field.

What do you actually need before you start?

Almost nothing. The only thing that truly matters is your Kaspa wallet address — the one you want payouts sent to. You do not need to back up any pool-side data, export keys, or create an account first; your address is your identity on the pool, and payouts go to whatever address you set as your miner's username. It is worth jotting down a worker name per rig (for example, rig1 or s19-garage) so you can tell your machines apart on the dashboard. That is the entire prep list.

Kat Pool connection details

• Stratum URL: stratum+tcp://kas.katpool.com:3333
• Host: kas.katpool.com — a single global anycast endpoint that automatically routes you to the nearest of seven regions, so you do not have to pick a regional server.
• Port: any of 1111–8888 will work; 3333 is recommended.
• Username: your Kaspa wallet address, optionally as address.workername.
• Password: a placeholder such as x. Kaspa stratum pools ignore this field, so the exact value does not matter.

The step-by-step migration

The steps below apply to essentially any ASIC or GPU miner — the labels differ slightly between firmwares, but the fields are always the same: a pool URL, a worker/username and a password.

1. Have your Kaspa address ready. This is the only thing you carry over from your old pool; everything else is new configuration.
2. Log into your miner's web interface (or your fleet management tool) the same way you do for your old pool. Find the Pools, Mining or Miner Configuration page.
3. Set the stratum URL to stratum+tcp://kas.katpool.com:3333. Some firmwares ask for the host and port in separate fields — in that case enter kas.katpool.com and 3333 and leave the protocol prefix off if it is added automatically.
4. Set the worker/username to your Kaspa address, optionally with a worker name appended as address.workername (for example, kaspa:yourwalletaddress.rig1). This is what determines where your KAS is paid.
5. Set the password to x (or leave whatever the field defaults to). It is not used for payouts.
6. Save the configuration and restart or apply, so the miner reconnects to the new pool.
7. Open the dashboard at app.katpool.com and confirm your worker appears. It can take a minute or two for the first connection to register.
8. Verify the worker is healthy: you should see accepted shares climbing and a reported hashrate that lines up with what the machine showed on your old pool.
9. Once you are satisfied, remove the old HumPool entry — or keep it configured in a lower priority slot as failover. More on that below.

How do failover and multiple pool slots work?

Most ASIC firmwares let you configure three pool slots, used in priority order. The miner mines the first reachable pool and only falls back to the next slot if the one above it stops responding. To migrate with a safety net, put Kat Pool in the first slot and leave your old pool in the second. Your rig mines Kat Pool normally, and if Kat Pool were ever unreachable it would temporarily fall back rather than sitting idle. Each slot has its own URL, worker and password fields, so you can use the same Kaspa address across all of them. Once you have run clean on Kat Pool for a while, you can clear the old slots entirely.

What should you expect for the first payout?

Kat Pool pays out on a PROP (proportional) scheme with a 10 KAS minimum. You accrue a share of each block proportional to the work your workers submitted, and once your balance crosses 10 KAS it is paid to the address you set as your username — no manual withdrawal step. Because the threshold is low, smaller miners see their first payout sooner than on pools with 50–100 KAS minimums. Time to first payout depends on your hashrate, so run your hardware through the Kaspa mining calculator for an estimate rather than relying on a fixed number.

Do you need to move your wallet or do anything on-chain?

No. Switching pools never touches the blockchain and never requires changing wallets. The pool simply sends mined KAS to the address you configured as your worker username, so as long as you keep using the same address, your payouts continue to land in the same place. There is nothing to migrate on-chain, no keys to export, and no downtime beyond the few seconds your miner takes to reconnect.

The takeaway

Moving from HumPool to Kat Pool is repointing your miner to stratum+tcp://kas.katpool.com:3333, keeping your Kaspa address as the username, and confirming accepted shares on the dashboard. You get an open-source pool, an effective fee around 0.5%, and a low 10 KAS payout — without touching your wallet. New to mining Kaspa generally? The Kaspa mining guide covers the full setup from scratch.