Is my NerdQAxe++ more likely to find a block on SoloLuck than elsewhere?

No. The odds are identical on every solo pool — they're set by your hashrate against the whole network, not by the pool. SoloLuck only changes your fee, payout style, and latency. At ~4.8 TH/s a single NerdQAxe++ statistically expects a block on a scale of thousands of years, here or anywhere.

Which port should I use for a NerdQAxe++?

Use :3333 (Lite). That tier is built for the Bitaxe/NerdQAxe class and handles stock ~4.8 TH/s — and a modest overclock — comfortably. The bigger tiers (:8081 Standard, :4334 Pro) are for much larger iron and would just starve your share feed. The port never affects your odds.

What do I put in the username and password fields?

Username is your own bc1... Bitcoin address, optionally with a worker name like bc1qyouraddress.nerdqaxe. That address is your payout — SoloLuck is non-custodial, so a solved block pays straight to it on-chain. The password is ignored; type anything.

When does the 2% fee get taken from my NerdQAxe?

Only on a block you actually solve, as a single coinbase output. Every other moment — which, realistically, is all of them — you pay nothing, because nothing is being paid out.

Has anyone actually found a block with a NerdQAxe on SoloLuck?

No block has been solved on SoloLuck yet, by any device, and most of the current hashrate is our own test rigs — including the NerdQAxe++ these notes are written from. We'd rather tell you that plainly than sell you a fairy tale.

SoloLuck

NerdQAxe++ Solo Mining: Pointing a 4.8 TH/s BM1370 Board at SoloLuck

← back to pool

Your live odds with a NerdQAxe++

At about 4.8 TH/s and the current network difficulty of 133.87T, the statistical mean time for a single NerdQAxe++ to solve a block solo is:

Avg time to a block

≈ 3.8k yr

Your share of the network

1 in 216.4 million

Recommended tier

:3333

“Avg” is the statistical mean — real luck swings wildly either way, which is the whole point of solo. The numbers move with the network; run your own on the odds calculator.

What the NerdQAxe++ actually is

The NerdQAxe++ is shufps' four-chip cousin of the Bitaxe family: 4× BM1370 ASICs (the same silicon as the Bitaxe Gamma) on one board, rated around 4.8 TH/s at roughly 15 J/TH, so it draws on the order of 60-80 W at stock depending on your tuning. It runs a fork of AxeOS, has its own LCD/web UI, and joins your WiFi like any small ESP-class miner.

We are not guessing at this one. SoloLuck's own test fleet includes a NerdQAxe++ (we call it jm198), so the notes below are first-hand, not spec-sheet copy. It is a genuinely lovely little machine: quiet, cool by ASIC standards, and about 4× the raw hashrate of a single Bitaxe — which matters less than you'd hope, for reasons we get to next.

The honest part: 4.8 TH/s is still a lottery ticket

Solo mining is a lottery, and we will not pretend otherwise. A block is found by whoever's miner first hashes below the network target; more hashrate buys you more tickets, not better odds per ticket. At ~4.8 TH/s against a network running in the hundreds of EH/s, a single NerdQAxe++ statistically expects to solve a block on a timescale of many thousands of years. That is the math on every solo pool on Earth — the odds are identical everywhere.

What a pool can change is only three things: fee, payout style, and latency. Nothing else. If a site implies your NerdQAxe will "hit faster" on their pool, close the tab. Run the numbers yourself on our solo mining odds calculator, and read solo vs pooled mining if you'd rather take small, steady payouts instead of a near-zero shot at a whole block.

Full disclosure: no block has been solved on SoloLuck yet, and most of the hashrate currently on the pool is our own test rigs — including this very NerdQAxe++. We'd rather you know that than discover it later.

Which tier port to use

SoloLuck splits miners by hashrate onto difficulty-matched ports so your share rate stays sane. Host is stratum.sololuck.io (148.230.98.87) on all of them.

Port	Tier	Fit for the NerdQAxe++?
`3333`	Lite	Recommended. Bitaxe/NerdQAxe class. Stock ~4.8 TH/s lives here happily, and so does a modest overclock.
`3335`	Nano	No. Difficulty 1 is for NerdMiner / tiny ESP32 / sub-100 GH toys — far below this board.
`8081`	Standard	Mid-size single ASICs; the start difficulty is overkill for one NerdQAxe and would thin out your share feed.
`4334`	Pro	No. This is the S19-class / high-hashrate tier. Its start difficulty would starve a 4.8 TH/s board of shares.
`3334`	TLS	Encrypted stratum if your firmware fork supports it. Otherwise stick to Lite.

When in doubt, :3333. Wrong-port mining still works — it just makes your share interval clumsy. It does not change your odds.

AxeOS-fork setup, step by step

The NerdQAxe++ runs a fork of AxeOS, so the pool config screen is near-identical to a Bitaxe. From the device web UI:

Stratum Host: stratum.sololuck.io
Stratum Port: 3333
Stratum User: your own Bitcoin address — a bc1... bech32 address you control, optionally with a worker name, e.g. bc1qyouraddress.nerdqaxe
Stratum Password: anything at all — x is fine. It is never checked.

That address is your username and your payout. SoloLuck is non-custodial: there is no account, no balance held by us, no withdrawal button. If this board ever solves a block, the coinbase pays straight to that address on-chain. So triple-check it — a typo is a donation to the void. Save, and within a minute or two the dashboard at /setup should show your worker submitting shares.

Thermals and tuning, from our own unit

First-hand notes from running jm198:

Four BM1370s on one board put out more heat than a single Bitaxe — the stock fan copes, but it wants airflow and breathing room, not a closed shelf.
Watch the per-chip temps in AxeOS, not just the average. We've seen one corner chip run hot while the board average looked fine.
Overclocking is real but earns less than it looks: pushing frequency raises both hashrate and draw, and we hit a hard wall where one of ours pulled over 8 A and tripped overcurrent. We detuned the frequency to bring it back under spec. More tickets, but watts and noise climb faster than the odds improve.
Whatever you clock it to, it stays a small board — keep it on the Lite tier at :3333. The higher tiers are for far bigger iron and will only starve your share feed.

Stock is the sweet spot for a home device: quiet, cool, ~15 J/TH, and the lottery odds are the same as a screaming overclock anyway.

Why a SEA miner might point it here

Since the odds are identical everywhere, the only honest reasons to choose SoloLuck are the three things a pool can actually change:

Fee: 2%, and only ever as a single coinbase output on a block you solve. The other 99.999...% of the time you pay 0% because nothing is being paid out.
Payout style: true per-miner solo on ckpool -B, paid on-chain to your own address. No custody, no minimum, no middleman.
Latency: our Jakarta node is roughly 6 ms from much of Indonesia and SEA versus ~250 ms to US pools, which means fewer stale shares. AtlasPool's HK anycast is further for an Indonesian miner; ckpool and public-pool sit in the US/AU. See the side-by-side on /compare.

The site speaks 10 languages (en/id/ms/ja/th/ko/zh/vi/tl/hi), and the people running their NerdQAxes hang out on Telegram at @SoloLuckPool. Come for the latency, stay for the company — just don't quit your job over a 4.8 TH/s lottery ticket.

Ready to take a ticket?

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.

Get the setup config →

Not ready to point a miner yet? Run your gear through the odds calculator, or join Telegram for block & record alerts — no rig required.

More guides

Browse all guides →