Should the KAS monitor use a kaspa: address or a BTC or TON payout?
The help page allows payout in KAS, BTC, or TON and shows an example of each. The monitor reads only a regular-pool address that starts with kaspa: and continues for about 61 to 65 characters. Do not paste the rig name that follows the address in the miner config. Fee wording stays with that help page: it says KAS payouts cost nothing and gives upper figures for BTC and TON. The help page does not state a minimum payout, so this page does not fill one in.
| What you paste | What this page does |
|---|---|
| kaspa: then about 61 to 65 lowercase characters | Reads it as the KAS payout on the regular pool |
| A help-page address starting with bc1, 3, 1, or UQ | Not queried. Those are optional BTC or TON payouts, not this page's KAS account |
| The address plus .rig-1 | Rejected. Leave the rig name in the miner. The help page caps it at 32 characters |
| The Kaspa site or an on-chain wallet balance | Not pool unpaid. The project site does not provide this pool account |
The pool lets you take KAS, BTC, or TON, but the monitor accepts only one kind of paste. On the Kaspa monitor, enter the kaspa: payout used on the regular pool. The regular pool versus SOLO is in regular-pool monitor. How to read unpaid and paid apart is in unpaid and paid.
Direct answer
The 2Miners help page says you can be paid in Kaspa, Bitcoin, or Toncoin. It shows examples starting with kaspa:, with bc1 or 3 or 1, and with UQ. It also says KAS payouts cost nothing, BTC stays under $0.2, and TON stays under $0.02. The help page does not state a minimum payout, so this page does not fill one in.
This page queries only the kaspa: payout. A BTC or TON payout can still settle on the pool side, but pasting it here does not open the KAS account.
Split the address from the rig name
GPU examples put a dot and a rig name after the wallet. The help page says the rig name can be empty, at most 32 characters, using English letters, digits, hyphen, and underscore. ASIC examples put the wallet in the Worker field and the password as x. The monitor wants the wallet alone. Do not include .rig-1, and do not paste only the short miner name.
The accepted form is kaspa: plus about 61 to 65 characters of the kind in the help example. Leading or trailing spaces, a private key, and a SOLO host name are not the address.
What to do next
Check the miner config uses a kaspa: wallet, then put that line in the monitor. If you actually receive BTC or TON, look at that wallet or exchange for arrival. This page does not show balances in those coins. After sign-in, bind the address to a saved device: five saved devices per project on Free, 50 on Pro. Workers listed under one wallet do not each take a slot. A device counts when you save it. The balance stays one wallet and is not copied per machine.
If a lookup fails, leave the figure unknown. Do not write 0. Fetch time is in sources and freshness.
An illustrative case
This is a format note, not a miner's bill. The help page's KAS sample starts with the characters kaspa:qzd6. If the config is that address plus .rig-1, the monitor accepts only the part before the dot. Pasting the bc1 sample does not open a KAS unpaid balance. Treating the sample address as your income is also wrong: it is a format sample on the help page.
Common questions
Why can a BTC address mine KAS but this page rejects it?
The help page treats BTC and TON as optional payout coins. The pool can pay those addresses. This page's account lookup accepts only a kaspa: payout, so those pastes do not open KAS unpaid.
Should I save the rig name with the address?
No. Leave the rig name in the miner config so the pool statistics can label the machine. The monitor stores the kaspa: wallet. Workers listed under that wallet do not automatically add device slots.
Are the help-page fees the amount that already arrived?
No. The help page says the KAS payout fee is zero, BTC stays under $0.2, and TON stays under $0.02. That is the pool's fee note, not proof this unpaid balance has arrived. The help page does not state a minimum payout, so this page does not fill one in. On-chain arrival still depends on the pool and the wallet.