# What does the KAS page rate mean when ASIC share difficulty changes?

The rate on the page is the regular pool's current account rate and each Worker rate, not daily KAS. Share difficulty follows the machine class. 2Miners says it does not change miner rewards.

- Canonical: https://iotahome.site/en/learn/kas-asic-worker-hashrate
- Publisher: IOTA Watch
- Topics: Kaspa
- Published: 2026-10-24
- Updated: 2026-10-24

## At a glance

The help page assigns the lower share difficulty to GPU and KS0, and higher steps to KS1/KS2 and KS3-class machines. It says share difficulty does not change miner rewards. The monitor shows the pool's current account rate and each Worker rate. The unit is not a count of KAS. The API also offers share stats for 5 minutes, 30 minutes, and 6 hours. This page does not draw those windows as an earnings curve and does not promise a daily amount.

## Rate, share difficulty, and coins

| The figure you see | What it is not |
| --- | --- |
| The account's current rate, or one Worker's rate | Not unpaid KAS, and not profit after adding other Workers |
| A share difficulty on the help page, such as the lower step or the KS3 step | 2Miners says it does not change miner rewards. It is not a hashrate reading |
| The 5-minute, 30-minute, and 6-hour share ranges in the API notes | This page does not chart those ranges as earnings. A missing rate stays unknown |

After an ASIC moves to another share-difficulty port, the rate on the [Kaspa monitor](https://iotahome.site/en/projects/kas) is still only the hashrate the pool reports now. It is not how much KAS you will receive today. Whether this is the regular pool is in [regular-pool monitor](https://iotahome.site/en/learn/kas-mining-monitor-guide). When one row is marked offline, read [offline marks](https://iotahome.site/en/learn/kas-worker-offline-diagnostics) before you change the miner.

## What share difficulty changes

The 2Miners help page splits kHeavyHash by machine class. GPU and KS0 use the lower share difficulty, KS1 and KS2 use a higher step, and KS3 or KS3L class uses a higher step again. If you are unsure, choose the lower step. The help page recommends the high share difficulty for a very large GPU count or for NiceHash. Its own sentence says share difficulty does not change miner rewards. Use the regional host and port on the help page for your machine class. Those notes describe how to connect. They are not the hashrate of your machine.

ASIC examples put the kaspa: wallet in the Worker field. GPU examples add a dot and a rig name. Names on the page are Workers the pool returned, so you can match a machine. They are not a second balance.

## How to read the rate

The account row is the pool's current account rate. Each Worker has its own rate. Neither is a count of KAS. Do not add the rows and subtract power to invent net profit. Unpaid still belongs to the wallet, as the unpaid guide in this pack explains.

The API notes also offer share stats for an account and for one Worker, with ranges of 5 minutes, 30 minutes, and 6 hours. Those are share windows. They are not the last-24-hour reward on this page, and they are not a daily guarantee. This page does not convert those windows into coins.

## Which branch to inspect

- If the whole rate is missing, check the host and address the miner actually uses. Change the config only when they disagree with the regular pool kas.2miners.com and a full kaspa: address. An empty monitor is not a reason to change the share-difficulty port first. A SOLO account does not appear here.

- If one machine has no rate and the others do, check that its name is the Worker on the pool and that the share difficulty matches the help page for that class.

- If every rate is present and the coins look small, the rate and unpaid balance were never the same unit. One cannot prove the other wrong.

Viewing every Worker under one wallet does not turn them into extra saved devices. Free remains five saved devices per project, and Pro remains 50. Separate saved devices count only when you create them for each ASIC.

## An illustrative case

Illustrative example: suppose the help page puts a small ASIC on the lower share difficulty, the pool returns about 1.5 TH/s for that Worker, and the account's current rate is only that machine. After you move it to the KS3-class port, 2Miners still says the reward rule is unchanged, while the pace of accepted shares can differ. If the page then omits the rate, leave it unknown. Do not write 0, and do not multiply 1.5 by 24 hours to estimate today's KAS.

## Common questions

### Does a higher share difficulty earn more?

The 2Miners help page says share difficulty does not change miner rewards. A higher step is their connection advice for a machine class or for NiceHash, not a daily profit this site promises. The rate on the page also does not convert into today's KAS.

### Why is the 5-minute share window not on this page?

The API notes list 5-minute, 30-minute, and 6-hour share stats for the account and for a Worker. This page shows the current rate and the last-24-hour accounting from the pool account. It does not chart those short windows or use them to estimate earnings.

### Can I add two ASIC rates to get the account rate?

The pool supplies both the account rate and each Worker rate, and neither unit is KAS. If a row is missing, leave it unknown. Do not fill 0 to force a total, and do not treat a total as unpaid balance.

## Sources and implementation

- [2Miners · KAS help](https://kas.2miners.com/help)
- [2Miners · API documentation](https://github.com/2miners/apidoc)