HobbyHash Coin HOBC command center HOBC HobbyHash Coin wordmark
ChainRefreshing HeightRefreshing WalletTemporarily unavailable ExplorerRefreshing wHOBC—
Announcement Android wallet 0.2.23 can mine from your phone - Windows app updates

Published

HobbyHash Wallet for Android 0.2.23 is out. We also released a faster windows app.

You can mine the HobbyHash CPU pool from the phone. Open Start mining, choose 10% to 80% of the phone CPU, and start. The page shows your hashrate, accepted shares, and blocks found for your wallet address.

Phones already on the release app will be offered this update. You can also download it here: https://hobbyhashcoin.com/downloads/#android-wallet
Pool stats

Pool Stats Guide

Understand HOBC solo pool metrics for SHA, GPU, and CPU pools: difficulty, workers, blocks, and rejections. For network-wide race hashrate, open /network/.

Core pool stats

Active workersMiners with recent accepted shares in the active session window. This can be higher than a raw live connection count from pool software.
HashrateAn estimate based on shares over time. It can jump around, especially for small miners.
Accepted sharesValid work accepted by the pool.
Rejected sharesWork rejected by the pool because it was invalid, stale, late, or mismatched.
Rejection percentageRejected shares divided by total submitted shares.
Last shareThe most recent share submitted by a miner or pool.

Difficulty stats

  • Pool difficulty: the assigned share difficulty miners must meet for shares to count.
  • Best difficulty: the best share seen in a session or time window.
  • Network difficulty: the chain target required to find a real block.
  • A share must meet or beat network difficulty to become a block.

Worker identity

  • Worker name: the full configured miner username, usually HOBC_ADDRESS.WORKERNAME.
  • Miner address: the HOBC address before the dot in the worker name.
  • Worker suffix: use HOBC_ADDRESS.WORKERNAME, not the HOBC address alone. The address before the dot is the payout address.
  • Use a real HOBC address. Do not use BTC, BCH, DGB, exchange, or unrelated addresses.

Blocks and payout stats

  • Blocks found: blocks credited to the pool or miner when a share meets network difficulty.
  • Pending payout: a block reward that is found but not paid yet because the coinbase is still maturing on-chain (currently 100 confirmations). This is normal coinbase maturity, not a manual pool hold.
  • Confirmed payout: a payout that has completed under the pool rules.
  • Luck: a way to describe whether blocks are found earlier or later than statistical expectation. Luck is not a promise.
  • Estimated odds: probability estimates based on hashrate and difficulty. They can change quickly.

When a pool block is found, payout goes to the HOBC address before the dot in the worker name after the coinbase reaches 100 on-chain confirmations. A waiting-for-maturity status is normal coinbase maturity, not a manual pool hold.

GPU pool stats (KawPow)

The GPU pool on port 5558 uses KawPow network difficulty and accepts shares continuously in the Tri-PoW race after height 16800. Metrics at zero usually mean no connected workers — not an idle window.

GPU hashrate comes from KawPow miner shares, not SHA chain getnetworkhashps. Use the GPU pool overload page for live graphs. Compare algos on /network/.

Why hashrate jumps around

Pool hashrate is estimated from shares. Tiny miners submit fewer shares, so the estimate can be low, zero, or jumpy in short windows even when the miner is connected. Longer windows smooth the estimate but react more slowly.

Why tiny miners show low counts

A small miner may submit only a few shares per window. Low share counts do not always mean the miner is broken. Check pool URL, worker format, accepted shares, and miner logs before changing everything.

What to check first when shares reject

  • Wrong algorithm: SHA pools need SHA-256; GPU pool needs KawPow; CPU pool needs RandomX (not Ethash, etc.).
  • Wrong pool URL or wrong port.
  • Wrong wallet address or non-HOBC address.
  • Worker format typo.
  • Network latency or unstable internet connection.
  • Miner difficulty too high or too low for the device.
  • Miner firmware bug, clock issue, or old configuration profile.