⛏️ Mining Configuration

Fewer ports listed — your existing ports keep working

We used to give each device type its own port (Bitaxe, NerdQAxe, S21 and so on), because every port carried its own starting difficulty. Back then difficulty could not adapt to a device's power quickly enough, so picking the right port mattered. Recent work has made Miningcore's difficulty adjustment far more precise: it now settles on the right value for any device, whatever its hashrate, within minutes. Separate ports are no longer needed, so each pool shows one TCP and one TLS port. Important: the old ports have not been closed. If your miners are already running on 6613, 6616, 6617, 6618 or any other previous port, there is nothing to change — they keep working without interruption. Use the ports below for new setups.

BTC SOLO Mining Ports

Bitcoin solo mining — the full block reward goes to whoever finds it

TLS / SSL

port 6611

stratum+ssl://btc.onpool.net:6611

TCP

port 6610

stratum+tcp://btc.onpool.net:6610

BTC PPLNS Mining Ports

Bitcoin PPLNS — rewards shared in proportion to submitted work

TLS / SSL

port 6621

stratum+ssl://btc.onpool.net:6621

TCP

port 6620

stratum+tcp://btc.onpool.net:6620

BCH SOLO Mining Ports

Bitcoin Cash solo mining

TLS / SSL

port 7711

stratum+ssl://bch.onpool.net:7711

TCP

port 7710

stratum+tcp://bch.onpool.net:7710

BCH PPLNS Mining Ports

Bitcoin Cash PPLNS — proportional rewards

TLS / SSL

port 7721

stratum+ssl://bch.onpool.net:7721

TCP

port 7720

stratum+tcp://bch.onpool.net:7720

LTC+DOGE SOLO Mining Ports

Litecoin + Dogecoin merged mining, solo

TLS / SSL

port 8811

stratum+ssl://ltc.onpool.net:8811

TCP

port 8810

stratum+tcp://ltc.onpool.net:8810

LTC+DOGE PPLNS Mining Ports

Litecoin + Dogecoin merged mining, PPLNS

TLS / SSL

port 8817

stratum+ssl://ltc.onpool.net:8817

TCP

port 8816

stratum+tcp://ltc.onpool.net:8816

XMR SOLO Mining Ports

Monero solo mining

TLS / SSL

port 8821

stratum+ssl://xmr.onpool.net:8821

TCP

port 8820

stratum+tcp://xmr.onpool.net:8820

XMR PPLNS Mining Ports

Monero PPLNS — proportional rewards

TLS / SSL

port 8827

stratum+ssl://xmr.onpool.net:8827

TCP

port 8826

stratum+tcp://xmr.onpool.net:8826

LCC SOLO Mining Ports

Litecoin Cash solo mining

TLS / SSL

port 8831

stratum+ssl://lcc.onpool.net:8831

TCP

port 8830

stratum+tcp://lcc.onpool.net:8830

LCC PPLNS Mining Ports

Litecoin Cash PPLNS — proportional rewards

TLS / SSL

port 8841

stratum+ssl://lcc.onpool.net:8841

TCP

port 8840

stratum+tcp://lcc.onpool.net:8840

User / Wallet	`YOUR_BTC_ADDRESS` bc1qt57atgl5m2cetv98xetmjp8zpnwarq8h6xw7cy.NerdQaxe-1 BTC:bc1qt57atgl5m2cetv98xetmjp8zpnwarq8h6xw7cy.NerdQaxe-1
Password	`x` (or anything, not used or example for bitaxe 601 "d=1500" or a static maxDifficulty value that suits you "d=?")
Algorithm	SHA-256 (BTC/BCH) · Scrypt (LTC+DOGE) · RandomX (XMR)
Payout Scheme 1	PPLNS (Pay Per Last N Shares - Fair Shared Rewards)
Payout Scheme 2	SOLO (You are a "lone wolf"; you do all the work)
Pool Fee	3% (Lowest in the market)

NERDQAXE 5TH SETUP : Start Tutorial

Need help setting up your Bitaxe or Nerdminer?

Read Setup Tutorials on our Blog

🛠️ Common Errors & Troubleshooting

1. "Unauthorized Worker" / IP Ban

Your miner is getting 10s temporary bans in our logs.

Cause: Using a prefix like BTC: or bitcoin:.

Fix: Use ONLY your clean wallet address as username.

BTC:bc1qxs2j...

bc1qxs2j...

2. Difficulty Too High / No Shares

Miner connected but 0 Shares on dashboard.

Cause: one of two things

A fixed difficulty in the password field (something like d=8192). That switches automatic difficulty off entirely and leaves your device stuck at a value that does not match its hashrate.
The device only just connected and the difficulty has not settled yet. This is normal — it takes a few minutes for the pool to measure your hashrate and land on the right value.

Fix: put just x in the password field and nothing else. The pool sets the difficulty itself and adapts to your hardware within minutes. Which port you choose no longer has anything to do with difficulty.

3. SSL/TLS Handshake Failed

Fix: If using stratum+ssl://, make sure to use our dedicated TLS ports (BTC SOLO: 6611; BTC PPLNS: 6621; BCH SOLO: 7711; BCH PPLNS: 7721; LTC+DOGE: 8811 / 8817; XMR: 8821 / 8827; LCC: 8831 / 8841). Our German node supports full TLS 1.2/1.3 for maximum security.

root@server1 ~ # echo | openssl s_client -servername public-pool.io -connect public-pool.io:4333 2>/dev/null | openssl x509 -noout -dates
notBefore=Feb 19 01:37:55 2026 GMT
notAfter=May 20 01:37:54 2026 GMT

root@server1 ~ # echo | openssl s_client -servername btc.onpool.net -connect btc.onpool.net:6611 2>/dev/null | openssl x509 -noout -dates
notBefore=Feb 10 00:00:00 2026 GMT
notAfter=Mar 13 23:59:59 2027 GMT

4. Duplicate Shares (normal on Bitaxe / NerdQaxe)

Your miner shows 2–4% "duplicate shares"? No worries — this is a well-known behavior of the Bitaxe / NerdQaxe firmware (ESP-Miner), not a pool issue.

Cause: On job transitions the firmware occasionally resubmits the same share. This happens on EVERY pool (public-pool, ckpool, Ocean …).

Fix: Nothing to do. Your rewards and block chance are NOT affected — the pool correctly detects and ignores duplicates. Your miner works perfectly. ✅

Our Community for Help

Join X

Join Discord

Join Telegram