Mining Receipts
Mining Receipts Show the Work Your Rig Sent
Mining receipts record the work a pool counted from one rig each hour. Learn what a signed receipt can verify, and what it cannot prove for a solo miner.
A mining receipt should answer a narrow question: what work did the pool count from this rig during this hour? It should not ask you to infer the answer from a dashboard number. Mining receipts turn that record into something you can keep, inspect, and check against a published signing key.
That scope matters. A solo miner does not need a receipt to establish ownership of a found block. The block itself pays the Bitcoin address in its coinbase transaction. A receipt instead records the path before that rare event: the shares your rig submitted and the work the pool accepted for its own accounting.
What mining receipts are actually for
A pool cannot observe every hash your miner tries. Your hardware performs hashes locally. It sends a share only when a hash meets the share target in the job it received.
That makes a share a small piece of evidence. It tells the pool that your rig produced a result for assigned work at a stated difficulty. A pool checks that result before it counts it.
A mining receipt is not one receipt per share. At NexusPool (nexuspool.io), one signed receipt covers one rig for one hour. It records the work the pool counted during that period and attaches a signature made with a published key.
The signature changes the useful question from "Do I believe this dashboard?" to "Does this record verify against the key the pool published?" A valid signature tells you that the holder of that key signed those exact receipt contents. If one character changes after signing, the signature check fails.
That does not make a receipt a guarantee of a block, a payment, or a particular amount of future work. It is a signed accounting record. Its value comes from being specific about what it says and equally specific about what it does not say.
Shares are not block finds
Most accepted shares are far below Bitcoin's network target. They prove that a rig met the lower target assigned by the pool. They do not qualify as blocks.
A found block is a share that also meets the network target. That target comes from Bitcoin network difficulty. It is the same regardless of where you point your miner.
Solo mining is a lottery. An expected wait is not a schedule. A period of steady, valid shares can end without a block, and a block can arrive early. Mining receipts do not change that condition. They document the work counted while your rig was participating.
What a signed receipt can verify
A receipt is useful when you check the right properties. Start with its identity, its time window, its stated work, and its signature. The receipt must identify one rig and one hourly period rather than blending a fleet into an untraceable total.
Then check the signature against the published public key. BIP340 signatures use a public key for verification and a private key for signing. The pool can publish the verification key without exposing the signing key.
Any implementation that supports BIP340 verification can perform that cryptographic check. You do not need to trust the screen that displays the receipt. You do need to preserve the exact receipt data being checked. A copied value with a missing character is not the original message.
A valid signature verifies three limited things. It verifies that the receipt data has not changed since signing. It verifies that the expected signing key produced the signature. It verifies that the signer made a statement about the counted work for that rig and hour.
It does not independently prove what your miner hashed but never submitted. No pool has access to those local attempts. It also does not prove that every submitted message was readable, valid, or applicable to the active job. Those are separate checks made at submission time.
This limit is not a flaw hidden by the receipt. It is the boundary of the evidence. A record is better when its boundary is visible.
Why the hour matters
An hourly period gives you a reasonable unit for checking behavior. If a rig disconnects, changes difficulty, or becomes quiet for several minutes, you can compare receipt periods with what the machine reported locally.
A receipt will not make a flaky Wi-Fi connection less flaky. It can make a disagreement easier to isolate. Was the rig submitting shares? Did the pool count work during the period? Did the work stop at the miner, on the route, or at the receiving server?
For a small farm, this is more useful than an unexplained all-day total. One rig can be checked without treating every other worker as part of the same problem.
Receipt verification is separate from payout verification
Work accounting and block payout are different claims. They need different evidence.
A mining receipt says what work a pool counted. It does not show where a future block reward will go. A coinbase transaction in a found block shows where that actual reward went.
Before a block exists, a payout construction can still be checked. Payout Preflight builds the payout for your Bitcoin address on the current block template before your rig finds anything. That lets you inspect the intended destination and amount for the current block, including the subsidy and transaction fees in that template.
The two checks answer different questions. The receipt asks whether work was counted over an hour. Preflight asks what the current block would pay to your address if your rig found it.
Neither check changes your odds. Network difficulty sets those odds. What these checks can do is reduce the number of places where you must accept an untested claim.
The path before the receipt
A meaningful receipt depends on the pool correctly handling the messages that precede it. A rig needs current work. It needs a clear result when it submits a share. It needs its difficulty handled predictably when it is briefly quiet.
For Bitcoin, a rig can connect with its Bitcoin address to solo.nexuspool.io:3350. There is no account or KYC step. The same port accepts Stratum V1 and encrypted Stratum V2.
The endpoint steers a miner toward a nearby healthy Bitcoin region. Distance still matters to the round trip. A miner far from Los Angeles, Chicago, Frankfurt, and Singapore will see new work and statistics arrive later than a miner close to one of them.
Distance does not change the chance that a valid hash meets Bitcoin's network target. It changes communication time, not the network difficulty.
On the receiving side, the pool must distinguish an invalid share from a valid one and give the rig a reason when it rejects a share it read. Otherwise, a receipt can show only the final total while leaving the cause of a missing total opaque.
The work record also needs to survive ordinary operational events. If a rig pauses briefly, immediately changing its difficulty can create misleading behavior when it returns. If a found block is discovered, submitting it must continue after a restart if it remains pending. The receipt is one part of that larger chain, not a substitute for it.
A practical way to use receipts
Treat the receipt as a periodic audit artifact, not as a number to stare at. Save a few consecutive receipts for a single rig. Compare their hourly windows with the miner's own uptime and share log. Verify their signatures against the published key.
If the values differ from what you expected, begin with the scope. Check whether the rig was connected for the entire hour. Check whether it changed jobs or went quiet. Check whether you are comparing accepted work with all attempts, which are not the same measure.
For operators, retain receipts per rig rather than only as fleet-level records. A fleet average can conceal one machine with a network path problem or a configuration error. A one-rig, one-hour record gives you a smaller claim to test.
A signed receipt cannot promise a block. Nothing honest can. It can leave a checkable trail of what the pool says it counted while you wait for one.
Trust nothing. Verify the signature on the receipt for your rig and hour.