Mine solo.Keep the whole block.Trust nothing. Verify it.
We don’t change your luck. We prove we didn’t lose your work.
Look up your fleet
No account, no password: your Bitcoin address is your key. Enter it and your dashboard opens: every rig you have mining here, live.
Four claims, and what breaks each one.
If a claim here cannot be broken by checking something, it does not belong on the page.
- 01
The pool never holds your coins
Payment happens inside the block. No custody window, no withdrawal queue, no balance page.
WaitingPayout mode not reported right now.Block count unavailable.
The coinbase output pays the address in your worker username. Read any block we find and compare it against what you configured.
Open the block on any explorer, look at the coinbase transaction, and read the output address. It is the one you typed into your miner. There is no second hop, so there is no balance anyone here could freeze or release.
- 02
Zero fee, provable on chain
The full subsidy plus transaction fees go to whoever finds the block.
WaitingFee not reported right now./api/poolreports fee: 0. Taking a cut needs a second coinbase output, and that output is visible to anyone reading the chain.Count the outputs on the coinbase transaction. One output means the whole reward went to the finder. A pool skimming anything needs a second one, and it cannot hide it, because the coinbase is part of the block every node validates.
- 03
Stratum V2 in the core
Encrypted over Noise, implemented in the daemon, not translated in front of a V1 pool.
WaitingCould not read both copies of the key.Pin the authority key published below and check the handshake against it. The connect panel carries the same key in both encodings.
Copy the authority key from the connect panel into your miner as the pinned pool pubkey. If anything sits between you and this pool and tries to answer for it, the Noise handshake fails rather than falling back to plaintext.
- 04
Glass Ledger: a receipt for counted work
Shares, difficulty served, best share and window, signed with BIP340 against a key you pin.
You settle this one, not us. The verifier is directly below.
In plain terms: the pool writes down your address, the shares it counted, the difficulty it served, the hour and your best share, then signs that exact text so no number in it can change afterwards. Load one below and the bytes appear field by field.
Check a receipt against the published key, on this page today or in your own code. The standalone
np-custody-verifyis still in development: a static binary with no network and no dependencies, so that check will not need this pool online, or honest, or still running.
Every rig here gets a signed receipt for the work we counted.
Load one and the exact bytes the pool signed appear below, field by field, checked against the key we publish. Change a byte and watch the check fail. All of it runs in this tab, so nothing you load is sent anywhere.
Have your own receipt?
A page can always show a key that matches the signature it just checked. The pool publishes this key where you point your rig too, and miners pin it in firmware. Compare the two before you trust either. A standalone verifier will run this same check over a whole journal, where record numbers also have to run without gaps; it is still in development. How proof of custody works →
The wait, not the odds.
Solo mining pays the finder everything and pays almost nobody. Put in what you actually run and read the mean wait against Bitcoin’s difficulty.
Network difficulty 127,479,855,693,691, recorded 2026-08-19 at height 963,228. A rig at 1 TH/s waits about 17,300 years for a block at that difficulty. The same arithmetic applies at every pool on earth.
Every value your rig needs
The full reference, always on this page. Or let the setup walk you through it →
Stratum V1
Stratum V2 native
Pinning this key means your miner refuses any handshake NOT signed by it. That protects against a network attacker presenting their own key on your first connection. An unpinned SV2 connection still mines, but accepts whatever key it sees first (trust-on-first-use).
Distance to the pool is the first thing people ask about and the easiest to check for yourself. Time this endpoint from your own machine →
The odds you can’t beat. The pool you can’t match.
The odds are fixed by Bitcoin. We don’t pretend otherwise. But everything a pool actually controls (proving your work, protecting your block, wasting no hash) we engineered to be provably correct, and proved it.
Glass Ledger: proof, not promises
A cryptographic receipt for your work in three states (counted, useful, conserved), each a BIP340 signature against a key we publish and you pin yourself. You check it yourself on this page today, and a standalone verifier is in development. Nothing else in solo mining proves what happened to your hash.
Stratum V2: native, and hardened
Encrypted, authenticated mining over Noise, built in. Not a V1 pool with a translation shim. The handshake refuses nonce reuse, verifies the authority signature and wipes its keys; the binary codec bounds every read, so a malformed or oversized frame can never touch memory. Extended channels drive modern Bitaxe/NerdAxe firmware, byte-exact to the published V2 standard. V1 and V2, side by side, from one engine.
A valid block, always · never waste a hash · fuzz-verified SV1/SV2 · public-grade anti-abuse, engineered and verified, capability by capability.
Pool statistics
Pool Hashrate
Accumulating hashrate data…
Updates as miners submit shares
Bitcoin Network
Block Reward Potential
Recent Blocks
We publish every security advisory, with the date we fixed it.
A pool that hides its own defects will hide other things. Five most recent, newest first.
Miners pick the transactions their block will carry. Release notes
RFC 9116 reporting contact. Read it
Null dereference and unbounded read, found in our own review. Read the advisory
Regional accelerator live. Release notes
Rebuilt around work the pool already counts. Release notes
Every fix and version, with its date, lives in the full NexusPool changelog.
Solo mining,
answered straight.
Straight answers, no asterisks. The rest is provable: open the Glass Ledger.
Yes. NexusPool is a solo & lottery pool: when your miner solves a block, 100% of it pays straight to your Bitcoin address. The pool never holds your coins: no pool wallet, no custody window, no FPPS middleman.
Zero in solo mode, which is what every public NexusPool box runs. A true 0% fee: 100% of the block subsidy and fees go to the finder. No commission, no cut, no upstream skim.
Yes. Point any Bitaxe (Ultra, Supra, Gamma), NerdAxe / NerdQAxe, or any Stratum V1/V2 miner at the pool using your-bitcoin-address.worker as the username. It works out of the box with AxeOS.
A signed, append-only ledger. Every rig that mines here gets a receipt for the work the pool counted from it: how many shares, at what difficulty, over which window. Each receipt is a BIP340 signature against a key we publish and you pin yourself. The standalone offline verifier is still in development, so today that check runs on this page, or in your own code against the published key. It is our side of the ledger, and your own miner’s counter is the other, so you never have to take a dashboard number on faith.
Yes: native, encrypted Stratum V2 over Noise, plus Stratum V1, served side by side from a single engine. Not a translation layer bolted onto a V1 pool.
The instant a share could be a block, it’s validated and broadcast to the network first, ahead of every rate limit and check, and can fan out to multiple nodes for the fastest propagation. The block uses your own node’s witness commitment and every field is verified byte-for-byte before it ever reaches mainnet, so it can’t be silently rejected; a crash-handler and fsync journal mean a solved block survives a restart. The engine is fuzz-tested against adversarial input (connection floods, malformed and oversized packets) with zero crashes, leaks or lost shares.
Your odds are fixed by Bitcoin itself: p = 1 / (D · 2³²) per hash, the same on every pool. We show it plainly and can’t change it. What we can do is sign what we counted from you, so the dashboard number is not something you have to take on our word.
Yes: Payout Preflight. Enter your Bitcoin address and the pool rebuilds the exact coinbase it would pay you, byte-for-byte, the same construction used for every real block, then shows the amount and the raw transaction so you can re-derive it yourself. Paid on-chain straight to your address, 0% fee, non-custodial. You confirm the payout before you ever find a block.
Yes. The pool speaks standard Stratum V1, so a rented order connects like any other miner: version rolling, extranonce subscribe, an 8-byte extranonce2, and a difficulty set per rig from measured hashrate. The pool takes a rig of any size. A Bitmain Antminer S23 Hyd 3U, the largest single machine shipping today, connects the same way a Bitaxe does, and industrial rented orders have run here with the stale rate flat and no setup rejections. One thing is required on an order that size: put d= and a difficulty in the password field. Leave it empty and the connection opens at a difficulty sized for a small rig, floods, and the marketplace proxy drops it. NexusPool is not affiliated with any of them: the names identify where the rented hashrate comes from.
A from-scratch mining engine: a lean core that talks to our own full Bitcoin node (never a third party for your block templates), a real-time control plane, and a live dashboard. One engine speaks both Stratum V1 and native, encrypted Stratum V2, sets each rig’s difficulty from its measured hashrate, and streams per-rig telemetry, all non-custodial, with the Glass Ledger signing what the pool counted from each rig.
The question the FAQ did not answer.
Ask in the open if the next person will hit it too. Write privately if the answer needs your address. Either way the rule is the same, and it is short.
How support works