Pool Transparency System
On PPLNS, what you earn is your slice of the pool's total. That total has always been the pool's own number.
Our new transparency page publishes it. Every share the pool counted, open to anyone, and a proof on demand that your own work is in there.
The whole record is public
Shares are grouped into slices, which are finalized records of a group of shares. Every slice is published with its reference job, height, share count, total difficulty and fees, and you can browse back through them. Each slice carries a slice root, and that is what makes it tamper evident.
None of it needs a token. Anyone can read the record and add up the total your reward is calculated against.
Verify a random share
Open the Challenge tab, paste your PPLNS token and hit Verify a share. One share is drawn at random from the published record, and the pool proves that the share is in the record and represents real mining work.
The record is published before you ask, and the draw happens against that already fixed record. So we cannot select a favourable example for you, and we cannot alter the record after seeing which share came up. Any share in the record could be the one drawn, which means passing the check requires the whole record to be accurate.
The token is the only private part of this. It exists so that a specific miner can prove a specific share that sits inside a record everyone else can already read.
Every other pool asks you to take the total on faith
Legacy pools run on trust. The pool counts the shares, sets the total and calculates what you are owed, and nothing outside the pool exists to check any of it against. Your dashboard is the pool's own account of its own work. No transparency page fixes that, because the problem is in the design.
This covers every PPLNS miner on DMND. If you declare your own jobs you are on SLICE or PPLNS by definition, so it covers you too.
Also on the page
The page pulls Bitcoin's current chain tip from mempool.space. We do not run, own or fund it, so what you see is measured against a source outside the pool.
You can also watch the jobs going out to miners, with the raw Stratum fields shown on the page: height, nBits, nTime, version, clean jobs, merkle branches, previous block hash, coinbase txid and merge commitment. Each job is graded against basic wire job checks and flagged as passing or as a warning.
Why this matters
Mining has run on trust for its whole history. Miners trusted the pool to count correctly, and were given numbers they had no way of checking. On PPLNS the total is the number that decides your payout, so that is the number we publish.
Don't trust. Verify.
Try it: transparency.dmnd.work