SoloLuck Blog · 2026-07-01
Open your Bitaxe, NerdQAxe, or Avalon Nano and it reports one hashrate. Open your SoloLuck stats page and it shows another. Sometimes they're close; sometimes the pool reads noticeably lower, or bounces around. This is almost never a fault, and you have not lost any hashrate.
The reason is simple: the two numbers are measured in completely different ways. Your miner counts the work its own chips are doing, moment to moment — a direct reading. The pool can't see your chips at all. It only sees the shares (proofs of work your miner submits over the network) and works backwards from those to estimate your hashrate. One is a measurement; the other is a statistical estimate. They rarely line up exactly, and the gap is widest in the first minutes after you connect, before enough shares have arrived to settle the estimate down.
Each time your miner produces a hash good enough to meet its assigned share difficulty (a target the pool sets for you), it submits a share. The pool counts those shares and applies a rough formula:
estimated hashrate ≈ share difficulty × number of shares ÷ time
Every share is statistical evidence of work done — more shares, or higher-difficulty shares, in a given window imply more hashrate. To keep the share stream readable, SoloLuck uses vardiff: the engine automatically tunes your share difficulty so you submit roughly one share every few seconds, whether you run a 1 TH/s Bitaxe or a 100 TH/s S19. As long as shares keep flowing steadily, the estimate settles close to your miner's own reading. Worth stressing: none of this touches your odds. Share difficulty only controls how often you report in. In true-solo mining your chance of a block depends on your raw hashrate against the network target, not on the share difficulty the pool happens to assign you.
Shares don't arrive on a metronome — they're a stream of random events (mining is a lottery at heart). So the pool averages them over several windows at once, typically 1m, 5m, 1h, 1d, and 7d.
The short windows are twitchy by design. Over a single minute, a few extra or missing shares swing the 1m figure wildly — it might read double your true rate one minute and half of it the next. The long windows pool thousands of shares, so the random noise cancels out and the 1h and 1d numbers sit much closer to your miner's steady reading.
If you want a fair comparison against the number on your miner's screen, look at the 1h or 1d figure, not 1m. The minute reading is handy for spotting a dead worker quickly, but it was never meant to be precise.
Two everyday situations make the gap look alarming when nothing is actually wrong:
1h/1d figures climb to meet your miner.:4334 ("Pro", floor 1,048,576) a tiny Bitaxe meets that difficulty so rarely that it submits only a trickle of shares — the estimate is starved of data, jumps around, and can even look dead, while the miner itself is happily hashing.In both cases the hashrate is real and fully counted toward your address. The estimate just doesn't have enough samples yet to be smooth — which is exactly why matching your hardware to the right port keeps your stats clean.
Here's the reassuring part: leave a healthy miner running and the pool's estimate and your miner's reading drift toward each other. Over a full day the 1d average typically lands within a few percent of what your hardware reports. The wobble you saw earlier was variance — the normal statistical scatter of a share-based estimate — not a leak.
Crucially, a low or jumpy pool reading does not mean lost hashrate or worse odds. Every valid share is credited, and your real chance of finding a block is driven by the actual hashes your chips produce against the network target — set by the network's difficulty, about 133.9 trillion today — which the pool's display number has no influence over whatsoever. Think of the estimate as a speedometer with a slightly shaky needle: the engine underneath is running exactly as fast as it always was. And because SoloLuck is true-solo and non-custodial, a found block pays the whole reward straight to your own address — minus the 2% fee, which is charged only when a block is actually found.
The cleanest cure for a jumpy reading is matching your hardware to the right SoloLuck port (host stratum.sololuck.io), so your share rate lands in the sweet spot vardiff is built for:
:3335 Nano — floor 1, for CPU and sub-10 GH/s miners.:3333 Lite — floor 1,024, for small ASICs (~0.5–5 TH/s, e.g. a Bitaxe).:8081 Standard — floor 131,072, for mid rigs (~2–200 TH/s).:4334 Pro — floor 1,048,576, for big or rented rigs (200 TH/s+).Match the port to your hashrate and you'll submit shares at a comfortable cadence, which makes every window — even 1m — settle faster and read truer. Remember the port changes your stats granularity and nothing else: not your odds, not your payout, not how much real work your miner does. For an encrypted link on an untrusted or rented network, add TLS via :3334. Pick for clean numbers, mine to your own address (e.g. bc1qexampleaddr….worker1), and let the averages do their thing.
Paste your address and copy the config from /setup, watch the pool on /status, and check every claim on /verify. Mine to your own address — that is what makes it truly solo.
Not ready to point a miner yet? Run your gear through the odds calculator, or join Telegram for block & record alerts — no rig required.
Join the SoloLuck community
Mine true-solo with other miners on Telegram — setup help, block alerts, and real people.
Join on TelegramRemembered with a first-party flag — no cookies, no trackers.