You don’t need to understand cryptography to understand the problem it solves here, so start with the problem.
When you point a miner at a pool, your hardware sends a stream of solved puzzles, called shares, to prove it’s doing real work. The pool is supposed to count those shares and use them to calculate things like your share of a payout, or in a solo pool’s case, whether one of them happened to solve an actual block. The trouble is you have no way to check any of that from your side. The dashboard says whatever the dashboard says. If it undercounts your work, or overcounts someone else’s, you would likely never know.
What a signature actually does
A digital signature is a way to prove two things at once: that a specific piece of data came from a specific party, and that the data hasn’t been changed since it was signed. It works using a pair of keys, one private and one public. The private key signs something, and the public key lets anyone verify that signature without ever seeing the private key itself. This is the same basic idea behind how a Bitcoin transaction proves you own the coins you’re spending, just applied to a different kind of message.
Apply that to mining: instead of just showing you a number on a webpage, a pool can issue you a signed record stating what it counted from your account. You don’t have to trust the number on the page. You can take the signed record and check the signature yourself, using a small, independent program and the pool’s published public key. If the signature is valid, you know the record is authentic and hasn’t been tampered with since it was issued. If someone tried to alter even one character of it, the signature check would fail.
What makes this different from just trusting a screenshot
A screenshot can say anything. A signed record can’t be faked without the private key, and it can’t be silently edited after the fact without breaking the signature. The difference is the difference between someone telling you a number and someone handing you a notarized document with a wax seal that visibly cracks if anyone opens it. You’re not trusting the person anymore. You’re checking the seal.
You can also run the check offline, with no connection to the pool at all, which matters more than it sounds like it should. If checking a receipt required going back to the pool’s own server, you’d just be trusting the server again, one layer removed. A check that works with your network cable unplugged is a check that doesn’t depend on the party being checked.
What it doesn’t prove
Here’s the honest limit, and it’s worth stating plainly rather than letting a reader assume more than is true. A signed receipt proves that whatever was issued to you is authentic and unaltered. It cannot prove that something was never issued in the first place. If a pool simply chose not to issue you a receipt for some work, there’s no receipt for you to check, and no way to detect that gap from the receipt system alone. Verification proves the integrity of what you have. It doesn’t prove completeness of what you should have gotten. Anyone telling you otherwise is overselling the tool.
NexusPool issues signed receipts of this kind for account-level work summaries, checkable offline against a published key. The format of those receipts, along with the published key used to check them, is laid out on NexusPool’s technology page. It doesn’t change your odds of finding a block, because nothing can. Solo mining is a lottery, the odds are set by the network’s difficulty alone, and an average wait is not a schedule. This is free, non-custodial software, not an investment, and no reward is ever guaranteed.
Trust nothing. Verify the receipt, not the dashboard.
About NexusPool: NexusPool issues signed, offline-checkable receipts so miners can confirm their submitted work was recorded rather than taking a dashboard number on faith. A plain description of how NexusPool’s technology works is available for anyone who wants to read past the summary.