Skip to content

The pool is the only witness to what your rig did.

That is true at every mining pool, including this one. It is the thing the Glass Ledger exists to end.

Your rig guesses numbers against a target. The Bitcoin pool hands them out, collects the results, and decides what counted.

A short count and bad luck look identical from where you are standing.

Most pools are honest. You could not tell either way.

You hold no second copy of anything.

One character in. Sixty-three out.

A receipt is the second copy. It is a short line of text with one signature taken over it, and the signature covers a digest. The digest is the part that moves.

Change a digit of the count below. Watch how much of the digest goes with it.

seq
4831
type
custody.hash
window
3600s
counted
One bar per hex character. A bar rises if that character moved on the last edit.
0 / 64 moved
································································
matches the sealed digest

Computed in your browser, over the same bytes the pool signed. This page hashes. It does not check a signature. That runs against the published key, off this machine.

There is no version of a changed receipt that the seal still accepts, and no way to work backwards from a digest to a number that would fit.

The digest stops a number from being changed quietly. The signature stops the changed number from being re-issued. Anyone can recompute a digest, and only the key holder can sign one.

A receipt cannot make you win. It stops a short count from hiding behind bad luck.

What this does not do

Nothing here improves your odds. Difficulty is set by the network and is the same everywhere. Solo mining is a lottery. Expected time is an average, not a date. Lower difficulty means a shorter wait, not more value.

One key, published once

Copy it the first time you look. Every receipt after that either verifies against it or it does not, and our word stops being part of the answer.

BIP340 Schnorr over sequence, type and payload. Procedure at docs/audit.

Authority pubkey · hex · NexusPool ref-miner
124797e8bc0ec89ed60b77c30e1770c624407f72659dc97aa4c4fd7d9377106c
Authority pubkey · base58check · standard SV2 clients
9amd6GUzTaGXASESCa75c9Rx3vWYihRyLUAE3Vrmqwgm3T9jtxN

The pool signs each receipt once, with a key it publishes. After that a receipt either matches or it does not.

Read the ledger, not our summary of it.

Below are the receipts this pool has actually signed. Nothing was typed in to fill it.

tip height
fresh work out, p50
fresh work out, p95
receipts held here
0
seqrecordserved
This node holds no signed receipts yet, so the bench is loaded with the reference payload used elsewhere on this site. It carries no signature, and nothing here pretends it does.
Receipt 4831 · custody.hashreference payload
Reference payload · 31 bytes · tap any digit
|custody.hash|s|
SHA-256 of the payload as it now reads · at rest
································································
Signature
none — this node has signed no receipts yet
payload is at rest

Hashed in your browser. This page does not check the signature. That is the one step you should not let us do for you. The key is published below, and the offline verifier is not released yet.

Nothing is stored on our side by looking. The address is the lookup key, and it is the same one your rigs already send us.

Three things get a receipt

Each covers something specific, and each says plainly what it does not cover. Receipts are written per rig, per window of time. They are not written per share, and we will not describe them that way.

custody.hash

Counted

For each of your rigs, each window, we sign what we counted from it. If that rig reports its own hashrate, the receipt carries the gap between the two figures, and only when the gap is wider than ordinary statistical jitter.

We are not going to call noise a loss.

custody.time

Useful

Work goes stale the moment somebody else finds a block. Each time we notice a new tip quickly, we sign how fast fresh work went out to you.

The occasional tip we catch only by polling gets no receipt. It would not be honest to sign for a speed we did not achieve.

custody.block

Conserved

The moment a block is won here, a receipt records it going out to every node we reach, and names the coinbase transaction that pays you. Look that transaction up on any block explorer and you see the address for yourself, so the receipt shows where the money went and not only that a block was found. It gets amended once the chain settles its fate.

There is nothing to show you under this heading yet. This chain has not won one.

What is not finished

The offline verifier is not released yet, so the check still runs through this site. The public repository holds the licence and the readme, not the source.

We don’t change your luck. We prove we didn’t lose your work.

Glass Ledger: a signed receipt for the work we counted · NexusPool