Block Zero (BLOZ): the token, in plain words
What is BLOZ?
Why miners and holders like it
Latest Block Zero news
Block Zero pool launched
Stratum opened on port 33340 today after the node came out of sync with the dev-fund output active and two clean end-to-end runs: the project's own blockzero-miner.py and XMRig with -a rx/blockzero both pushed accepted shares. The pool takes 1% and pays every hour once a balance clears 0.1 BLOZ, with a block's coins spendable after 100 confirmations — around seventeen hours behind the block itself.
source →How-to-mine pages, English and Russian
Both guide pages went live with the pool: ready-made XMRig command lines for Windows and Linux, where to get the patched xmrig-bz build, a systemd unit for Linux rigs, the HiveOS route, and the payout fine print — fee, maturity and the dev-fund rule — set next to a comparison against the official pool and rplant.
source →rc38 finishes the Block Zero rebrand
The October tag completes what rc37 started: RPC help text, CLI output, error messages and the Windows installer now say Block Zero and BLOZ instead of Bitcoin and BTC, the bloz: URI handler included, and the smallest unit picked up the name rex. Checksummed builds for Windows, macOS and Linux ride along; the author notes the C++ suite carries the same fourteen pre-existing failures as before the rename.
source →The official mining handbook
The project's own walkthrough runs from a fresh wallet to a running miner: one-line installers for Windows, macOS and Linux that fetch the patched XMRig, thread and rig-name tuning, a pool-versus-solo table, and a solo route that refuses to start until the node has peers — mining on zero peers builds a fork.
source →Dev fund, in the project's own words
How the on-chain Development & Growth Fund actually behaves: from block 1500 every coinbase must route at least 10% of its subsidy to a published address, getblocktemplate hands miners the output ready-made, a block that skips the payment is rejected outright, and transaction fees stay entirely with the miner.
source →Wallet, GUI first and CLI for servers
Create a descriptor wallet, pull a fresh bz1… address off the Receive tab, keep the backup somewhere sane — and switch on chain pruning if the machine's only job is mining. Keys never leave the wallet; the pool just pays whichever address the worker name carries.
source →Run a node yourself
The node guide covers both routes: the release tarball with its sha256 files checked first, or a cmake build straight from source. Ports 8210 and 8211, roughly a gigabyte of memory for RandomX validation, and the single public seed — worth knowing it is a single host before your first sync.
source →Where the miners come from
The ops repository holds patch.py, which lays rx/blockzero over stock XMRig v6.26.0 — nonce moved to offset 76, donations pinned to zero — plus the native Python miner that doubles as the pool's test client. The only difference from Monero's rx/0 job is that nonce offset.
source →Prebuilt patched binaries
Releases of the patched miner land on the ops page — grab the latest xmrig-v6.26.0-bz4 build, unpack it, and point it at pool.ion.cool:33340 with your bz1 address. HiveOS images ship from the same project.
source →Watch the chain, check the payments
The chain's own explorer tracks blocks and addresses — and every payout the pool sends shows up there as an ordinary on-chain transaction to your bz1 address, transaction id included.
source →The thread that started it all
The Bitcointalk announcement lays out the consensus rules, the dev-fund flag day at block 1500, and the pool field as the project counts it: the official pool at 0% fee with a 0.5 BLOZ minimum, and rplant running the same RandomX job at 1% on PROP.
source →Project homepage
Chain parameters at a glance — ten-minute blocks, a difficulty retarget every 72 of them, the 21 million cap — plus pointers to the wallet, the explorer and the documentation.
source →