Why NexusPool. Keep your reward, and check where it goes.
Your rig's block pays your own address in full, with no fee taken, and you can read that payout before your rig connects. Some reasons below describe the inside of the pool. Until we publish its source, those are our word, and the page marks them.
Start with the factsYour terms, from the first share.
Each term comes back further down as a reason, with the page that tests it.
- Pool fee
- 0%Nothing comes off the top of your block.
- Payout
- Your addressPaid in your block's coinbase. We hold no balance.
- Account
- NoneYour Bitcoin address doubles as your username.
- Receipts
- HourlySigned per rig and filed under the rig's address.
- Regions
- 4Each one a full pool with a Bitcoin node of its own.
- Protocols
- V1 + V2Either one works at the same address.
The whole block pays your address.
No fee on your block
The pool takes no cut in solo mode. A block from your rig carries a coinbase that sends all of the value, subsidy and fees, to that rig's address.
Rebuild that coinbaseNothing to withdraw
You skip the payout minimum and the withdrawal request, because your wallet receives the reward inside the block.
Read how the payout worksThe payout transaction, before you mine
Give Payout Preflight your address and it assembles, byte for byte, the coinbase this pool would build for you on the block in progress, as a raw transaction you decode yourself. Once your rig mines, firmware that parses its jobs can read the same outputs in each one.
Run Payout PreflightA wrong address fails at login
Your username is your Bitcoin address, and on Stratum V1 the pool validates it at login. It turns away an address it could not pay before your rig spends a hash on it.
Get your rig settings
Your rig keeps up, and a found block reaches the network.
New work before our node finishes
A new block arrives, and your rig gets work on top of it before our node has finished validating that block. That first job holds no transactions, and the job with fees follows once validation ends.
See the dated Frankfurt panel- Our word until the source is out
Version bits, read three ways
Firmware families write rolled version bits three different ways. The pool reads a Stratum V1 share all three ways and keeps the reading whose proof of work holds. We tested it on regtest and against firmware source; no rig has run it yet.
Read the three formats - Our word until the source is out
Shares that arrive after the switch
The pool keeps the jobs it replaced, inside a memory budget, so it still tests a share that lands on one of them as a possible block over either protocol, and gives that share no credit.
See the late share step - Our word until the source is out
The block test comes first
Over Stratum V1 the network's target is the first test a share meets, ahead of any limit the pool sets, so a rig past its share-rate limit can still send a block.
See the order of the tests - Our word until the source is out
A found block survives a restart
The pool saves a found block to disk before sending it, keeps trying until a Bitcoin node answers, and submits it again if the pool restarts with that block still in flight.
Follow a found block - Our word until the source is out
A second block skips the line
If your rig hits a block while the pool still retries an earlier one, the new block leaves for the network ahead of those retries. Slow disk writes and stalled reports no longer hold up new work for your rigs.
Read the release notes
Our count of your work, signed each hour.
Receipts signed for each rig
We sign a BIP340 receipt for every rig you run, each hour, listing how many shares we counted and the difficulty we assigned them. The signature proves what we counted, and your rig's own log of accepted shares is how you check the count.
Open Glass LedgerA signature you check yourself
Paste a receipt into the verifier on the home page and your browser tests its signature with the key we publish. The audit procedure shows how to repeat that with any BIP340 library.
Test a receiptAnchored in Bitcoin
Each hour the Los Angeles region timestamps its new receipts in a Bitcoin block through OpenTimestamps, so you can prove when a receipt existed.
Read the audit procedureThe fees in the work we serve
Block Pulse sits on a home line in Los Angeles, outside the pool, and records the fees inside our work's coinbase on every new block.
Open Block PulseAvailability, measured
The status page publishes the measured availability of each service, so you can read our record before your rig connects.
Open the status pageA changelog that names its fixes
Each release gets a dated entry that says what changed and which bugs it fixed.
Read the changelog
Close to your rig, in the protocol it speaks.
The nearest region, from one address
Your rig dials one pool address and reaches the closest region that is answering on its mining port. Each region mines on its own, so one going down leaves the others working.
Probe from your networkEither protocol, one connection
From the first bytes your rig sends, the pool tells plain Stratum V1 from encrypted Stratum V2, so both reach the same address with no translator between them.
Read the technical docsA single key to pin
Stratum V2 in every region uses a single authority key. We publish it beside the pool address so your rig can pin it.
Copy the address and keySettings for rigs, fleets and rentals
Tell the settings page your ASIC model, your fleet or the marketplace you rent from, and it works out the d= difficulty each of your connections needs.
Size your difficultyBitcoin Cash and Litecoin too
We also run a Bitcoin Cash pool and a Litecoin pool that merge-mines Dogecoin, each at an address of its own.
Mine Bitcoin Cash
The odds
Difficulty decides your odds, hash by hash, at any pool you choose. Solo mining stays a lottery, and an average wait cannot tell you which day your rig hits.
Five checks for one afternoon.
- Rebuild your coinbase
Type your address into Payout Preflight and decode the transaction it hands back.
- Measure your distance
Run the probe on the latency page from your home connection and read how many milliseconds separate you from each region.
- Size your difficulty
Pick your rig or rental on the settings page and copy the four values it gives you.
- Connect one rig
Connect one rig with those values and watch its log. Firmware that parses jobs shows their coinbase outputs, and each rejected share comes back naming its reason.
- Check your first receipt
After an hour, open Glass Ledger with your address, check the signature on your rig's receipt and hold its count against your rig's log.
Before you decide.
Can I try it with one small rig first?
Yes. A USB miner connects the same way a farm does, and Payout Preflight works for any address before you connect a thing.
Run Payout PreflightCan I leave whenever I want?
Yes. You have no balance here and no account to close, so you point your rig elsewhere and leave nothing of yours behind.
Why would I trust a pool I don't know?
For your payout you don't have to: the coinbase shows where a block pays, in Payout Preflight before you connect and in the jobs your rig receives. For the inside of the pool you do, until we publish the core's source, and the page marks those reasons as our word.
Start with your address.
Trust nothing. Verify the coinbase Payout Preflight builds for it.