Mining and compute monitoring: devices, rewards and troubleshooting
Choose a guide for your question: adding public identifiers, organizing devices across projects, checking reward periods or investigating failed refreshes.
Use cases and tool choice
How can I track several projects on one machine?
Link IOTA, XID, fly.ai and other identifiers to one device card. Keep device rewards, wallet balances and monthly points distinct.
Monitoring questionsWhen should I use IOTA Watch or an official dashboard?
Choose between IOTA Watch and official dashboards for saved-device monitoring, installation, runtime logs, account actions and reward claims.
Monitoring questionsCan rewards from different projects be added together?
Compare reward periods, currencies and attribution across IOTA, Vast.ai, io.net, Golem and fly.ai before interpreting a device earnings total.
Product differences
What IOTA Watch is — not the IOTA cryptocurrency
IOTA Watch is an independent multi-project monitor built around Macrocosmos IOTA Train at Home. Public Miner IDs show reported activity, yesterday's rewards and lifetime rewards. Local telemetry and controls require the optional paired Mac agent. It is not an IOTA Foundation wallet.
DisambiguationIOTA Train at Home vs the IOTA cryptocurrency
IOTA Train at Home is a Macrocosmos / Bittensor subnet. The IOTA Foundation chain, Firefly, and IOTA Layer 1 wallets are a different product.
TokenWhat SN9 / IOTA means on Train at Home
On IOTA Watch, IOTA is the Bittensor subnet 9 (SN9) alpha token used by Train at Home. It is not TAO and not the IOTA Foundation Layer 1 coin.
Add devices
How Google sign-in stores your IOTA Watch device list
Without an account, this browser keeps 3 Miner IDs per project on Free. Google sign-in binds up to 3 devices per project on Free, or 100 per project on Pro to your account so you can open the same list elsewhere.
TroubleshootingIOTA Watch says the Miner ID was not found
Not found means every active run list loaded, and this public Miner ID was not in them. Check the full SS58 hotkey before treating the device as faulty.
Status and rewards
What IOTA Train at Home device statuses mean
Contributing, waiting, and not participating come from the last official sample. An old sample time is not proof that the device went offline.
RefreshWhat “refresh interrupted” means on IOTA Watch
Refresh interrupted means IOTA Watch could not finish a successful read of official data for more than five minutes. It is not proof that the device is offline.
Data reliabilityWhere IOTA Watch data comes from and how often it refreshes
Official API sources, refresh intervals, sample timestamps and stale data: how to tell whether an IOTA Train at Home reading is current.
Training historyHow to read IOTA Train at Home training history and throughput
Read daily, weekly and monthly training trends, epoch tokens, throughput, contribution percentage and rank without confusing them with rewards.
Network statusIOTA Train at Home network status: slots, roster miners and training progress
Understand active runs, roster coverage, online versus training miners and partial network data before diagnosing an individual device.
Project comparison
IOTA
How to find your IOTA Train at Home Miner ID
Copy the public Miner ID from the Miner screen in the official IOTA Train at Home app. Use the SS58 hotkey, never a private key.
Yesterday, lifetime, and payoutsIOTA rewards explained: reconcile yesterday, lifetime and payouts
Match the IOTA amount for the same date before comparing dollars. The site attributes the next accounting day to the previous date in UTC+8. Email and the site use that same date. Lifetime is Total Earned.
USD estimateHow IOTA Train at Home rewards are shown in USD
IOTA Watch shows official subnet IOTA amounts and a public SN9 market estimate in USD. The dollar figure is not a payout.
Data and rewardsIOTA Train at Home: Miner ID vs payout coldkey
Use a public hotkey to monitor a device and a coldkey for official payouts; organize Macs that share a payout address.
TroubleshootingMac online but no rewards: should I restart?
Separate device heartbeat, app processes and official training contribution before taking action.
Monitoring questionsWhere can I check multiple Macs running IOTA together?
Track multiple IOTA Train at Home Macs using public Miner IDs. Learn which IDs to add, how to sync your list and when to check the official app.
Setup and troubleshootingHow to start IOTA Train at Home and monitor rewards
Start training in the official app, then monitor its public Miner ID. IOTA Watch is an independent monitor, not the training client or an IOTA Layer 1 wallet.
Queue and zero throughputIOTA queued or 0 tokens/s: wait or restart?
Keep training on when a recent log still says queued. Read the sample time before treating 0 tokens/s as a failure. Throughput freshness and the agent task status can disagree.
Stop and auto-recoveryIOTA training stopped but the app is open: check and recover
An open window is not proof of training. Check the button, fresh logs, and throughput time. Auto-recovery is off by default and does not need Pro. A Stop from the site will not start training again.
Applying for another tierIOTA Iron to Bronze or Silver: application and eligibility checks
Another tier goes through the official compute application, with a public coldkey and real hardware. Acceptance is emailed. IOTA Watch Pro, a new Miner ID, or repeated restarts do not replace that review. No published fixed wait or score bar is stated.
Tiers, eligibility, and layersIOTA Iron, Bronze, Silver and Gold: tiers, eligibility and layers
A tier is a name for a run group. Eligibility comes from official review and that run. A layer is one slice of the model pipeline. None of the three is a Mac model, and none is a fixed daily amount. A missing label stays unknown.
Practical checksIOTA contribution after a new training run starts
Live throughput belongs to the selected training run; accounted rewards can cover earlier runs. A new run, a layer change or re-entry into a participant list can change the current contribution display. A smaller live value alone does not establish that previously recorded rewards were removed.
Practical checksWhy IOTA reward USD values change without new tokens
The USD figure is a token amount multiplied by a market estimate. A refreshed quote can change that figure without any additional training reward. It is not a cash balance or a guaranteed execution price. Read the native IOTA amount first, followed by the quote source and its timestamp.
XID
XID mining with MMM: Mac mainnet setup and monitoring
XID is the xCoin token and MMM is the Mac miner. Set mainnet, an xpa1r address and the current pool in MMM, then save that same public address on the XID monitor. The page does not start mining.
Read three hashratesXID / MMM hashrate: workers, shares and last activity
On one address, the pool estimate, the miner report and the chain estimate can differ at the same time. Shares are accepted work, not XID received. A Worker name is not a machine count.
Balance is not yet spendableXID mining rewards vs balance: blocks and maturity
Explorer balance is not lifetime mining income. Chain-attributed blocks are a separate cell. A coinbase waits 1,000 blocks, about 3.5 days, before it can be spent. Two official texts disagree on whether the pool splits rewards.
Practical checksMMM worker renaming and XID pool history
A worker name labels the origin of pool shares; it is not a hardware serial number. After a rename, the pool may retain the old label while new shares arrive under the new one. Two rows during that reporting window do not establish that two machines are mining.
Practical checksTrace an XID pool payout to the mainnet explorer
Pool paid totals, payout transactions and wallet displays are three separate reconciliation points. Start with the individual payment and its public transaction reference. Comparing a lifetime paid total directly with the wallet’s current spendable balance mixes payment history with later transfers and other wallet activity.
Do not treat testnet as a balanceXID mainnet vs retired testnet: xpa1r and txa1r
Mainnet addresses start with xpa1r. Retired testnet A starts with txa1r. Testnet balances did not carry onto mainnet. The monitor accepts only a mainnet address that passes validation. Genesis was 2026-09-26 at 00:00 UTC.
Missing from the list is not powered offXID Worker missing: what to check before calling it offline
No Worker under an address does not prove the Mac stopped mining. Check the fetch time, whether the source marks the pool stale, and whether the address is mainnet, then look at MMM on the machine. This website cannot see the menu bar.
Quantus
Quantus QTC mining on Mac: mainnet sync and monitoring
On a Mac, confirm --chain mainnet and a node at the chain tip, then save the public wormhole address. Planck is retired. A running process is not QTC.
Data and rewardsQuantus wormhole address: check daily and lifetime QTC rewards
Use the wormhole public address your miner actually pays. Today and lifetime are indexed QTC block rewards, not a wallet balance and not an exchange balance.
When rewards are missingQuantus mining with no rewards: address, sync and index checks
Separate a real zero for today, an address absent from the index, a failed query, and a pool that pays elsewhere. Missing data stays unknown.
Practical checksCompare Quantus local sync height with the network
A progressing network does not establish that your local node is synchronized. The explorer shows the network view; local node status or logs show your own progress. Both records must refer to the same mainnet.
Practical checksKeep Quantus reward history when changing addresses
Changing configuration does not migrate reward history to a new address. A pool payout identifier and a Wormhole reward address can also belong to different lookup paths. Record their relationship before replacing either saved record.
Hashrate and blocksQuantus hashrate is not the same figure as a block reward
A local benchmark is hash attempts on that machine for a duration you choose. QTC on the monitor is an indexed block reward. One does not convert into the other, and this site does not show network hashrate.
Address and keysWhat to paste for Quantus mining: the public wormhole address only
The monitor stores the public Address only. Keep the 24 words, inner hash, miner auth token, and node private key on the machine. This page cannot spend a wormhole balance.
fly.ai
How to read the current fly.ai month: address, end time and wallet share
Look up a public 0x payout address to see the points month, that address’s month points, and its share. Share is a fraction of points, not dollars or one machine’s day.
Practical checksFind fly.ai points after a monthly rollover
The current leaderboard can start a fresh period when the month changes. Previous points, monthly allocations and claims are separate records. A lower current-month figure alone does not show that the previous month was deleted.
Practical checksReconcile fly.ai allocation, claim and wallet receipt
Monthly allocation is not the same as wallet receipt. Identify whether the page shows points, an allocated amount, claim availability or a completed claim. Each describes a different stage, and none should silently replace another in a reward total.
Address and secretA fly.ai public 0x wallet is not the miner secret
fly.ai in IOTA Watch accepts only the public payout address. A bearer secret used by the miner or the browser session is not a wallet you can look up.
Points are not cashfly.ai month points are not dollars: the share is claimed after the month
Month points and share on the monitor are the current month’s score. fly.ai splits a $FLYAI pool by points and claims on Robinhood Chain. The page does not convert points into dollars.
Several machines, one walletWhen several fly.ai machines share one wallet, month points are counted once
Month points for one public address belong to that wallet and are not added per machine. Only separately saved device records count toward three per project, or 100 on Pro. Looking inside one device does not take extra slots.
Empty pointsWhen fly.ai points are empty: no row, a zeroed day, or a month that has not rolled
A missing month row, a day zeroed for a wrong answer, or an unlinked wallet can all look empty. Match the month and the address, then check that day’s jobs on the official page. Blank is not zero dollars.
Nosana
How to read a Nosana node: running jobs and completed jobs
Paste the node’s public Solana address in the Nosana monitor. The page shows that node’s running-job count and completed-job count. Those are not a GPU count or NOS earnings.
Practical checksNosana job retries, executions and reward counting
Jobs, execution attempts and payments are not interchangeable row counts. A retry after a failure can belong to one job lifecycle. Two log entries alone do not establish two settled NOS rewards.
Practical checksNosana history after replacing a host identity
Reinstallation does not necessarily change the host identity; compare the actual address first. If the public key changed, old jobs remain associated with the old identity. A shared machine nickname does not merge two network identities.
Choose the addressNosana Host address vs wallet: which one to paste
The Nosana monitor accepts only the node’s public Solana address. A wallet signs in on the official site. A job address points at one piece of work. The wrong paste does not look up this host.
Idle or offlineNosana running jobs at 0: spare GPU or an offline host
Running jobs at 0 only means that running list is empty. Nosana’s idle GPU is spare capacity you can share. Offline is checked on the official node page. This monitor has no heartbeat.
Jobs are not payoutNosana job counts and NOS: why they are not earnings
Nosana’s docs say hosting GPUs earns $NOS. The monitor shows job counts only, and it says there is no device daily earnings figure. SOL is a chain asset, not a completion count.
When figures disagreeNosana host jobs do not match: check in this order
When the Nosana monitor disagrees with you, confirm the node public key, separate a failed read from a real zero, then check eligibility and jobs in the official console. Do not explain it with hashrate or NOS.
Akash
How to read an Akash provider: address, online flag and GPU capacity
Open the directory row with the provider’s own public address and read name, online flag, check time, and GPU capacity. Those figures are not lease income.
Practical checksAkash GPU allocation ratio versus actual utilization
Allocated GPUs divided by total GPUs describe a capacity snapshot. They do not measure kernel utilization, hours occupied over the day or the share of revenue already settled.
Practical checksAkash provider endpoint changes versus identity changes
A provider endpoint change is different from an akash1 identity change. A new access URL alone does not establish a new earnings history. A new identity likewise does not prove that old leases migrated automatically.
Which addressAn Akash provider address is not the same record as a wallet
The directory card accepts only the provider’s own akash1 address. A tenant wallet, a deployment id, or a chain balance does not open that provider record’s online flag or advertised GPU capacity.
Income boundaryAkash leases, GPU capacity, and a chain balance are not earned income
Allocated GPUs in the directory are a capacity snapshot. Active leases, settled amounts, and a wallet balance each have to be checked in their own official records.
Token balancesThe Akash monitor does not show an AKT or USDC balance
The provider card has only that provider’s directory status and advertised GPU capacity. Read AKT and USDC in a wallet. The same wallet balance is not copied into income once per saved record.
Online flagWhen an Akash provider looks offline, separate unknown, unlisted, and a directory flag
A directory mark of not online describes that check. A missing flag is unknown. An address absent from the directory is unlisted. None of the three is an automatically computed outage loss.
io.net
How to connect an io.net device: ID, read credential and today’s IO
Paste the device ID in the io.net monitor and save a read credential on your signed-in account. The page shows hardware, GPU count and UTC-day block rewards. Hire earnings and uptime are not that line.
Practical checksio.net reward history after a Device ID change
A device nickname is not the IO Explorer Device ID. If reinstallation or registration changes that ID, a shared nickname does not automatically move the old ID’s rewards into the new record.
Practical checksio.net UTC rewards versus Hong Kong calendar dates
This monitor reads io.net daily block rewards by UTC date. Hong Kong is eight hours ahead. During early Hong Kong hours, the source’s UTC day differs from the local calendar date, so date labels across projects may refer to different intervals.
ID versus keyAn io.net device ID is not the worker private key
The device ID is the UUID you paste. A worker private key and the Bearer token are secrets. The token is stored encrypted on the server, never in the ID field, and deleted on disconnect.
Idle versus hiredIs an io.net GPU idle or hired? What the monitor can show
Official device details put minutes hired, minutes served and status on each job. The monitor does not turn those into idle or hired, and it does not replace today’s IO with job earned.
Rewards versus uptimeio.net today’s IO is not the same thing as uptime
Today’s IO is that device’s block rewards for the UTC calendar day. Downtime and job uptime on official details are not converted into IO. A missing summary stays blank. A returned 0 is shown as 0.
Private readHow an io.net read credential is stored: 7 days, server only, deleted on disconnect
After sign-in, submit a Bearer token. Saving requires that the token can already read the device you entered. The credential is stored encrypted for at most 7 days, one io.net connection per account. Reading one device does not verify the whole account.
Vast.ai
How to add Vast.ai host income: Machine ID and four components
Enter the Machine ID from the Vast.ai Host machines page. The day’s USD total appears only when GPU, storage, upload bandwidth, and download bandwidth are all present. A missing line stays unknown.
Practical checksVast.ai Machine ID changes and host income history
Host accounts, nicknames and Machine IDs describe different scopes. After hardware replacement or registration, compare IDs before attributing income. A reused name does not establish continuity of a machine’s revenue record.
Practical checksReconcile Vast.ai machine income report intervals
Contract rates, rental duration and income reports are different records. A current offer does not rewrite historical revenue. Reconcile reports by Machine ID and explicit start and end times, not only a date label.
Machine and contractAfter you change a Vast.ai price, do current rentals keep the old rate?
A Vast offer can change. A rental contract keeps the price, end date, and hardware from the moment it was accepted. Unlisting only stops new rentals. The monitor’s Machine ID is still the whole machine.
Occupancy and offersDoes a Vast.ai machine’s GPU count equal the number of cards already rented?
The GPU count on the monitor is how many cards the machine registered, not how many are rented now. Minimum GPU grouping decides whether a client can take 1, 2, 4, or the whole box. Public search shows only part of the catalog.
Revenue and balanceCan a Vast.ai account balance stand in for this machine’s income today?
No. The day’s amount on the monitor adds only the four earnings lines for that Machine ID. Account credit, another machine’s earnings, and billing top-ups are not filled into the total. A missing line stays unknown.
Read-only keyWhich Vast.ai API key should the monitor use, and where does it go?
Put the key in the account connection, not in the Machine ID field. A read-only monitor needs permission to view machines and earnings. Transfers and listing changes are write permissions and should stay off that key. A refused report leaves the total unknown.
Golem
How to separate Golem GLM: rolling 24 hours and lifetime
Rolling 24-hour GLM and lifetime GLM on one Golem node are separate records. A missing figure stays unknown. Neither is a wallet balance or a Hong Kong calendar-day payout.
Practical checksGolem provider history after a Node ID change
A Node ID identifies the provider, while its payout wallet is another configuration field. Reinstallation can leave the same wallet associated with a different node identity. Separate public statistics do not establish loss of wallet funds.
Practical checksWhy Golem rolling 24-hour GLM can decrease
A rolling 24-hour window continuously drops older records. A decrease can mean an earlier payment left that window, not that funds were debited or that today’s Hong Kong income became negative.
Node id and walletA Golem node id is not the same field as the GLM wallet
The monitor opens a provider with the node id on Golem Stats. The Ethereum address you set for GLM at install can be a different key. Looking like 0x is not enough to swap them.
Offered capacity and tasksCapacity you offer on Golem is not a paid task
Cores, memory, and disk are capacity you are willing to share. Task counts in status and GLM on the monitor are separate. Capacity or an online flag does not mean a task was paid.
GLM payments and capacityConfirm the Golem payment network before reading GLM; capacity is not a balance
GLM is an ERC-20 on Ethereum and Polygon. A provider must be set to mainnet explicitly. Testnet amounts have no real value. Shared cores and disk are not those balances, and rolling GLM on the monitor is not spendable wallet funds.
Provider offline checksWhen a Golem provider looks offline, check the process, virtualization, and UDP
A provider runs on x86-64 Linux. The guide’s healthy status is a running service, a valid VM, and an OK driver. A Mac can open the monitor. A Mac cannot be the provider. Offline does not set GLM to zero.
NOID
Why NOID payouts differ from daily earnings
A rolling 24-hour paid figure, unpaid balance and lifetime paid are three different ledgers. An InnovLab source has no daily-earnings column. On the NOID monitor, read the source first, then match that column on the pool.
Address not foundNOID address not found: InnovLab and Parano1d pool checks
Not found usually means the address, the pool, or the lack of accepted shares. The monitor asks Parano1d Pool first and InnovLab only after a miss or a failure. The two ledgers are not merged.
Practical checksNOID pool switching and outstanding balances
Pools maintain separate ledgers. Reusing an o1 payout address does not move the old pool’s unpaid balance into the new pool when the miner endpoint changes. A shared chain address is not a shared pool account.
Practical checksNOID confirmation differences across source snapshots
Nodes and pools observed at different times can show different confirmation counts. Chain confirmation, pool maturation and payout are separate stages. A confirmation count is not a device’s daily earnings.
Hashrate and workersNOID wallet workers: hashrate, online and saved-device slots
Parano1d Pool places measured and reported hashrate in the same roughly 10-minute window. Address online does not mean every worker is online. Balance is shared by address. A separate saved device is what uses the five-per-project or Pro 100 slot.
Balance and paymentsNOID owed, paid and the 18-confirmation unlock
Owed is still on the pool ledger. Paid is what that pool has already recorded as paid. Parano1d Pool says rewards unlock after 18 confirmations and labels the current-round fee at 3%. Do not add InnovLab’s confirmed unpaid to the other pool’s owed.
Pool, node and coinNOID pool, node RPC and the o1 address are different things
A Parano1d node’s JSON-RPC defaults to localhost port 9601. Parano1d Pool states main.parano1d-pool.fun:3784. The monitor reads a public miner account on a pool, not your node, and not IOTA.
Acurast
Acurast monitoring: managers, processors, rewards and balances
Enter a mainnet manager or processor public address to inspect processor heartbeats, manager-level paid rewards and wallet balances.
Practical checksAcurast phone replacement and shared manager rewards
Processor identities identify phones, while manager rewards may cover several processors. If old and new phones share a manager, assigning the full manager total to both device cards would duplicate the same reward.
Practical checksAcurast free, frozen and total balance accounting
Frozen amounts describe restrictions on balances rather than a new asset outside the total. Wallet holdings also differ from manager paid rewards. Adding total, free and frozen figures indiscriminately double-counts funds.
Processor and managerAcurast manager vs processor address: which one should I enter?
A manager may own multiple processors. A processor lookup does not turn manager aggregate rewards into per-device income.
What the phone is doingAcurast heartbeat vs online state and running jobs
An on-chain heartbeat records recent reporting, not a running customer job. Check task state, rewards and local device state separately.
Where rewards are assignedAcurast daily paid ACU rewards vs cumulative rewards and balance
Paid compute rewards are manager aggregates. Hong Kong-day increases, cumulative values and wallet balances are separate measures.
The phone looks stoppedTroubleshoot Acurast offline processors, stale heartbeats and missing data
Distinguish an old chain heartbeat, a failed source read and a stopped local app before checking the same processor.
Pearl
Pearl PRL on Mac: check pool hashrate, workers and rewards
See whether the Mac miner points at Kryptex or LuckyPool, then select that same source in PRL monitoring. The ledgers do not stand in for each other, and a Kryptex username is not a prl1 address.
Practical checksCompare PRL pool payment methods without inventing hourly income
Payment methods distribute risk and accounting differently. Verify the current PRL pool, mode and fee documentation. A historical PPS report from one pool does not establish guaranteed hourly income on another pool’s SOLO service.
Practical checksPRL shared worker names and physical device attribution
Multiple machines using the same address and worker label can appear as one pool row. That aggregate cannot reveal each machine’s measured earnings. Dividing it equally by the number of devices would create an unsupported attribution.
Two poolsSame valid prl1: why Kryptex and LuckyPool keep different records
Kryptex and LuckyPool each keep their own shares and balances. No record on one side does not imply none on the other. Unpaid amounts are separate account rows. Do not fold them into one income figure.
Workers and sharesA PRL worker is not another wallet: where accepted shares show up
A worker is a machine label under an address. The balance still belongs to the prl1 address. Kryptex monitoring here has no accepted-share count. LuckyPool shows one only when that pool returns it.
Balances and payoutsPRL locked, unlocked, paid, and rolling 24 hours
On LuckyPool, locked is not payable yet, unlocked is the unpaid balance, and paid is the cumulative payout. The recent column is a rolling 24 hours on LuckyPool and today’s UTC day point on Kryptex. Those two are not comparable across pools.
Miner programsWhich miner fits PRL on a Mac versus a discrete GPU
On Apple Silicon, use the range the Pearl Metal author lists: M1 through M5, not Intel Macs. For a discrete GPU, use the programs and GPU families named on Kryptex’s page. Sample hashrates are not an earnings promise. A calculator separates gross reward from electricity.
Monero
Which Monero address should the XMR monitor use?
The Monero monitor accepts a public Kryptex address only: 95 characters starting with 4 or 8, or 106 characters starting with 4. A username, OpenAlias, or a full wallet/worker line will not open a row.
Practical checksXMR payout address changes and old pool balances
Pools account by the payout identifier supplied to them. Changing it does not merge the old record into the new one. Different subaddresses may belong to one wallet without becoming one pool account.
Practical checksPrivacy when sharing an XMR pool monitoring link
Monero’s on-chain privacy does not make a pool statistics link information-free. A public lookup can expose worker labels, hashrate and payment statistics. A device nickname may also reveal a location or employer.
Payout address and pool sourceWhich payout address matches the Kryptex XMR source?
A Kryptex username used for auto-convert, an address from another pool, and a solo: prefix do not open the Kryptex XMR record. The payout string has to be the public address the miner used when it submitted shares.
RandomX hashrateWhy does the XMR monitor hashrate disagree with local RandomX?
The monitor hashrate is Kryptex’s per-worker pool rate, added only when every worker has a number. It is not the live XMRig line, not network hashrate, and not XMR already posted.
Unpaid balanceWhat do XMR unpaid, paid, and UTC today each mean?
Unpaid is what Kryptex has not sent yet. Total paid is what it has already sent. The page keeps the two lines apart and does not print its own total. Adding UTC today on top of both counts that day again when it already sits in one of the lines. Neither line is the wallet balance. Today exists only when the reward series has that UTC midnight.
Offline and sharesWhere are accepted XMR shares when a Worker says offline?
Offline is the status word Kryptex gives that Worker, and the last share is a time. This site does not show an accepted-share count, so a missing count is not zero shares. Offline does not stop the miner.
Ethereum Classic
Why the ETC monitor rejects an Ethereum address and SOLO
The IOTA Watch ETC page reads only a 0x payout on etc.2miners.com. An Ethereum balance, a BTC or TON payout, and a SOLO pool are not that unpaid ETC.
Practical checksETC pool switching without losing track of unpaid balances
The same ETC 0x address can have independent ledgers on different pools. Changing the connection routes future shares; it does not automatically clear the old unpaid balance or transfer it into the new pool.
Practical checksETC payment thresholds, payout cycles and receipt checks
Reaching a displayed amount does not establish that an on-chain payout was sent. Check whether it is payable balance, the pool’s current conditions, its payment cycle and whether a transaction actually exists.
Two 0x networksWhy the same 0x string is not both ETC and ETHW
ETC and ETHW can both use 0x plus 40 hex characters. The 2Miners help names ETC as ETCHash and points miners at etc.2miners.com. That is not the ETHW ETHash pool.
Rig name and algorithm textWhy the monitor still reads Workers on the ETCHash account when the miner says etchash
The 2Miners help says to choose ETCHash, while software examples print etchash or ethash. The monitor reads the regular pool account by payout address. A Worker is only a rig name.
Three reward figuresWhy ETC's last 24 hours, unpaid, and paid are not one total
The last 24 hours is a rolling window. Unpaid is ETC still on the pool account. Paid is what the pool has recorded as paid. None of the three is a wallet arrival. A missing figure is a dash, not zero.
Zero or blank hashrateWhen the ETC pool hashrate shows 0, do you check shares or income first?
Account hashrate is the rate the pool reports. A shown 0 means that reading is 0. A dash means it was not read. The help page says share difficulty does not change miner rewards, and this page does not convert the rate into ETC.
Ravencoin
Why the RVN KawPoW monitor separates wallet and Worker
One RVN address on 2Miners has one unpaid balance, one paid total, and one 24-hour reward. A Worker is a rig name under that wallet, not a second income.
Practical checksRVN worker renaming and overlapping hashrate windows
Pool averages retain historical shares, so an old RVN worker label may not drop to zero immediately after a rename. A KawPoW worker name is a share label rather than a verified physical-device identifier.
Practical checksMatch RVN pool payouts with wallet transactions
A pool payout is a transfer, while rolling 24-hour rewards are an accounting window. A payment can include earlier accumulated balances, so receipt today does not mean the entire amount was earned today.
Address and rig nameWhich RVN wallet address and Worker name this monitor accepts
This page accepts a Ravencoin address that starts with R. The rig name goes after the address, separated by a dot. A BTC or TON payout address cannot be looked up here.
How to read hashrateIs the RVN hashrate an effective rate, and does share difficulty change rewards?
This page shows the pool's current hashrate for the address and each Worker's hashrate. It does not compute a second effective rate. 2Miners says share difficulty does not affect miner rewards.
Rewards and payoutsWhich RVN figure is unpaid, already paid, or a 24-hour reward?
All three figures are the 2Miners account ledger, not the official wallet balance. Shares and block maturity are not these three figures. The 2Miners RVN help page does not state a confirmation count or a minimum payout.
Reading offlineIf an RVN Worker is offline, is that rejected shares or a zero balance?
Offline is the pool's state for that rig name. It is not a rejected-share ratio, and it does not set the address balance to zero. This page does not show accepted or rejected share counts.
Zcash
Why the ZEC monitor accepts only transparent t-addresses
The ZEC monitor queries only a transparent t1 or t3 on zec.2miners.com. Shielded and unified addresses are not that pool account, and the rate unit is S/s.
Practical checksZEC pool payouts before moving funds to a shielded address
A pool payment to a transparent address and a later wallet transfer into shielded funds are separate activities. This transparent-address monitor does not track shielded balances. An unavailable shielded balance does not cancel the original payout record.
Practical checksZEC address replacement and old worker history
A worker record belongs to the pool and payout address used when shares were submitted. Replacing a t address can create separate histories even if the worker label stays unchanged.
Transparent addressesWhen a ZEC t1 or t3 is this pool's account
Both t1 and t3 can be this page's transparent account. The help example is a t1. Shielded addresses, unified addresses, and BTC or TON payout strings are not that account.
Solutions and hashesWhy ZEC S/s is not H/s and not a coin count
This page shows the Equihash solution rate as S/s. The pool API still places that number in a hashrate field. Share difficulty does not change miner rewards, according to the help page.
Rewards and paymentsHow to read ZEC unpaid, paid, and the last 24 hours separately
Unpaid is ZEC the pool has not sent, paid is the cumulative total sent, and the last 24 hours is a rolling window. None of the three is a shielded balance or a BTC or TON payout.
A worker is missingZEC worker missing: check the address before the miner
An empty list can mean the address shape was refused, the miner is not on this pool, or the help page's Worker field is the wallet so the name is not a rig nickname. Empty is not a hardware verdict.
Kaspa
Why the KAS monitor is the regular pool, not SOLO
Read a KAS account on the 2Miners regular pool with a kaspa: address. SOLO is another pool type, and share difficulty is not daily profit.
Practical checksKAS mining with non-native payouts: keep assets separate
Mining network, accounting asset and payout asset can differ. A non-native payout must retain its own denomination. BTC amounts are not KAS amounts, and a native KAS address lookup cannot establish a different payout asset’s wallet balance.
Practical checksKAS ASIC replacement with a reused worker label
A pool worker label is not an ASIC serial number. Reusing it after replacement can mix old and new shares within an averaging window. That mixed average cannot directly validate the new ASIC’s advertised performance.
Address and payout coinShould the KAS monitor use a kaspa: address or a BTC or TON payout?
This page accepts only a kaspa: payout. 2Miners can pay BTC or TON, and those addresses are not queried here. A short Worker name is not the wallet.
ASIC rate and share difficultyWhat 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.
Unpaid and paidHow to read KAS unpaid, paid, and the last 24 hours
All three are the regular pool's books for one kaspa: wallet, on different windows. They are not the on-chain balance and cannot be split into income per Worker.
Worker offlineWhat should I check first when a KAS Worker shows offline?
Offline is the regular pool's mark on one Worker, plus a last-seen time. It does not prove whether power, the fan, or the network failed, and it is not zero hashrate.
Midstate
How to check Midstate MDS pool rewards, addresses and units
Paste the 64-character lowercase MSS address the miner is using. MDS monitoring reads one LuckyPool ledger: unpaid (locked plus unlocked), cumulative paid, a rolling 24-hour block allocation, nonces/s, and workers. Other pools are not added in.
Practical checksMDS miner upgrades and reusable MSS payout identity
A software upgrade and a payout-identity change are different actions. Midstate reusable MSS addresses and one-time WOTS addresses are not interchangeable. Check current pool instructions before carrying an old configuration into a new miner.
Practical checksMDS solo: payout labels and pool statistics
A mining-mode prefix is distinct from the underlying wallet address. LuckyPool instructions identify SOLO with solo:ADDRESS. Sharing an underlying address does not make statistics from different payment modes interchangeable.
Address mismatchMDS monitoring says the address is missing: MSS, one-time keys, and LuckyPool
If the miner is running and MDS monitoring reports no such address, check LuckyPool and the 64-character lowercase MSS from wallet generate-mss. A one-time wallet receive and mw1 do not belong in the field.
Rate and denominationMDS nonces/s are not H/s, and they are not divided into mMDS
MDS monitoring shows the account rate with a decimal prefix and nonces/s. kMDS, mMDS, and gMDS are protocol coin steps. Balances stay base MDS integers. Hashrate is not converted into coins.
Three amountsWhy MDS locked, unlocked, and paid do not match
Unpaid on MDS monitoring is unlocked plus locked. Cumulative paid is a separate transfer total. The last 24 hours are a block allocation for a window of exactly one day. Accepted shares are not a payout.
Workers and sharesWhen an MDS worker looks offline, accepted shares are not paid MDS
On MDS monitoring a worker is online when its last share is inside 15 minutes. Account amounts are not split per worker. Accepted and rejected counts on the miner screen are not a payout.
Blocknet
How to check BNT mining rewards: Blocknet addresses and payments
Paste the full mainnet payout address Seine resolved. Read hashrate, the immature estimate, confirmed unpaid, queued payment and cumulative paid as separate lines. Shortnames, other pools and USD quotes are outside this page.
Practical checksIdentify privacy Blocknet BNT versus BLOCK and Bancor
Here BNT refers to the privacy PoW network at blocknetcrypto.com. The names Blocknet and BNT also appear in unrelated projects. Prices, explorers and reward rules from old BLOCK or Bancor must not be substituted.
Practical checksBNT local daemon status versus pool share activity
Daemon reachability, wallet synchronization and miner share submission are different states. A local tool such as bntop and a public pool observe different scopes. A responding node alone does not prove that a pool worker is submitting work.
Choose a backendSeine on CPU or NVIDIA: which address to copy before you look up BNT
Seine documents CPU and NVIDIA backends, the default pool URL, and shortname resolution. The monitor accepts only the full mainnet address fixed in the log. Check the driver and the port on the miner.
Several machinesSeveral machines on one BNT address: when the balance is counted twice
One public address on bntpool.com can list several Workers. Unpaid and paid wallet amounts are counted once per address. Saving that address on two rows does not create two incomes.
Payout stateBNT immature, queued, and paid: which amount is still at the pool
Read bntpool.com's immature estimate, confirmed unpaid, queued payment, and cumulative paid as separate lines. 1 BNT is 100 million atomic units. A missing line is unknown, not zero. The start page states no minimum payout.
Hashrate dropsBNT hashrate fell over 24 hours: a gap, a zero, or one machine
The address line is bntpool.com's 24-hour samples. Worker lines are samples collected from lookups over the last 24 hours, not a continuous curve. A gap is not zero.
Compute Substrate
How to check CSD mining hashrate and G-pools payments
Look up a public addr20 to see the G-pools 1-hour hashrate, unpaid balance, confirming amount, and lifetime paid. Coins stay on the whole address.
Practical checksCSD addr20 records across different mining pools
The same addr20 identifier does not merge pool ledgers. Shares, unpaid amounts and payment history remain source-specific. Changing a miner endpoint does not transfer a G-pools balance into another pool.
Practical checksCSD chain balances do not establish a pool account
A chain balance shows asset holdings, not that a particular pool received shares for that address. Ordinary transfers, payments from another pool and current mining activity can coexist without creating an account on the selected source.
Payout addressWhere to copy the CSD addr20 and what to paste into monitoring
Monitoring accepts only the 40-character addr20 used with the miner’s --address flag. Do not paste a private key, wallet file, RPC URL, or another G-pools chain.
Hashrate unitsWhat CSD H/s and per-Worker hashrate mean
The account and each Worker show the pool’s about-1-hour average in H/s. That is not a count of CSD and does not prove GPU or ASIC hardware.
Unpaid and paidHow to tell CSD unpaid, confirming, and lifetime paid apart
Confirming is not payable yet, unpaid is the confirmed balance waiting for the next payout, and lifetime paid is the historical sum. Adding them is not today’s earnings.
Not foundWhen a CSD address or Worker is missing, which kind of empty is it?
A full-page miss means the pool has no shares or payments for that address yet. A missing Worker, or 0 H/s, can still leave the address ledger open. Do not treat all three as one restart.
Ergo
Which 9-address belongs on the ERG Autolykos monitor?
Paste the mainnet address your miner uses as the ERG payout on 2Miners. Only a 9-address that checks out opens the public account on erg.2miners.com. If the payout is already BTC or TON, this page cannot read it, and you should not change the miner for that. The separate SOLO category is not merged into this row.
Practical checksERG P2PK address changes and historical pool payments
One wallet application can manage several addresses while the pool still accounts by the submitted payout address. A new P2PK address does not automatically inherit the old address’s workers, unpaid balance or lifetime payouts.
Practical checksERG raw amounts, decimals and displayed rewards
A raw integer can represent the smallest unit while a display reports ERG. A different magnitude does not establish a reward surge. Applying decimal conversion twice to an already normalized field is equally incorrect.
P2PK versus coinbase scriptWhy the ERG monitor accepts a 9-prefix P2PK and not the P2S coinbase script
On Ergo mainnet a 9-address is P2PK. Protocol mining rewards lock in P2S. 2Miners’ ERG payout example starts with 9. The monitor looks up that pool payout address only.
Autolykos and worker hashrateHow to read Autolykos worker hashrate on the ERG monitor, without splitting it into income
The miner algorithm is Autolykos. The monitor shows the pool’s current account hashrate and each worker’s hashrate. Those figures are not ERG income split per worker. Short-window charts are not on this page.
Balance, paid, and 24-hour rewardWhat do balance, paid, and the 24-hour reward mean on the ERG monitor?
All three figures belong to the same 9-prefix payout address. The pool accounts 1 ERG as one billion base units. A missing figure stays unknown, is not shown as 0, and is not copied per worker.
Worker offline or no sharesWhere to look when an ERG worker is offline or no shares show up
This page shows whether the worker is online, its hashrate, and when it was last seen. Share charts from 5 minutes to 6 hours stay on the pool account page. Share difficulty does not change rewards, as the help page states.
Zephyr
Which pool and which address does the ZEPH monitor read?
The ZEPH monitor reads a mainnet standard address on the regular zeph.2miners.com pool: hashrate, Workers, unpaid, paid, and a rolling 24-hour reward. It is not a network balance and not a Monero address.
Practical checksKeep ZEPH mining rewards separate from ZSD and ZRS
Assets in the Zephyr ecosystem do not share one unit simply because they share a protocol. Native ZEPH mining statistics cannot be added directly to stable-asset or reserve-share quantities, nor valued with one interchangeable quote.
Practical checksZEPH immature balances after changing pools
Switching pools does not automatically mature an old pool balance or move it to the new source. Its accounting stage and maturation rules remain those of the original pool.
Address typeZEPH uses RandomX. Why is a Monero address rejected?
RandomX is the mining algorithm, not an address format. The ZEPH monitor stores only the Zephyr mainnet standard address used on zeph.2miners.com. Monero, integrated, and subaddresses are rejected.
Workers and the algorithmWhere does a ZEPH RandomX Worker name come from?
2Miners mines ZEPH with RandomX. Distinct rig names identify Workers, and a name may be left empty. Share difficulty does not change the reward. The Worker count in the monitor is not your saved-device count.
Rewards and paymentsWhy ZEPH unpaid and 24-hour figures are not a payout time
The ZEPH monitor shows the pool account’s balance, cumulative paid, and rolling 24-hour reward using 1e12. It does not list immature blocks separately, and it does not store a fixed minimum payout.
Hashrate at zeroA ZEPH Worker shows 0. Has the rig stopped?
A ZEPH Worker hashrate of 0 means the pool reported 0 for that row. A blank hashrate is unknown. The offline flag and last heartbeat say whether the pool still treats the rig as online.
Bitcoin
How do I check Bitcoin hashrate and Workers on CKPool?
Paste one mainnet payout address on the Bitcoin monitor. The page shows that address's one-hour hashrate and Workers. A dash means the source published no amount, not daily BTC.
Practical checksCKPool best share difficulty versus a Bitcoin block
Best share records the highest share difficulty in a reporting scope. It is neither a BTC amount nor proof of a valid block. A Solo outcome must be reconciled against an actual block and its reward transaction.
Practical checksOrganize CKPool addresses without duplicating worker hashrate
Address totals and the workers underneath them are hierarchical views of the same work. Adding both duplicates hashrate. A payout-address change also requires separating observations before and after the transition.
Solo rewardsCKPool solo is not daily income or an ordinary shared pool
CKPool pays the mining reward only when that address finds a block. Hashrate does not become daily BTC. Current terms stay on the operator site, and a dash is an unpublished amount.
Worker namesHow should a CKPool wallet address and several Workers be named?
The miner username is the Bitcoin address plus an optional dot and Worker name. The monitor stores the address. The password is not a login, and a Worker has no balance of its own.
Hashrate windowWhy can a CKPool hashrate window lag when shares are sparse?
The monitor shows only that address's one-hour hashrate. A minimum difficulty of 10000 makes low-hashrate shares sparse, so the page can mark a miner offline after about 10 minutes without a share. That is not daily income.
Missing recordHow do I troubleshoot a CKPool address with no record?
No record and an address that is not accepted are two paths. Low hashrate can also have no user stats yet under difficulty 10000. An empty amount is not 0 BTC.
EthereumPoW
Which 0x address belongs on the ETHW monitor?
The EthereumPoW monitor stores only a 0x payout address for the 2Miners ETHW pool. Bitcoin, TON, and a Worker suffix are not accepted. Missing lifetime paid stays unknown.
Practical checksETHW mining and non-native pool payout reconciliation
A pool may offer payment in another asset, but native ETHW monitoring does not automatically cover every conversion path. Mining accrual, conversion and receipt are separate stages of the same value, not three additional rewards.
Practical checksETHW payouts when a wallet displays the wrong network
Identical 0x formatting does not establish that the wallet is viewing ETHW. Ethereum, ETC and ETHW maintain separate records, so selecting another network can show a different balance for the same address string.
Address and networkWhy the same 0x text does not prove the chain is ETHW
0x plus 40 hex characters is only a shape. Ethereum, Ethereum Classic, and EthereumPoW can all use it. The IOTA Watch ETHW page reads ethw.2miners.com and follows the help page's ETHash, not ETC's ETCHash.
Rigs and sharesWhy an ETHW rig hashrate is not a split of the wallet
One 0x address can have several rigs. Address hashrate, each rig's hashrate, and unpaid balance are three different readings. The help page says share difficulty does not change miner rewards, and the monitor does not split the balance by hashrate.
Balance and payoutsWhy ETHW unpaid, 24-hour reward, and paid do not match
Unpaid, lifetime paid, and the 24-hour reward are three amounts. Unpaid, the rolling 24 hours, and paid are already shown as ETHW and mean different things. Missing paid stays unknown.
Offline checksWhen ETHW hashrate is empty, what do you check first?
Hashrate on the monitor comes from the ethw.2miners.com account, not the speed on the miner's own screen. Check ETHash, the three hosts on the help page, and the rig name before the pool's offline mark.
TensorCash
TensorCash monitoring: five pools, workers and TSC balances
Choose your mining pool to see address-level throughput, workers and unpaid balance. Sign in to save addresses with their pool.
TensorCash lookupHow to check TensorCash pool workers and throughput
Look up a TSC address on the pool you use, then compare workers, reporting windows and throughput units.
TensorCash lookupTSC wallet balance vs pool unpaid balance and daily rewards
Separate chain balances, pool accounting and payouts when reading TensorCash mining records.
TensorCash lookupTensorCash address not found, missing workers or stale data
Check the address, selected pool, original source and timestamps before interpreting missing TSC data.
Practical checksTensorCash N/s versus PoI/s: compare the source units
Miners and pools can expose different throughput units. N/s and PoI/s are not interchangeable merely because both are rates per second. Conversion requires an explicit source definition and the conditions under which it applies.
Practical checksTensorCash paused pools and historical payout records
A retained pool website or old statistics page does not prove that it still accepts mining. Current operation, API readability and historical payouts are separate facts. A static online label is insufficient when a current notice says otherwise.
For practical workflows and troubleshooting, browse the blog.