Payout Preflight

Inspect Payout Preflight Results Before You Mine

Inspect Payout Preflight results before you mine: check the Bitcoin address, block reward, fees, and transaction output your rig would receive on-chain.

Inspect Payout Preflight Results Before You Mine

A solo block is rare. That is not a reason to leave the payout path vague. Inspect Payout Preflight results before your rig starts hashing, while there is still time to catch an address typo, a stale page, or a payout you do not understand.

NexusPool (nexuspool.io) builds Payout Preflight for one question: if your rig found the current Bitcoin block, where would the subsidy and transaction fees go? The answer should be your Bitcoin address, inside the block your rig finds. Nothing waits in a pool balance. Nothing needs a withdrawal request.

The current block matters. Its transaction fees can change as transactions arrive and leave the mempool. A Preflight result is therefore a check of a payout constructed for the block being worked on now, not a promise of a fixed amount for some future block.

What Payout Preflight is showing you

Payout Preflight is not an earnings estimate. It does not tell you when a block will arrive. Solo mining is a lottery, and an average wait is not a schedule. Network difficulty sets the odds at every pool.

It shows the payout structure your found block would use at this moment. Start with the destination address. It must be the Bitcoin address you intended to mine to. Then inspect the amount and the transaction construction that assigns the block reward to that address.

For a Bitcoin block, the reward has two parts: the subsidy and the transaction fees in that block. The subsidy is set by Bitcoin's consensus rules. Fees depend on the transactions included. A page showing a result for the current block can change when the pool moves to new work or when the available fee set changes.

That movement is expected. What should not change without your instruction is the destination. If Preflight shows an address you do not recognize, stop there. Do not point a rig at the pool until you know why the address differs.

The address is the first check

Copy the address from your miner configuration and compare it with the address in Payout Preflight. Compare the full string, not just the first and last characters. A display can shorten an address for readability, but your check should use the complete value when the page provides it.

This check is especially useful for a home miner moving between devices. A Bitaxe, an open-source ESP32-class rig, and an ASIC can each hold their own configuration. One old configuration can keep mining to an old address long after you changed the address in another machine.

The pool connection for Bitcoin is solo.nexuspool.io:3350. Your payout address belongs in the miner's configured identity or username field according to that miner's setup. Preflight lets you check the consequence of that choice before a found block makes it permanent.

Read the amount as a snapshot

Do not treat the displayed total as a quoted return. It is the reward available for the current candidate block under the conditions shown. The transaction fee portion can be higher or lower on the next block. The next block can also contain a different transaction set.

The useful question is not, “Will this be my payout next week?” It is, “If this work produced a valid block now, does this construction pay the full reward to my address?”

If the answer is yes, you have checked the part that matters. If a value changes after new work arrives, inspect the new result rather than assuming the old one remains current.

How to inspect Payout Preflight results

Use a slow, literal process the first time. It takes less time than correcting a mining configuration after you have forgotten which device received which setting.

First, enter or select the Bitcoin address you plan to use. Use an address you control. A self-custody wallet address is not a username. If you cannot verify control of it, do not mine to it.

Next, confirm that the displayed address matches your configured address character for character. Check the network as well. A Bitcoin payout needs a Bitcoin address. Similar-looking formats and copied labels are not a substitute for reading the actual address.

Then inspect the reward components. You should be able to distinguish the subsidy from the fees, or otherwise see that the displayed construction accounts for the whole block reward. A 0% pool fee means the reward is assigned to the miner's address in the found block: subsidy and transaction fees.

Finally, check that the result is current. If the page identifies the block being worked on, the template, or the time the result was prepared, use that context. A result tied to prior work is useful for learning how the payout is built, but it is not the active candidate once the pool has issued new work.

For a small farm, repeat this check for each distinct payout address. Workers can share one address if that is your plan. They can also use separate addresses. The important point is that the address on the miner and the address in Preflight agree for that worker's intended payout.

What changes when the network moves on

Bitcoin miners receive new work when the network finds a block. The candidate height changes. The available transactions can change. The fee total can change. Payout Preflight should be read in that context.

There is another detail worth knowing. The first job sent on a new block can carry no transactions while the pool prepares later work. That is a short-lived work state, not a statement about the reward a later template may carry. A miner who wants to inspect a fee-bearing construction should refresh Preflight after the current work has settled rather than draw a conclusion from one transition.

NexusPool measures how quickly it prepares that first work because old work is work on a block the network has already left. On the Frankfurt server, the median time from a new block header to work was 0.49 ms across 162 mainnet blocks on September 10 and 11, 2026. That early job carried no transactions. The measurement says nothing about mining odds. It describes when the pool can give a rig a new target.

For Payout Preflight, the practical consequence is simple: refresh after a block change if you are checking the current fee set. Do not expect one screenshot to describe every later block.

A preflight check is not a custody check alone

The page answers where a found block would pay. The chain supplies the final record if a block is found. The coinbase transaction in that block contains the payout output. Anyone can inspect it after confirmation.

That distinction matters. Before a win, Preflight shows the intended construction for current work. After a win, the block itself records what happened. The first check prevents a wrong destination. The later check confirms the destination in the chain's history.

This is different from a balance page that asks you to accept an internal number. With solo mining, the reward is not credited to a pool account for later distribution. The payout is part of the block your rig found.

It also means there is no honest way to promise a date or a frequency. A lower network difficulty means a shorter expected wait, not more value. More hashrate changes the rate at which your rig searches, but it does not turn an expected result into a calendar event.

If the result does not look right

Start with the address. Most apparent payout problems begin with a copied configuration, an old worker profile, or an address from a different wallet than the miner owner expected.

If the address is right but the amount changed, check whether the current block changed. Fee totals move with the transaction set. If the displayed result is old, refresh and inspect the current construction.

If you are unsure whether a miner accepted its configuration, reduce the problem to one device. Set one payout address, verify it in Preflight, then confirm the same address in that device's configuration screen. Only then copy the pattern to more rigs. This is slower than bulk editing, but it leaves less room for a single bad template to spread across a fleet.

A miner far from Los Angeles, Chicago, Frankfurt, or Singapore may see a longer round trip to the pool. That can delay when new work or status reaches the rig. It does not change the odds of finding a block. Those come from the rig's hashrate and Bitcoin's network difficulty.

Check the payout before you mine. If your rig finds the current block, you should already know the address that will receive it.