Same hash.Different difficulty.Still a lottery.
The difficulty is Bitcoin Cash’s. The arithmetic is on this page.
Look up your fleet
No account, no password: your Bitcoin Cash 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.
WaitingThis page reads the payout mode from the pool's live data.Payout Preflight shows the exact coinbase before you find a block.
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.
WaitingThis page reads the fee from the pool's live data./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.
WaitingThis page compares the key it shows with the key it publishes.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 the Glass Ledger works →
The wait, not the odds.
A block on any SHA-256 chain costs, on average, D · 2³² hashes. D is the chain’s own difficulty, set by the network, not by us.
A 1 TH/s rig (an arbitrary round number, not a recommendation) costs ≈60 expected years to a Bitcoin Cash block at today’s difficulty, against ≈17,308 expected years on Bitcoin at the reading above. p ≈ 1 / (D · 2³²) per hash, either chain.
That gap is between two chains, not between two pools. Solo mining is a lottery on both chains. An average is not a schedule. A smaller difficulty means a shorter expected wait. It does not mean more value: a block is worth what its chain is worth, and that is not our claim to make. This is a statement about probability, not about what a block is worth.
The Bitcoin Cash figure above is a dated reading. Bitcoin Cash retargets every block, so the live value further down this page, under Pool statistics, will already differ. See how to connect →
Every value your rig needs
The full reference, always on this page. Or let the setup walk you through it →
Stratum V1
Your username accepts a CashAddr (bitcoincash:q…) or a legacy address (1…/3…), whichever your firmware sends. We check the checksum, not the prefix, so either format works without a setting to change.
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 →
Check the receipt against the key.
Each hour the pool signs a receipt for the work it counted from each rig you point here. Check the signature with the verifier on this page or in your own code, against the key we publish.
Solo miners, auditors and developers
Solo miners
Point any Bitaxe, NerdAxe or Stratum V1/V2 rig at the pool with your CashAddr as the username, legacy addresses work too. Find a block, keep the whole thing.
Native SV1 / SV2 →Verifiers & auditors
Each rig gets a signed receipt every hour: the shares we counted, the difficulty we served them at, the window they landed in. That is our side of the ledger; compare it with your miner’s own counter.
BIP340 receipts →Developers
A C mining engine under the MIT license, with a public REST API. We haven’t published the source yet; the API is open, so you can drive your own dashboard from it.
MIT · public API →The path from your hash to a block
Difficulty explains the wait, and it sets the odds on each hash at every pool. A pool decides how fast your rig moves to a new block and what happens to a share that wins. Start with the two checks you can run today: the coinbase that would pay you, and the receipt for the work we counted.
Glass Ledger: a signed receipt each hour
Each hour the pool signs, for each rig, the shares it counted, the difficulty it served them at and the window they landed in. The signature is BIP340 against a key we publish and you can pin. Check a receipt on this page or in your own code; our standalone verifier is still in development.
Stratum V1 and V2 on one port
Point your rig at our stratum port with either protocol, and the pool reads the first bytes of the connection to tell them apart. Over V2 the connection is encrypted, and the handshake carries a signature from the authority key shown under Connect, so a rig that pins that key refuses an impostor.
Found blocks on disk first · a reason for each rejected share · the coinbase pays your address · a signed receipt each hour
Pool statistics
Pool Hashrate
Accumulating hashrate data…
Updates as miners submit shares
Bitcoin Cash Network
Block Reward Potential
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.
SV2 fleets behind one translator keep every rig past the 16th channel, and rigs that connect during a restart wait for their work instead of being turned away. Release notes
A found block goes out at once, even while an earlier one is still being retried. Release notes
A found block now reaches the network through reconnects, node restarts and replaced jobs. Release notes
Miners pick the transactions their block will carry. Release notes
RFC 9116 reporting contact. Read it
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 rig solves a block, the coinbase pays 100% of the reward to your Bitcoin Cash address inside that block. The pool keeps no wallet for you and no balance to withdraw.
Zero. Every public NexusPool region runs in solo mode at a 0% pool fee, so the block subsidy and the fees go to the address of the rig that found the block.
Yes. Point any Bitaxe (Ultra, Supra, Gamma), NerdAxe / NerdQAxe, or any Stratum V1/V2 miner at the pool using your-bitcoin-cash-address.worker as the username. It works out of the box with AxeOS.
A signed, append-only record. Each hour the pool signs, for each rig, the shares it counted, the difficulty it served them at and the window they landed in. The signature is BIP340 against a key we publish and you pin yourself. Our standalone verifier is still in development, so today you check a receipt on this page or in your own code against the published key. The receipt is our side of the ledger, and your miner’s own counter is the other.
Yes. The pool serves native, encrypted Stratum V2 over Noise and Stratum V1 on the same port, from one engine. Pin the authority key shown under Connect, and your rig refuses a handshake signed by any other key.
It writes the block to its journal on disk before it sends it anywhere, then submits it to our Bitcoin Cash node. If the pool restarts before the node accepts the block, it submits the block again on startup. These steps cover the minutes after a find. They don’t change your odds of finding one: difficulty sets those, at every pool.
Bitcoin Cash’s difficulty sets the odds on each hash your rig computes, the same at every pool, this one included. Solo mining is a lottery: the expected time on this page is an average, not a date, and your rig’s first block can land before or after it. Enter your hashrate in the odds panel to see the expected wait at today’s difficulty.
Yes: Payout Preflight. Enter your Bitcoin Cash 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, from a Bitaxe to a Bitmain Antminer S23 Hyd 3U, and a rented order connects the same way. 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 Cash 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