Looking for cheap hosting power?
Terra Hosting →
Rent Hashpower For Rabid Pool
KAS …
ZKAS …
Fee 1%
Scheme PPLNS + SOLO · custodial
Kaspa (KAS) ZKas (ZKAS)| Coin | Window | Blocks found | Expected | Luck | Avg effort |
|---|---|---|---|---|---|
| Loading… | |||||
Luck 100% = exactly as many blocks as expected; above is luckier. Effort is the work spent per block as a share of the network’s expected work (under 100% = sooner than average). Kaspa and ZKas are measured separately, from the same shares, using each network’s own hashrate.
Samples are taken once a minute from the pool’s accepted shares. Network lines (Kaspa, ZKas) can be switched on in the legend.
Measured from the node’s circulating supply over time, so it needs a few hours of samples to draw. ZKas rewards are shielded, so its supply is not public and has no emission chart.
| Coin | When | Reward | Miners credited | Pool fee | Status |
|---|---|---|---|---|---|
| Loading… | |||||
A Kaspa or ZKas block pays its reward through the DAG, in a later block, so rewards are shown when the chain has paid them — and only blocks that end up in the chain pay anything. Credits are written when the pool has received the reward.
| Coin | When | Height | Hash | Found by | Pool effort | Finder effort |
|---|---|---|---|---|---|---|
| Loading… | ||||||
Pool effort: all the pool’s work since its previous block of that coin. Finder effort: that miner’s own work since their previous block of that coin. Under 100% is luckier than average.
Read straight from each chain’s blocks: the name every pool writes into the blocks it mines. Blocks with no tag are solo miners or unbranded pools. This is a sample, refreshed every 10 minutes.
| # | Address | Hashrate | Share | Workers | Owed KAS | Owed ZKAS |
|---|---|---|---|---|---|---|
| Loading… | ||||||
| Worker | Status | Hashrate (15 m) | Hashrate (24 h) | Shares | Last share |
|---|
| Coin | When | Your credit | Reward batch | Your cut |
|---|
| Coin | When | Status | Amount | Transaction |
|---|
| # | Address | Hashrate | Share | Workers | Shares | ZKAS address |
|---|---|---|---|---|---|---|
| Loading… | ||||||
| Address | Worker | Hashrate | Shares | Last share |
|---|---|---|---|---|
| Loading… | ||||
kas.rabidmining.com : 5555 5556 — a block you find pays you 99%kaspa:YourKaspaAddress.workernamezkas:YourZKasAddress — where your ZKAS payouts go (see below)ASIC (IceRiver / Bitmain / Goldshell) — pool settings page
URL: stratum+tcp://kas.rabidmining.com:5555 Worker: kaspa:YourKaspaAddress.rig1 Password: zkas:YourZKasAddress
GPU miner (e.g. lolMiner / BzMiner / SRBMiner — check your miner’s own kHeavyHash syntax)
--algo kaspa --pool kas.rabidmining.com:5555 --user kaspa:YourKaspaAddress.rig1 --pass zkas:YourZKasAddress
SOLO: the same settings with port 5556 (stratum+tcp://kas.rabidmining.com:5556).
Which address goes where? Your Kaspa address (kaspa:…) is your account for both coins and your KAS payout address. Your ZKas address (zkas:…) goes in the password field and is where ZKAS is paid. No ZKas address yet? Mine anyway: your KAS is paid normally and your ZKAS balance keeps building here until you add one — nothing is lost. Get a ZKas address from the official ZKas wallet.
Yes. A Kaspa or ZKas block’s reward goes to one address and is paid through the DAG to the blocks that merged it, so it cannot be split between miners on-chain. The pool’s own addresses receive the rewards and the pool sends each miner their PPLNS share. Our Bitcoin-family pools are non-custodial; this one is not, and we say so up front. Every payout batch is written to the database before anything is sent, so a crash cannot pay anyone twice, and the wallets hold only what the next payout needs plus a buffer; the rest is swept to the owner’s cold wallets.
ZKas is a Kaspa-style chain that accepts Kaspa-hash work as proof of work. One kHeavyHash share is checked against both networks: if it is good enough for Kaspa it can become a Kaspa block, and if it is good enough for ZKas it can become a ZKas block. You mine once and earn both coins.
Username: your Kaspa address and a worker name, kaspa:…address.rig1. Password: your ZKas address, zkas:…. With no ZKas address your KAS is paid normally and your ZKAS balance waits for you (it is never lost). Use your own wallet addresses; if you use an exchange address, check the exchange’s minimum deposit first.
Once a day, for each coin where your balance is at least the minimum: 50 KAS and 800 ZKAS. The pool pays the network fees, so you receive the full amount. Smaller balances carry over. The ZKAS minimum sits just above the 750 ZKAS minimum deposit at the exchange that lists ZKAS today (NonKYC), so it should clear — check your own exchange.
Kaspa runs 10 blocks per second and ZKas 1 per second in a DAG. A block’s reward arrives in a later block’s payout, and only if the block ends up in the chain. The pool credits miners from what the chain actually paid it, not from blocks it merely submitted, so you are only ever credited real rewards.
Yes, on port 5556 (PPLNS stays on 5555), same login. When a block your work found pays the pool, 99% of that reward is credited to you (1% fee), in both coins. The pool works out who found each block from the chain itself: every Kaspa and ZKas reward is paid inside a later block that lists the blocks it merged, in a fixed order, and the pool matches each payment to the block that earned it and to the stratum that found it. A reward that cannot be matched to a finder is held, not paid to anyone, until we have checked it by hand. SOLO miners never share in PPLNS blocks and PPLNS miners never share in SOLO blocks. Between finds a SOLO miner earns nothing.
PPLNS: the window is at least 15 minutes of shares and at least twice the network difficulty of the paying block; each miner gets their fraction of the reward (minus the 1% fee) by the difficulty-weighted shares they have in that window.
ZKas is a private-by-default chain: balances and transfers are shielded. The pool pays you to your zkas: shielded address; amounts and recipients are not visible on a public explorer. Your balance here on the pool page is visible to anyone who knows your Kaspa address, like on our other pools.
Anything that mines Kaspa’s kHeavyHash: IceRiver, Bitmain Antminer KS, Goldshell KD/KA ASICs, and GPU miners. The Connect tab has the settings.
Hashes per second of kHeavyHash work, from accepted shares (stratum difficulty 1 = 232 hashes). Network hashrate comes from each node’s own difficulty estimate.
No. Kaspa and ZKas are their own chains. Rabid Pool is an independent project, not affiliated with either.