Ycg455ndfy1nM8j2y9NsdMbuU5u.home

payout → Ycg455ndfy1nM8j2y9NsdMbuU5u

PPS balance

Payouts flow to your Thunder address on a cadence once the pool's Thunder reserve is funded. Ask the operator if you've been "Owed" a substantial balance for a long time and it isn't dropping.

Audit — why is this number what it is?

Every accepted share credits your worker FLOOR(share_difficulty × 0.029) sats. The rate is pps_sats_per_diff from the pool's config; the difficulty is what the pool held you at when the share landed (vardiff adjusts it based on how fast you're finding hashes). Everything below is derivable from the raw shares table — the stored balance is a running total the pool maintains, but you can always recompute it from scratch.

Independent check. The comparison above weighs two numbers the pool wrote. Separately, every share stores the rate it was credited at, so FLOOR(difficulty × rate_used) must reproduce its credit without reference to any current rate — and every rate used must appear in the pool's published rate log, derived from the block value and difficulty of the template it came from. ✓ All 528,321 of your credited shares re-derive exactly, against 106,273 logged rate(s).

For an even deeper trail (per-share running total, daily breakdown), the operator has an admin-only page at /admin/worker/<id>. Same numbers — just without exposing other miners' data on this public page.

Payouts to your Thunder address

No payouts recorded yet. Once the operator's Thunder reserve has enough BTC and the payout worker fires, each Thunder tx paying you will appear here with its txid so you can verify it in your own Thunder wallet.

Hashrate · 10-min buckets · last 24h

Recent shares (last 200; worker target diff = 6,724.502)