The pool is told an account that is not yours.
You are paid in shielded ZEC.
Neither step leaves a public record of what you earned.
asking the pool…
A mining payout address is on-chain forever. Anyone who finds it reads the whole history off it: how much you make, since when, roughly how large the rig is.
No pool chose this. A pool has to pay you somewhere and the only somewhere it knows is transparent.
A stratum proxy. Your miner connects to it, it connects onward under an account of its own.
your miner sends mining.authorize ["you.rig1", "x"] the pool receives mining.authorize ["pool-account", "x"] $ grep -c 'you' everything-the-pool-received.txt 0
Who earned what is settled here, from what the upstream pool accepted. Never from what a worker claims. Once a month that becomes one shielded payment.
Every round publishes its transaction, the number of accounts paid, and a commitment to the amounts. Anyone confirms the transaction is real. You confirm your own amount is inside the commitment. Nobody sees anyone else's.
The receipt prints what it does not establish. Shielded transactions hide amounts, so the total is not confirmed by the chain, and your own inclusion is not proof that nobody was left out.
proxy against real pools working identity, accounting working payout rounds, receipts built, tested money actually moved not yet
Read that as what it is: not a measurement, but the operator's own account of the code. The block above it is the pool answering for itself; this one is us saying so. The last line is the only one that matters yet, and it stays red until a payment has moved and can be checked on the receipts page. There is no receipt to show until there is, and there will not be an invented one.
Shielded ZEC is awkward to sell — most exchanges take transparent addresses only — so this is worth a lot if you accumulate and little if you sell every month. Mining is also not always worth doing: the calculator puts power cost beside revenue and will say so.