●…

help --getting-started

Point your ASIC at the pool in under a minute. There is no signup and no account system — the BCH wallet address you mine to is your identity here, and it is where the coinbase pays out.

Quick start

  1. In your miner's web interface (the pool settings page on Antminer, Whatsminer, Avalon and similar), set the Pool 1 URL to stratum+tcp://bch.harshy.site:3333. If your firmware supports encrypted stratum, you can use stratum+tls://bch.harshy.site:3334 instead.
  2. Set the worker / username to your BCH wallet address — this is the address the coinbase transaction will pay when you find a block, so double-check it. Any standard format works: legacy (1…), cashaddr (q…) or prefixed (bitcoincash:q…).
  3. Set the password to x. It is not checked. (Power users: d=500000 here requests a fixed share difficulty.)
  4. Save — the miner reconnects within seconds. After your first accepted share, your address appears in the Miners list and the My Stats page starts showing live numbers; give the hashrate averages a minute or two to settle.

Connection parameters

Stratum
stratum+tcp://bch.harshy.site:3333
TLS
stratum+tls://bch.harshy.site:3334
Username
Your BCH wallet address in any standard format: legacy (1…), cashaddr with or without the bitcoincash: prefix. Use an address whose keys you control — rewards are paid there directly and cannot be redirected afterwards.
Password
Not validated — x is the convention. One special form is recognised: d=NUMBER (e.g. d=500000) requests a fixed share difficulty instead of automatic adjustment. The minimum accepted value is 100,000.

Running more than one machine? Append a dot and a name per rig — statistics are tracked separately per worker while all rewards still go to the same address:

bitcoincash:qqj9rrt85mzdhf3mknppz7xvkxnxlxel9ynfku43nh.rig1
bitcoincash:qqj9rrt85mzdhf3mknppz7xvkxnxlxel9ynfku43nh.rig2

When to fix the difficulty: mainly rental marketplaces and very large farms, where the automatic warm-up would waste the first seconds. For everything else automatic difficulty converges within a minute and keeps share traffic optimal.

TLS encrypted connection

Port 3334 speaks the same stratum protocol wrapped in TLS: everything between your miner and the pool — hashrate, shares and above all your wallet address — travels encrypted, so nobody on the path (public Wi-Fi, hosting LAN, ISP) can read or tamper with it. It requires firmware with TLS/SSL support; if yours lacks it, plain stratum on port 3333 behaves identically. Mining results are the same either way.

Rental hashrate (NiceHash / MRR)

NiceHash MiningRigRentals
  • NiceHash: tested end to end. Create a SHA-256 order pointing at stratum+tcp://bch.harshy.site:3333 with your BCH address as the username. Auto difficulty (password x) is recommended; if you need a fixed difficulty, use d=500000 or higher.
  • MiningRigRentals: add the pool as SHA-256 with the same URL and username; choose automatic or fixed difficulty as you prefer — no special restrictions.
  • Minimum fixed difficulty: 100,000.

What solo mining means

Solo means no reward splitting, ever. Shares only measure your work so the pool can display hashrate and effort — they earn nothing by themselves. When one of your shares actually meets the network target, that share IS the block, and the entire reward goes to you alone. The flip side is variance: at 100 TH/s against a ~4.5 EH/s network you would find a block roughly every ten months on average — but it could be tomorrow, or twice in one week. Every share is a lottery ticket whose only cost is electricity.

How payouts work

There is no payout system to trust, because there are no payouts: the pool writes your address into the coinbase transaction of the block you solve, so the reward belongs to you the moment the block exists on the chain. You can verify it in any block explorer — open the block, look at the first (coinbase) transaction, and your address is the output. Coinbase outputs unlock after 100 network confirmations (roughly 17 hours); that is a Bitcoin Cash consensus rule that applies to every miner and every pool equally.

Pool Transparency Tools

In Solo mining, block rewards should go directly to your wallet, or to a trusted pool address with transparent payout records. We provide two open-source tools built specifically for BCH to decode the raw block template dispatched by any pool via the Stratum protocol, so you can personally verify the reward destination, output addresses, and pool tags.

Some opaque pools fake hashrate to boost rankings, hide block discovery and payout history, or even serve BCH block templates from endpoints labeled as BTC—meaning your hashrate could be mining a different coin without your knowledge. The tools below can help identify such risks.

Web Frontend Parser

A client-side browser tool with no backend. Paste the mining.notify JSON from your miner's log to locally parse block height, Coinbase output addresses, pool tags, block reward, and more. Supports Bitaxe, NerdQAxe series and other open-source miners.

Try Online →

CLI Stratum Inspector

Zero-dependency Python script that connects directly to any pool's Stratum endpoint to capture and decode Coinbase transactions and block metadata in real time. Reveals block reward addresses, pool tags, and payout amounts.

GitHub Repo →

FAQ

What is the pool fee?
0%, permanently. 100% of the block reward — the 3.125 BCH subsidy plus every transaction fee in the block — goes to the miner who found it. The pool's infrastructure is funded by voluntary donations (see the footer), so the fee never needs to change.
When do I get paid?
Instantly, by construction: the reward is paid in the block’s own coinbase transaction, directly to the address you mine with. There is no balance, no minimum threshold and no withdrawal step. It becomes spendable after 100 confirmations — a BCH consensus rule for coinbase outputs, not a pool policy.
What happens if the block is orphaned?
If the network extends a competing block instead of ours, our block becomes stale ('orphaned') and its coinbase is invalid — nobody gets that reward, the pool included. It is rare: the pool runs a well-connected, up-to-date node and submits blocks over a dedicated fast path to keep the orphan window as small as possible. Orphaned blocks stay visible in the Blocks list with the 'orphaned' status.
Is there a minimum hashrate?
No minimum hashrate — a USB stick and a warehouse connect exactly the same way. Note, however, that the pool enforces a minimum share difficulty, so very low-hashrate non-ASIC devices (CPUs, GPUs) may take a long time to submit an accepted share. Also understand solo variance: expected time between blocks scales inversely with hashrate — half the hashrate, double the average wait. The 'Avg time to block' figure on My Stats does this math for you.
Why do my shares reset?
The Shares counter shows work submitted since your last found block and restarts from zero after one — that's the number personal effort is computed from (shares ÷ network difficulty). The cumulative counter next to it shows your running total.
Do you support other coins or merged mining?
No. This pool deliberately does one thing: SHA-256 solo mining on Bitcoin Cash. The node tracks BCH network upgrades in lockstep so found blocks are never lost to rule changes.
How can I verify a block I found?
Every entry in the Blocks list links the finder's address. Open that block height in any BCH explorer, look at the first transaction — the coinbase — and you will see the full reward paid straight to your address. Nothing else touches it on the way, and you can check this for every block the pool has ever found.
My miner won't connect or shows rejected shares — what should I check?
In order: (1) the URL is exactly stratum+tcp://bch.harshy.site:3333 — a typo in host or port is the most common cause; (2) the username is a valid BCH address, since the pool rejects malformed ones; (3) if you set a fixed difficulty, it is at least 100,000; (4) the TLS port 3334 needs TLS-capable firmware — try the plain port to isolate the problem; (5) a restart notice on the status strip can explain a brief burst of rejects. Still stuck? Email admin@harshy.site with your address and rough timestamps.

Contact

If you encounter any issues during setup or operation, feel free to contact the pool administrator for assistance.

Admin Email: admin@harshy.site