SV1 penalty · from block 977,350
Block 977,350 · about 15 Oct 2026 (147 blocks to go at the current pace)

The penalty we are going to roll out for SV1 endpoints will be so resounding that it will echo across the universe.

Your own nodePublic stratumSupplier endpoint
CHIRP0% pool77% pool—
WAVICLES0% pool77% pool—
CAROUSEL1% pool77% pool + 1% supplier1% pool + 77% supplier
Rentals: from that block, rented hashrate goes only to your own DATUM gateway. Orders already running finish where they are.Run PATUM →

Bring whatever you have.

Most pools have one port and assume an ASIC is behind it. Here every class of hardware has its own port, because BLAKE2b is cheap enough that a CPU is a real participant and not a courtesy. Pick your machine below and the three fields you need are right there. No account, no password to remember: your payout address is your account.
First, how do you want to be paid?
Solo · CAROUSEL

Your shares only pay if one of them is the block — and then 98% of the coinbase is yours (1% to the node-runner whose template you mined, 1% PyBLØCK). Until that happens you earn nothing, for however long it takes. Check the odds for your hashrate first.

Over DATUM your own node is the template, so there is no node-runner cut: 99% of the coinbase is yours · 1% PyBLØCK. Same rule otherwise — it pays only when your share is the block. Check the odds first.

Shared · CHIRP

A syndicate. Every block found by any member is split among all eligible members by standing (7-day tenure + 24h power) — 98% to the syndicate, 1% node-runner, 1% PyBLØCK, inside the coinbase. You are paid whether or not the winning share was yours. See the current split.

Over DATUM (CHIRP-PRIME) your node builds the block and the syndicate keeps 100% · 0% PyBLØCK — same draw by standing (7-day tenure + 24h power), paid in the coinbase whoever finds it. See the current split.

Shared · WAVICLES

A rolling work window (8 × network difficulty). Each block the pool finds is split across the window by work done, so a share earns a little from several blocks rather than everything from one. 0% fee, with your own node or through ours. Live window.

A rolling work window (8 × network difficulty): every block is split across the window by work done. 100% goes to the window · 0% PyBLØCK, with your own gateway or through our node. Live window.

Same chain, same hardware, same ports family — only the payout rule changes. Every payout on PyBLØCK is an output in the block’s own coinbase: nothing is held, nothing to withdraw.
Now pick your hardware
DATUM
With DATUM your node builds the block and you publish it; PyBLØCK only sends back who gets paid what. We never see your transaction selection and could not censor a transaction if we wanted to. This is how we would rather you mined — for sovereignty, not for a discount: the 45-day lock Bitcoin Knots adds from block 973440 applies to every freshly mined coin, whoever built the block.
The easy way: PATUM

One download, one run. PATUM sets up the node and the gateway for you, points them at the Prime you choose and registers your address — Windows, macOS and Linux, open source.

