Mining in your browser

Start a mining session

1. 01

   Create or import your wallet, unlock it and verify your address.

2. 02

   Open Miner. Supported GPU/browser, login and collection availability are separate readiness requirements.

3. 03

   Test GPU runs a local computation check. It creates no reservation or paid transaction.

4. 04

   When live mining is open, choose Start mining. Temporary access is created and the worker checks current jobs.

5. 05

   Keep Miner open. Mining can continue in another tab or app while the browser allows it. Stop mining ends local hashing; an accepted proof opens its claim dialog here.

Browser mining requires WebGPU, GPU acceleration and a secure website connection. Hardware information comes from your browser, which may expose limited details. A detected CPU is device information, not a claim that this GPU miner is mining on the CPU.

Read the dashboard

• Hashrate is the rate measured by this device’s running worker, not promised earnings.
• Total hashes counts attempts in the current session. Session duration cannot predict a winning hash.
• Difficulty shows expected hashes per proof. For example, 7.58 billion is rounded; the full attempt count is also shown.
• Network hashrate estimates work from verified proofs and observation time. It stays unavailable without enough samples.
• Active wallets and workers reflect recent valid job contact. Addresses are not unique people.

Why difficulty changes

All workers follow a shared target. A hash is valid only when its numeric value is at or below it. Difficulty combines three factors: the epoch minimum, a hashpower adjustment derived from accepted proofs, and a participation adjustment based on work-verified active wallets.

Participation is checked every 60 seconds. A wallet qualifies when an unexpired, unrevoked worker has both recent job contact and an accepted activity share within 90 seconds. Multiple devices on one wallet count once. Activity shares are small, independently verified pieces of work; they never reserve a token, create ownership or authorize a payment. Updated browser and external workers send them automatically.

The participation multiplier is the square root of qualifying wallets, rounded down to 0.001, with a minimum of 1× and maximum of 16×. Four wallets mean 2×; 25 mean 5×; 100 mean 10×. It raises both the difficulty floor and the network target interval. In epoch one, 100 qualifying wallets raise the network target from 120 seconds to 1,200 seconds. Actual arrivals remain random.

The separate hashpower retarget is considered after sixteen accepted mint proofs or sixteen current target intervals. Each hashpower adjustment is bounded to a factor of four. Each proof contributes the work of its exact assigned target; participation changes do not erase partial observations. A new target revision invalidates old jobs; workers request fresh work automatically.

Later epochs raise minimum work too. Participation falls again when recent activity expires, without making work easier than the epoch minimum. Addresses are not unique people: one person can operate several wallets, and activity work does not prove identity. This policy slows distribution; GPU speed still determines how many attempts a miner contributes. Expected attempts are an average, not a countdown.

Your GPU and parallel work

Your Device reads the WebGPU adapter selected by the browser. A successful GPU self-test confirms that this worker computed the expected hashes. Some browsers hide model names; the separately labelled WebGL renderer can reveal a model, but may belong to another adapter.

Parallel hashes changes the maximum hash attempts in one GPU batch. You can change it while mining. Lower limits make smaller bursts of work, while larger batches can improve throughput. The miner adapts below your limit for responsiveness. Workgroups use 64 shader invocations; browser-reported CPU logical processors are separate and are not a selectable number of CPU mining threads.

Stopping and locking

Switching tabs or using another app no longer deliberately stops the worker. Closing Miner, navigating to another page, signing out or removing the wallet stops it. Auto-lock and natural login expiry do not by themselves cancel an authorized worker. Separate mining access still expires at the time shown in the panel.

Mining uses your hardware and electricity and can increase temperature and power use. Start deliberately and stop when needed. A browser that suspends background computation cannot be treated as a continuously running worker.

External workers

The optional external worker follows the same jobs, targets and reservation rules. Create temporary worker access from your verified account on Miner. Its credential authorizes mining for your address; it cannot sign QTC payments.

The default external worker stops after an accepted proof and reports the reservation. Return to Miner to review and pay within five minutes. Every separate reservation has its own deadline. External mining does not enable automatic minting or payment.

Several devices can mine to the same wallet. Use a separate worker credential for each process so their nonce ranges are distinct. Browser mining uses one GPU selected by the browser. External rigs can select a GPU index for each process, including identical models. Device hashrates add to the wallet’s attempts; this does not guarantee a result.