Introduction
Pool mining allows individual miners to combine their hashrate with other participants and receive a share of block rewards according to the pool's payout method, rather than relying on the low probability of solo-mining a block. Kaspa (KAS) uses the kHeavyHash proof-of-work algorithm, and in practical terms, Kaspa mining today is ASIC-led. GPU mining is no longer applicable to pools configured for current-generation KAS ASICs, including ViaBTC's KAS pool (ViaBTC KAS Mining guide).
Joining a Kaspa pool is primarily a configuration task: create and secure a pool account, obtain the pool's Stratum connection details, enter those details into a compatible ASIC along with a worker name, confirm the pool is receiving shares, and then select a payout method and withdrawal address. This guide does not address profitability. Electricity cost, hardware efficiency, network difficulty, pool fees, uptime, and market price all affect outcomes and are outside the scope of a connection walkthrough.
What You Need Before Joining a Kaspa Mining Pool
Before configuring a miner, confirm the following items are in place.
- A kHeavyHash ASIC miner. ViaBTC's KAS guide lists example Antminer, IceRiver, and Goldshell models as applicable hardware and states that GPU mining is no longer applicable to its KAS pool.
- A stable power supply and network connection for the ASIC.
- Access to the miner's web-based configuration interface.
- A mining-pool account, where the pool uses account-based worker names rather than anonymous connections.
- A Kaspa wallet address to receive withdrawals.
- The pool's current Stratum URL, port number, and a backup endpoint, since published connection details can change over time.
Create and Secure Your Pool Account
Registering a pool account typically requires an email address and a password. Because pool account credentials gate access to accumulated balances and withdrawal settings, consider enabling two-factor authentication before configuring or changing a withdrawal address, and use a password that is not reused from other services.
Some pools, including ViaBTC, support sub-accounts that separate mining activity by site, device group, or payout arrangement. A sub-account is an organizational feature rather than a requirement for operating a single miner; a single-ASIC setup can mine directly under the primary account (ViaBTC sub-account guide).
Obtain the Pool's Stratum Connection Details
Connecting an ASIC to a pool requires three pieces of information: the Stratum server address (pool URL), the port the miner should connect on, and the worker name the pool will use to identify that specific device's submitted shares. Because these values are maintained by the pool and can be updated, always confirm them on the pool's live documentation rather than relying on a saved configuration from a previous setup.
As a worked example, ViaBTC's pool-information page currently lists the following KAS endpoints:
| Routing option | Stratum endpoint | Primary port | Fallback port |
|---|---|---|---|
| Global | stratum+tcp://mining.viabtc.io | 315 | 3015 |
| Global | stratum+tcp://hash.viabtc.io | 315 | 3015 |
| Europe | stratum+tcp://kas.powhashing.com | 315 | 3015 |
These values are published on ViaBTC's Mining Pools Information page, which also lists PPS+ and PPLNS as the payout methods currently available for KAS. Readers connecting to any pool, not only ViaBTC, should treat the pool's own documentation as the source of truth for current endpoints.
Configure the Kaspa ASIC Miner
The configuration workflow is broadly similar across kHeavyHash ASIC firmware, though menu names vary by manufacturer.
- Locate the miner's Pool, Mining, or Stratum configuration page in its web interface.
- Enter the pool's Stratum URL and primary port.
- Enter the worker name in the format the pool requires.
- Where the firmware supports multiple pool slots, add one or more backup entries so the miner can fail over if the primary endpoint becomes unreachable. This improves connection continuity; it does not increase the ASIC's hashrate.
- Save the configuration and restart the mining process if the firmware requires a manual restart to apply changes.
For ViaBTC specifically, the username field should contain the ViaBTC account name or sub-account name, not an email address or a wallet address, with an optional custom worker label added after a period:
accountname.workername
For example:
myaccount.ks3-rack1
ViaBTC's KAS guide documents this account/sub-account-plus-worker-name format, and separately documents an optional password-field convention (for example, d=1024) for setting an initial share difficulty. This difficulty setting is a pool-specific configuration option rather than a required step for a standard setup, and published reference values should not be treated as universal recommendations (ViaBTC KAS Mining guide).
Verify That the Miner Is Working
After saving the configuration, distinguish between several related but separate measurements when checking that mining has started correctly:
- Miner-reported hashrate is the hashrate the ASIC itself displays, based on its local averaging interval.
- Pool-estimated hashrate is the pool's estimate of a worker's hashrate, calculated from submitted shares over the pool's own reporting window. It is not identical to the miner's instantaneous local reading and should only be compared against the miner display over a matching time period.
- Worker status indicates whether the pool currently sees the worker as active, offline, or inactive, typically based on whether shares have been received within a defined period.
- Rejected shares are shares the pool does not accept as valid; stale, invalid, and duplicate shares are examples of underlying rejection reasons, not separate top-level categories.
ViaBTC's KAS guide states that, as a practical matter, operators can generally review worker status and estimated earnings after the miner has been running for approximately 10 to 15 minutes, since the pool needs a short window of submitted shares to produce a stable estimate. This interval is operational guidance from ViaBTC's documentation rather than a universal pool-industry standard.
Choose a Payout Method: PPS+ or PPLNS
ViaBTC currently lists two payout methods for KAS: PPS+ and PPLNS. These determine how submitted shares are converted into reward distributions and are selected per account.
PPS+ (Pay Per Share Plus). Under ViaBTC's definition, PPS+ pays for valid submitted shares according to standard PPS accounting, and separately allocates transaction fees using a PPLNS-based method. Because the pool absorbs more of the variance associated with the block-reward component, PPS+ is typically offered at a relatively higher fee than PPLNS. The transaction-fee portion is not fixed, since it is allocated under PPLNS logic, so PPS+ does not produce entirely guaranteed or invariant earnings (ViaBTC PPS+ and PPLNS guide).
PPLNS (Pay Per Last N Shares). Rewards are distributed based on the shares a miner contributed during the pool's most recent N difficulty rounds at the time a block is found. Because payouts depend on the pool's block-finding results, PPLNS earnings can fluctuate more than PPS+ earnings over short periods, though they are typically offered at a lower fee.
Neither method should be understood as a guarantee of specific returns; both remain subject to network difficulty, pool performance, and the fee structure in effect at the time of mining.
Set Up KAS Withdrawals
Once a worker is confirmed active and accumulating pool balance, the remaining step is configuring how that balance reaches an external wallet.
- Add the destination KAS wallet address in the account's withdrawal settings, and verify it carefully before saving, since an incorrect address can result in an unrecoverable transfer.
- Review the pool's current minimum-payout threshold before enabling automatic withdrawal; this value should be checked directly in the live account interface, as it can change.
- Understand that pool-account balance and an on-chain withdrawal are distinct: the pool first credits balance to the account under its chosen payout method, and a separate withdrawal transaction later moves that balance on-chain to the specified address.
ViaBTC's auto-withdrawal feature sends funds automatically once the applicable minimum-payout condition is met, and separately allows transfers to a user's own ViaBTC main or sub-account. According to ViaBTC's help documentation, automatic withdrawals are processed once daily, within a window of 10:00 to 18:00 (GMT+8) (ViaBTC auto-withdrawal guide). Readers should confirm the current minimum-payout figure and processing schedule in their own account, since pool policies are updated from time to time.
Troubleshooting Common Connection Issues
| Symptom | Practical checks |
|---|---|
| Miner does not connect | Recheck the Stratum URL, port, worker-name format, network/DNS access, and the miner's firmware pool settings. |
| Worker shows online but pool-estimated hashrate is low | Allow for the pool's reporting window, then compare miner and pool dashboards over the same time period rather than at a single instant. |
| Rejected shares are elevated | Check network stability, endpoint selection, firmware version, and general miner health. |
| No withdrawal received | Check the configured KAS address, current pool-account balance, the minimum-payout condition, and withdrawal status in the account interface. |
| Miner stops hashing after a configuration change | Restore a known-good pool entry, review the miner's log, and confirm the ASIC retains network connectivity. |
There is no universal acceptable rejection-rate threshold that applies across all miners and pools; the appropriate range depends on the specific ASIC, network path, pool implementation, and the measurement period under review.
FAQ
Can I mine Kaspa with a GPU?
Current Kaspa mining is ASIC-led, and ViaBTC's KAS pool documentation states that GPU mining is no longer applicable to its KAS pool. Readers evaluating hardware should plan around kHeavyHash ASICs rather than GPU rigs.
What is the difference between miner-reported and pool-estimated hashrate?
Miner-reported hashrate is the ASIC's own local reading. Pool-estimated hashrate is calculated by the pool from submitted shares over its reporting window. The two are related but not interchangeable, and should only be compared over matching time periods.
Do I need a sub-account to mine with a single ASIC?
No. A sub-account is an organizational feature that can separate workers, sites, or payout arrangements across multiple devices. A single miner can be configured and operated directly under the primary pool account.
How soon can I confirm a worker is mining correctly?
ViaBTC's documentation indicates that operators can generally check worker status and estimated earnings after approximately 10 to 15 minutes of stable operation, since the pool needs a short window of submitted shares to produce a reliable estimate.
Should I choose PPS+ or PPLNS?
This depends on an individual's tolerance for reward variance and the fee associated with each method on the chosen pool. PPS+ generally shifts more block-reward variance to the pool at a relatively higher fee, while PPLNS reward amounts move with the pool's block-finding results. Neither method guarantees fixed earnings.