Get PATUM →
Prefer the hard way, or a custom config? Everything below is exactly what PATUM does — step by step, by hand.
What you need: a synced Bitcoin Knots ≥ 29.4 on the BLAKE2b fork with RPC reachable, and a DATUM gateway beside it. Gateways connect to the ports below — miners never do: your ASICs point at your gateway, on your machine. Add blockreservedweight=60000 to bitcoin.conf and restart: this chain caps blocks at 800,000 WU and the Knots default (8,000) leaves no room for a WAVICLES/CHIRP coinbase — our own node rejected block 974536 for exactly that.
One command builds the gateway, points it at the Prime you choose and registers your address:
curl -fsSL https://b.pyblock.xyz:8443/gateway | sh -s -- carousel YOUR_BTC_ADDRESS
curl -fsSL https://b.pyblock.xyz:8443/gateway | sh -s -- chirp YOUR_BTC_ADDRESS
Already run a gateway? Put the Prime in its datum section:
CAROUSEL · b.pyblock.xyz:28916
"mining": { "pool_address": "YOUR_BLAKE2B_ADDRESS", "coinbase_tag_secondary": "your-name" }, "datum": { "pool_host": "b.pyblock.xyz", "pool_port": 28916, "pool_pubkey": "36f94e73ae4c9b9c479c544f035bc9e69565e9d882112031cb27032ecbac818e35a7976501d5cd0453f9fc3e9823127839225e89c45a2cc80902ba0a7e09577b", "pool_pass_workers": true, "pool_pass_full_users": true, "pooled_mining_only": true }, "stratum": { "vardiff_min": 1, "vardiff_target_shares_min": 8 }
CHIRP · b.pyblock.xyz:28917
"mining": { "pool_address": "YOUR_BLAKE2B_ADDRESS", "coinbase_tag_secondary": "your-name" }, "datum": { "pool_host": "b.pyblock.xyz", "pool_port": 28917, "pool_pubkey": "cf995bb5b975ef4b90932f0608c98a033679092e976982621243cd1226803c6417442870dff8372b11363d8f80665b1f298cc23132bf2dab23958a4bcc7d4f72", "pool_pass_workers": true, "pool_pass_full_users": true, "pooled_mining_only": true }, "stratum": { "vardiff_min": 1, "vardiff_target_shares_min": 8 }
WAVICLES · b.pyblock.xyz:28915
"mining": { "pool_address": "YOUR_BLAKE2B_ADDRESS", "coinbase_tag_secondary": "your-name" }, "datum": { "pool_host": "b.pyblock.xyz", "pool_port": 28915, "pool_pubkey": "b5e0b0326b964a92f3046c73a76b9e98173e0c3ea0e0ca771f4e6a3dd92e2935b2caad2a088fdd7bf0a48fc0c41776a9abb13c7d4c6964b53a9ceee4c775e036", "pool_pass_workers": true, "pool_pass_full_users": true, "pooled_mining_only": true }, "stratum": { "vardiff_min": 1, "vardiff_target_shares_min": 8 }
Paid in the coinbase of every block your gateway publishes — CAROUSEL 99% you · 1% PyBLØCK · CHIRP 100% to the syndicate · 0% PyBLØCK · WAVICLES 100% to the work window · 0% PyBLØCK.
Step-by-step guide with a check after every step →
This chain’s proof of work is BLAKE2b — the function Sia used — so Sia-generation hardware mines it unmodified: Antminer A3, Obelisk SC1, Innosilicon S11, iBeLink BM-S3 and the like. No new firmware, nothing to flash. Open the miner’s IP in a browser, go to the pool page and fill the first slot; add a second port as failover.
A SHA-256 ASIC will not mine here. An S19, S21, Whatsminer or Bitaxe connects and then every share is rejected, because it computes the wrong hash. Those belong on pyblock.xyz — and note the ports differ by one (:4444 SHA-256 vs :4445 BLAKE2b), the usual cause of a 100% reject rate.
DATUM · CHIRP via PyBLØCK’s node
Endpointpool.pyblock.xyz:23113
Starting difficulty4,096
Hashes per share1.76 × 1013
First share at 4.3 TH/s≈ 4.1 s
Fee100% to the syndicate · 0% PyBLØCK
Pool URLstratum+tcp://pool.pyblock.xyz:23113
Workerbc1qexample…7k4f.rig-01
Passwordx (anything)
Failover / fallback only. From block 977,350 (~16 Oct 2026), 77% of what you earn through this public endpoint goes to the pool, so it is never used as a preferred endpoint. Mine through your own node instead — one click with PATUM.
DATUM · WAVICLES via PyBLØCK’s node
Endpointb.pyblock.xyz:23114
Starting difficulty4,096
Hashes per share1.76 × 1013
First share at 4.3 TH/s≈ 4.1 s
Fee0% (with your own node or through PyBLØCK’s)
Pool URLstratum+tcp://b.pyblock.xyz:23114
Workerbc1qexample…7k4f.rig-01
Passwordx (anything)
Failover / fallback only. From block 977,350 (~16 Oct 2026), 77% of what you earn through this public endpoint goes to the pool, so it is never used as a preferred endpoint. Mine through your own node instead — one click with PATUM.
stratum · CAROUSEL
Endpointpool.pyblock.xyz:23112
Starting difficulty4,096
Hashes per share1.76 × 1013
First share at 4.3 TH/s≈ 4.1 s
Fee98% you · 1% node-runner · 1% PyBLØCK
Pool URLstratum+tcp://pool.pyblock.xyz:23112
Workerbc1qexample…7k4f.rig-01
Passwordx (anything)
Failover / fallback only. From block 977,350 (~16 Oct 2026), 78% of what you earn through this public endpoint goes to the pool, so it is never used as a preferred endpoint. Mine through your own node instead — one click with PATUM.
CHIRP and WAVICLES run on DATUM: your work goes to a DATUM gateway — here, PyBLØCK’s. Running a Knots node? Run your own gateway (DATUM tab): you build the block and pay less. CAROUSEL is classic stratum.
The ASIC ports start at 4,096 so a big unit does not flood the pool; from there vardiff follows your machine. Your credited hashrate is identical whatever the share difficulty — it only changes how often you report.
A graphics card will not out-earn an ASIC here and nothing on this page pretends otherwise. It earns its proportional share of every block found while its work counts, which is more than most chains offer a GPU in 2026 — and it costs one command line to find out.
pyblockMiner (GPU via OpenCL / Metal, CPU fallback) — clone, build, pick the pool, paste your address:
git clone https://gitlab.com/astrolexis-group1/pyblock-miner.git && cd pyblock-miner && ./build.sh
DATUM · CHIRP via PyBLØCK’s node
Endpointpool.pyblock.xyz:5574
Starting difficulty1
Hashes per share4.29 × 109
First share at 2 GH/s≈ 2.1 s
Fee100% to the syndicate · 0% PyBLØCK
Pool URLstratum+tcp://pool.pyblock.xyz:5574
Workerbc1qexample…7k4f.rig-01
Passwordx (anything)
Failover / fallback only. From block 977,350 (~16 Oct 2026), 77% of what you earn through this public endpoint goes to the pool, so it is never used as a preferred endpoint. Mine through your own node instead — one click with PATUM.
DATUM · WAVICLES via PyBLØCK’s node
Endpointb.pyblock.xyz:23115
Starting difficulty1
Hashes per share4.29 × 109
First share at 2 GH/s≈ 2.1 s
Fee0% (with your own node or through PyBLØCK’s)
Pool URLstratum+tcp://b.pyblock.xyz:23115
Workerbc1qexample…7k4f.rig-01
Passwordx (anything)
Failover / fallback only. From block 977,350 (~16 Oct 2026), 77% of what you earn through this public endpoint goes to the pool, so it is never used as a preferred endpoint. Mine through your own node instead — one click with PATUM.
stratum · CAROUSEL
Endpointpool.pyblock.xyz:4445
Starting difficulty1
Hashes per share4.29 × 109
First share at 2 GH/s≈ 2.1 s
Fee98% you · 1% node-runner · 1% PyBLØCK
Pool URLstratum+tcp://pool.pyblock.xyz:4445
Workerbc1qexample…7k4f.rig-01
Passwordx (anything)
Failover / fallback only. From block 977,350 (~16 Oct 2026), 78% of what you earn through this public endpoint goes to the pool, so it is never used as a preferred endpoint. Mine through your own node instead — one click with PATUM.
CHIRP and WAVICLES run on DATUM: your work goes to a DATUM gateway — here, PyBLØCK’s. Running a Knots node? Run your own gateway (DATUM tab): you build the block and pay less. CAROUSEL is classic stratum.
Any BLAKE2b miner that speaks Stratum V1 works: the protocol here is the ordinary one with the BLAKE2b header underneath. Work out your own wait rather than trusting a table: seconds per share = difficulty × 232 ÷ your hashrate. At difficulty 1 a card doing 2 GH/s lands a share every ~2 s; on the vardiff port (4096) the same card takes ~2.5 h per share but is credited exactly the same.
Difficulty 1 is where this port starts and where it stays: it is the floor of the chain itself, there is nothing easier to hand out. A CPU here does the same work as everything else on the pool, only less of it.
pyblockMiner (GPU via OpenCL / Metal, CPU fallback) — clone, build, pick the pool, paste your address:
git clone https://gitlab.com/astrolexis-group1/pyblock-miner.git && cd pyblock-miner && ./build.sh
DATUM · CHIRP via PyBLØCK’s node
Endpointpool.pyblock.xyz:5574
Starting difficulty1
Hashes per share4.29 × 109
First share at 50 MH/s≈ 85899345.9 s
Fee100% to the syndicate · 0% PyBLØCK
Pool URLstratum+tcp://pool.pyblock.xyz:5574
Workerbc1qexample…7k4f.rig-01
Passwordx (anything)
Failover / fallback only. From block 977,350 (~16 Oct 2026), 77% of what you earn through this public endpoint goes to the pool, so it is never used as a preferred endpoint. Mine through your own node instead — one click with PATUM.
DATUM · WAVICLES via PyBLØCK’s node
Endpointb.pyblock.xyz:23115
Starting difficulty1
Hashes per share4.29 × 109
First share at 50 MH/s≈ 85899345.9 s
Fee0% (with your own node or through PyBLØCK’s)
Pool URLstratum+tcp://b.pyblock.xyz:23115
Workerbc1qexample…7k4f.rig-01
Passwordx (anything)
Failover / fallback only. From block 977,350 (~16 Oct 2026), 77% of what you earn through this public endpoint goes to the pool, so it is never used as a preferred endpoint. Mine through your own node instead — one click with PATUM.
stratum · CAROUSEL
Endpointpool.pyblock.xyz:4445
Starting difficulty1
Hashes per share4.29 × 109
First share at 50 MH/s≈ 85899345.9 s
Fee98% you · 1% node-runner · 1% PyBLØCK
Pool URLstratum+tcp://pool.pyblock.xyz:4445
Workerbc1qexample…7k4f.rig-01
Passwordx (anything)
Failover / fallback only. From block 977,350 (~16 Oct 2026), 78% of what you earn through this public endpoint goes to the pool, so it is never used as a preferred endpoint. Mine through your own node instead — one click with PATUM.
CHIRP and WAVICLES run on DATUM: your work goes to a DATUM gateway — here, PyBLØCK’s. Running a Knots node? Run your own gateway (DATUM tab): you build the block and pay less. CAROUSEL is classic stratum.
This is also the port for a dry run before you repoint real hardware: if a CPU gets an accepted share, your address and worker string are right.
No install at all: the browser miner runs the same BLAKE2b core (WASM) on your CPU and talks to CAROUSEL, CHIRP or WAVICLES through our bridge. Lottery-scale hashrate — a real ticket, and the quickest way to see your address appear on the pool.
Open the browser miner →
Not a kind of hardware: Stratum V2 is a newer wire protocol — Noise-encrypted, binary, with the pool’s authority key pinned in the URL so your miner knows it is talking to us. Same chain, same payouts, same machines: :5594 / :23133 pay like CHIRP, :30130 like CAROUSEL.
You almost certainly do not need this. Sia ASICs do not speak V2, and the only SV2-BLAKE2b client today is the bridge’s test client — pyblockMiner’s SV2 mode ships next release. A stock V2 miner will not find a share here: it hashes SHA-256 over a Bitcoin header, this chain hashes BLAKE2b and needs 64-bit nonce and time fields. Both differences are written down with test vectors in the protocol document.
Pool URLstratum2+tcp://pool.pyblock.xyz:5594/9bHUc9mm6rV6mcg1QUWfgSToWtLrW9ydbXRvBfDGX1kCVeYhLfR
CHIRP ASICstratum2+tcp://pool.pyblock.xyz:23133/…
CAROUSELstratum2+tcp://pool.pyblock.xyz:30130/…
Authority key9bHUc9mm6rV6mcg1QUWfgSToWtLrW9ydbXRvBfDGX1kCVeYhLfR
Workerbc1qexample…7k4f.rig-01
How you know it worked
Within a few minutes of the first accepted share your address shows up on the pool: hashrate, workers, and on which port. Type it here (nothing is stored) — the same address you use as username.
Something off? The FAQ covers reject rates, missing hashrate and address formats.