hashpitround #–
Your device solves SHA-256 puzzles in this tab. When a round closes, the pot is split by verified work.
waiting for a proof0% of the 0.01 SOL payout threshold
hashpitleaderboard
Who is mining, and how each round's pot is shared.
Share is your verified work in the period divided by all verified work. A proof at difficulty d counts as 2d hashes.
hashpitstats
How the pool is doing: hashrate, miners, pots and payouts over time.
hashpitrounds
Every settled round. Open one to see exactly how its pot was split and paid.
hashpitbenchmark
Measure this device: 5 seconds on every CPU thread, then 5 seconds on the GPU. Nothing is mined or sent while it runs.
Self-reported by the browser that ran the test. Shown for comparison only; it never affects credit.
hashpitledger
Every payout, with its transaction. Balances are paid at round close once they cross the threshold.
hashpithow it works
From a random seed to SOL in your wallet.
Your tab asks the server for a challenge bound to your address: a random 32-byte seed and a difficulty in bits. Tickets last two minutes.
Web Workers on your CPU and a WebGPU compute shader on your GPU hash SHA-256(seed ‖ nonce), looking for a digest that starts with difficulty zero bits.
A hit is sent as its nonce. The server checks it with a single hash. Weak, reused, expired or borrowed proofs are rejected.
A proof at difficulty d is credited 2d hashes, the number of tries it takes on average.
Each address gets its own difficulty, tuned for about one proof every few seconds, so a phone and a GPU rig are measured the same way.
At round close the pot is split by share of verified work. Balances over the threshold are paid out and logged in the ledger.