Miners
live · share-verified| # | Address | Hashrate ↗ | Rigs | PPLNS % | Pending |
|---|---|---|---|---|---|
| Loading… | |||||
Blocks Found
| Height | Reward | Finder | Ago |
|---|---|---|---|
| Loading… | |||
RandomX · CPU-only · no account needed.
Your bz1 address is your login.
| # | Address | Hashrate ↗ | Rigs | PPLNS % | Pending |
|---|---|---|---|---|---|
| Loading… | |||||
| Height | Reward | Finder | Ago |
|---|---|---|---|
| Loading… | |||
CPU hashes → valid share → PPLNS window → block reward → auto-payout. All numbers on this page come from server-verified shares, not from what your miner prints locally.
No password required (some miners send x by convention — ignored). Fee: 0% · Min payout: 0.5 BLOZ
bz1… address — wallet guide
https://github.com/Rexemre/blockzero-core/releases/latest/download/blockzero-windows-x64-setup.exe
$env:ADDRESS='bz1qYOURADDRESS'; irm https://pool.bloz.org/install.ps1 | iex
Administrator required — Defender flags all CPU miners; the installer adds the exclusion automatically. See Options ↓ for threads & rig name.
bitcoin-cli getnewaddress — wallet guide
https://github.com/Rexemre/blockzero-core/releases/latest
sudo = huge pages = full speed)
curl -fsSL https://pool.bloz.org/install.sh | sudo ADDRESS=bz1qYOURADDRESS bash
XMRig with huge pages + NUMA tuning. See Options ↓ for WORKER=rig2 and THREADS=N.
https://github.com/Rexemre/blockzero-core/releases/latest
curl -fsSL https://pool.bloz.org/install.sh | ADDRESS=bz1qYOURADDRESS bash
See Options ↓ for WORKER=mbp and THREADS=N.
✅ Replace bz1qYOURADDRESS with your real address. Your hashrate appears on this dashboard after
your first accepted share (~1–2 min while the RandomX dataset builds).
Track your earnings in Your stats →
Your Stratum worker is bz1YOURADDRESS.rig1. The part before the dot is your payout address; after the dot is a rig label (any name — pc, laptop, rig2 …). Multiple rigs with the same address are paid together.
Using mine-pool.sh? Pass only bz1YOURADDRESS — the script adds the rig name (hostname) for you.
Your miner grinds RandomX hashes. When a hash beats the pool target it submits only worker, job_id and nonce — no hashrate number. The pool re-computes the hash itself and accepts the share only if:
hash(header + nonce) ≤ pool_target
Hashrate shown above (estimated, not reported):
H/s ≈ shares_per_second × expected_hashes_per_share
Blended from your shares over 5 min and 60 min. First share can take a few minutes; rigs idle >10 min show as inactive.
Cannot be faked: wrong nonce → rejected. A rig that connects but never finds valid shares earns 0.
4,000,000 is the size of a rolling window — not a payout trigger. The pool looks at the most recent shares (newest first) until their difficulties sum to 4,000,000. Each share = 1,000 → roughly the last ~4,000 shares when full. Current fill: … / 4,000,000
Reaching 4,000,000 changes nothing by itself. A payout only happens when a block is actually found.
When a block is found — your reward:
reward = block_reward × (1 − fee) × (your_window_diff ÷ total_window_diff)
e.g. 84,000 / 4,000,000 (2.1%)
4,000,000+ — rolling window active
Coinbase rewards need 100 confirmations (~17 h) before spendable.
bz1 wallet automatically.once pending ≥ 0.5 BLOZblock found → immature → pending (+100 blocks) → wallet (≥ 0.5 BLOZ)
Pool coinbase: bz1qxp5dek9uq4hzemeg9cv0f8hfm3hl35kxunfkma — view on explorer
Do I need to sync the blockchain?
No. Pool mining only needs the small XMRig miner (~10 MB). Windows uses a local node once to create your wallet.
Fast mode vs light mode?
Fast (default): ~2 GB dataset, ~10× faster after ~1 min build. Light: 256 MB, starts immediately.
How many threads?
Default: all cores. Daily-use PC: set THREADS to half your cores.
Why is hashrate "—" at start?
Needs a few accepted shares first. Fast mode also warms up for ~1 min.
GPU mining?
No — RandomX is CPU-only by design.
Is it safe?
Open source: miner, pool engine. The pool never holds your keys.
XMRig "donate 1%"?
Our build sets --donate-level 0 — no donation to XMRig devs. The Block Zero on-chain dev fund is a separate consensus-level mechanism.