PYBLOCK · TWO CHAINS
The same pool, the same ethos — on Bitcoin SHA-256 and on Bitcoin BLAKE2b.
PyBLOCK mines on two chains. Same operator, same rules: clean blocks, non-custodial payouts in the block's own coinbase, no KYC, no balances. Pick the one your hardware speaks.
this site · pyblock.xyz
Bitcoin · SHA-256
For ASICs. The pool you already know, running since day one.
- LOTTO — solo mining, you keep the whole block ·
:4444 - DATUM-POOLED — TIDES via OCEAN, paid to your address ·
:23334 - CHIRP — shared-reward syndicate ·
:5554 - Template suppliers & Carousel — your node's template ·
:30000
b.pyblock.xyz
Bitcoin · BLAKE2b
For GPUs, CPUs and Sia-class ASICs. A young chain where a small miner still finds blocks.
- Carousel — rotating sovereign templates · you keep 96%
- CHIRP — the syndicate, on BLAKE2b
- WAVICLES — our own DATUM pool: bring your node, keep the window
- Browser miner — mine from a tab, no install
Which one can I mine?
| Your hardware | Chain | Where |
|---|---|---|
| Bitcoin ASIC (S19, S21, Whatsminer, Bitaxe…) | SHA-256 | this site — stratums |
| GPU or CPU | BLAKE2b | b.pyblock.xyz — also a browser miner |
| Sia-class ASIC (BLAKE2b) | BLAKE2b | b.pyblock.xyz |
| A full node, no miners | both | publish templates: here · on BLAKE2b |
Two chains, two wallets. They share history up to the fork, but coins and addresses live on their own chain after it.
A BLAKE2b payout is not spendable on Bitcoin SHA-256, and the other way round. Same PyBLOCK rules on both: we never hold your coins —
every payout is an output in the block's own coinbase.
Why we run both
PyBLOCK is infrastructure, not a bet. Miners should be able to point their hardware at a pool that filters spam, lets them keep their own block, and pays on chain — whichever proof-of-work they run. We build the same thing twice rather than tell anyone which chain to believe in.