# Why the KAS monitor is the regular pool, not SOLO A Kaspa address starts with kaspa:. ASIC and GPU Workers sit under one wallet on the regular pool. solo-kas records are not here. - Canonical: https://iotahome.site/en/learn/kas-mining-monitor-guide - Publisher: IOTA Watch - Topics: Kaspa - Published: 2026-10-22 - Updated: 2026-10-22 ## At a glance A Kaspa address starts with kaspa:. ASIC and GPU Workers sit under one wallet on the regular pool. solo-kas records are not here. ## Use kaspa: on the regular pool [Open the Kaspa monitor](https://iotahome.site/en/projects/kas), paste the full kaspa: address, and do not open the SOLO server. ## KAS regular pool, SOLO, and Workers | Observation | Next step | | --- | --- | | kaspa: then about 61 to 65 characters | This is the Kaspa payout this page accepts. | | The ASIC uses the wallet and shows many Workers | The names come from the regular pool. They share that wallet's balance. | | The help page names KS or Antminer | Those are miner classes the regular pool accepts, not SOLO and not a measurement by this site. | | It appears only on solo-kas.2miners.com | Switch to kas.2miners.com. Do not treat the two servers as one account. | ## Which KAS address should I enter? Enter the Kaspa payout on the regular pool kas.2miners.com. It starts with kaspa: and continues for about 61 to 65 bech32 characters. The 2Miners help example also starts with kaspa:. A Worker or rig name in the miner is not the address. BTC and TON payout addresses are not on this page. Do not paste a private key. Lookup does not start kHeavyHash. ## Should an ASIC use the regular pool or SOLO? This page reads only the regular pool at kas.2miners.com. On that same regular pool, the 2Miners help lists GPU miners and ASIC classes such as IceRiver and Antminer, and its miner examples use kHeavyHash. That is the pool's connection note, not a hashrate this site measured. The official API lists solo-kas.2miners.com as another server. A SOLO account does not show up here. The Kaspa site describes the network; it does not replace this pool account. ## The ASIC is running. Why is the Worker missing? Confirm the machine submits to the regular pool kas.2miners.com and the wallet is the full kaspa: address, not a SOLO host or a Worker name. An empty list only means this pool returned no name. Do not treat that as a broken machine. A missing reward stays a dash. Fetch time is the Hong Kong response clock and is not the rolling 24-hour window. See [sources and freshness](https://iotahome.site/en/learn/data-sources-and-freshness). ## Why doesn't hashrate from several ASICs match coins per machine? The pool reports an account rate and a rate per Worker, in units such as H/s, not a count of KAS. Several ASICs or GPUs may share one kaspa: wallet and use Worker names to separate rate and online status. Unpaid, paid, and the last 24 hours remain that one wallet's figures. They cannot be cut per machine. This page does not convert the rate into earnings and does not rank which machine earns more. ## What do balance, paid, and the rolling 24 hours mean? Unpaid balance is what the pool has not paid. Total paid is the sum already sent. The last 24 hours is a rolling window. It is not a UTC calendar day and not the on-chain Kaspa wallet balance. Do not add the three. A dash means this pool figure is missing. An open public statistics page does not mean this site stored that address's full history. ## How do I save and remove several kaspa: addresses? Sign in on the [Kaspa monitor](https://iotahome.site/en/projects/kas). Each line is one kaspa: address and one account. Free is 5 per project and Pro is 50. Many ASIC Workers under one wallet still use that single account. They are not priced per machine. The device overview has no extra total cap. Overview, the Mac Agent, and crash interpretation do not use KAS quota. Remove only detaches the save and does not power down an ASIC. A failed read can keep the last success and its original fetch time, marked stale. To check the source, open that wallet on the regular pool, not SOLO. ## Common questions ### Which KAS address should I enter? Enter the Kaspa payout on the regular pool kas.2miners.com. It starts with kaspa: and continues for about 61 to 65 bech32 characters. The 2Miners help example also starts with kaspa:. A Worker or rig name in the miner is not the address. BTC and TON payout addresses are not on this page. Do not paste a private key. Lookup does not start kHeavyHash. ### Should an ASIC use the regular pool or SOLO? This page reads only the regular pool at kas.2miners.com. On that same regular pool, the 2Miners help lists GPU miners and ASIC classes such as IceRiver and Antminer, and its miner examples use kHeavyHash. That is the pool's connection note, not a hashrate this site measured. The official API lists solo-kas.2miners.com as another server. A SOLO account does not show up here. The Kaspa site describes the network; it does not replace this pool account. ### The ASIC is running. Why is the Worker missing? Confirm the machine submits to the regular pool kas.2miners.com and the wallet is the full kaspa: address, not a SOLO host or a Worker name. An empty list only means this pool returned no name. Do not treat that as a broken machine. A missing reward stays a dash. Fetch time is the Hong Kong response clock and is not the rolling 24-hour window. See sources and freshness. ### Why doesn't hashrate from several ASICs match coins per machine? The pool reports an account rate and a rate per Worker, in units such as H/s, not a count of KAS. Several ASICs or GPUs may share one kaspa: wallet and use Worker names to separate rate and online status. Unpaid, paid, and the last 24 hours remain that one wallet's figures. They cannot be cut per machine. This page does not convert the rate into earnings and does not rank which machine earns more. ### What do balance, paid, and the rolling 24 hours mean? Unpaid balance is what the pool has not paid. Total paid is the sum already sent. The last 24 hours is a rolling window. It is not a UTC calendar day and not the on-chain Kaspa wallet balance. Do not add the three. A dash means this pool figure is missing. An open public statistics page does not mean this site stored that address's full history. ### How do I save and remove several kaspa: addresses? Sign in on the Kaspa monitor. Each line is one kaspa: address and one account. Free is 5 per project and Pro is 50. Many ASIC Workers under one wallet still use that single account. They are not priced per machine. The device overview has no extra total cap. Overview, the Mac Agent, and crash interpretation do not use KAS quota. Remove only detaches the save and does not power down an ASIC. A failed read can keep the last success and its original fetch time, marked stale. To check the source, open that wallet on the regular pool, not SOLO. ## Sources and implementation - [2Miners · KAS help](https://kas.2miners.com/help) - [Kaspa](https://kaspa.org/) - [2Miners · API documentation](https://github.com/2miners/apidoc)