SUPPLIERS

publish your block template · earn 1% on the Carousel
LIVE
CAROUSEL · the lap block 977,204 · 1,639 templates in the lap · agenda 1e415309

Nobody picks this order. It comes out of a public rule — turn = agenda[(start + cycle) mod n], with start = (height × 11) mod n — and the agenda is frozen once per block, which is what makes the next seven turns announceable at all. You can recompute it yourself: the agenda for this block is the 1e415309 above, and the tool is published in the repo.

Not being in these eight does not mean you are out or that you lost anything. You are in the lap — all 1,639 of them — and your turn comes. This is the window of what is next, not the list of who gets paid.

—
Template hashrate
—
Miners
—
Suppliers
—
Endpoints
3,642
In rotation
3,642 suppliers in the rotation · 1 stratums warm right now · join in. A stratum is kept warm for each turn as it comes up, so publishing costs you nothing while you wait. The fleet runs behind PULSAR, so the node never becomes the bottleneck.
📊 Top BLAKE2b suppliers

💰 Richest templates · fees

Loading…

▸ Most templates accepted

Loading…

🏆 Blocks won · templates that won

Loading…
Active BLAKE2b template suppliers
Nodes publishing block templates to the Carousel right now. Last picked = last time the Carousel mined your template · turns in 24h · Blocks = blocks found on your template · Fees = BTC in its best template · ℹ = details, declarations, dedicated stratum. Status = building on the current tip.
🔍
/ to search
SupplierStatusLast pickedBlocksFees
Loading…
Become a template supplier
Run a node? You can also mine your own template with WAVICLES — the PyBLØCK DATUM pool: your gateway builds the block, the pool only sets the split — 100% of every block to the work window, by share of work, paid in that block's coinbase · 0% fee.

Run a node and publish its block template to PyBLØCK. Miners on the Carousel build on your template; if one finds the block, you earn 1% of the reward on-chain — automatically, to your address. Your node, your transaction selection, your say in what blocks look like.

Publish · one command
curl -fsSL https://b.pyblock.xyz:8443/join | sh -s -- YOUR_BTC_ADDRESS "Your Name"
🔐 Verify your address so nobody else can publish templates under it: sign one message with your wallet and get a private token. Verify your supplier address →
Your BTC address is where your 1% is paid. Miners find your template on the Carousel:
stratum+tcp://pool.pyblock.xyz:23112
ASIC :23112 · GPU :4445
Two ways to supply · both live today

You earn the same either way — 1% on CAROUSEL, written into the block's own coinbase. What changes is who publishes the block, and that decides when you get paid.

You publish the template what you do today
  • You publish it; PyBLØCK builds the block and submits it.
  • The rotation picks your template and our hashrate looks for the block.
  • You get paid without having a single miner of your own.
curl -fsSL https://b.pyblock.xyz:8443/join | sh -s -- YOUR_BTC_ADDRESS "Your Name"
Miners reach your template on the Carousel: :23112 (ASIC) · :4445 (GPU).
You run the gateway DATUM · new
  • Your gateway builds the block and submits it. PyBLØCK only dictates the coinbase.
  • Your miners point at your machine, not at ours.
  • You get paid when a block is found on your gateway — so this one needs hashrate of your own.
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
One registration covers both products. Use sudo sh -s -- instead of sh -s -- to install it as a service. Read the script before running it — it is commented for that.
Your miners connect to your own machine; the gateway talks to b.pyblock.xyz:28916 (CAROUSEL) · :28917 (CHIRP).

Which one is for you. If you have miners of your own, the gateway is strictly better: your rigs mine your own template and you collect both things in the same coinbase — your 1% for the node plus whatever your miners earn under the product's rule. If you only publish a template and have no hashrate, the gateway means you would stop being paid, because no block gets found on your machine. In that case stay where you are: publishing still works and nothing is being switched off.

Why set it up anyway. This is where the chain is heading — WAVICLES already works this way, and the client now expects a miner to run their own node and gateway. Nobody is forced today and both paths run side by side, but having your gateway up is what keeps you from being left behind if that expectation ever turns into a rule.

Two limits, said up front. Changing your payout address after registering is manual — ownership is proved by the IP the gateway connects from, and that cannot tell apart two neighbours behind the same NAT. If you mistyped it or you get a 403, write to us. And a CHIRP block currently pays the 16 heaviest members, not all of them: an external gateway serves a small coinbase, so the rest stay in the membership and are paid in the next one.

How it works
  1. Run a full node with the block policy you choose; publish its template with your payout address.
  2. Carousel miners mine your template. Find a block → you earn 1% in the coinbase.
  3. Non-custodial. Paid on-chain, automatically. Split: 98% you · 1% node-runner · 1% fee.
LIVE on BLAKE2b mainnet · Carousel :23112 · :4445 · non-custodial on-chain split.
Requirements & details
What do I need?
A BLAKE2b-capable node — Bitcoin Knots ≥ 29.4 (rc4) following the BLAKE2b fork, with RPC reachable. A standard SHA-256 node cannot supply — it rejects the blake2b template rule. On your side you only need bitcoin-cli + curl — nothing to install.
Clean templates are mandatory
Set datacarrier=0 in bitcoin.conf and restart. If your node accepts OP_RETURN, every template is rejected — PyBLØCK only relays spam-free, sovereign blocks. Your node, your transaction selection, your say in what blocks look like.
How does publishing work?
The one-liner starts a small background loop that pushes your node's getblocktemplate to the pool: instantly on every new block (freshness) plus every ~20 s for mempool updates. Re-run it any time — it replaces the previous loop. Keep the node running to stay in the rotation.
How am I identified?
Your supplier name, in order of priority: the name you choose → your node's UA (uacomment) → your address. It labels you on this list and on the Carousel.
Privacy · publish over Tor
Run with PYBLOCK_NET=tor and your IP is never sent (published over the onion):
curl -fsSL https://b.pyblock.xyz:8443/join | PYBLOCK_NET=tor sh -s -- bc1q… "Name"
Verify your address (recommended)
Anyone could publish templates using your address. Verify it: sign a short message with the wallet that holds the address (Sparrow, Electrum, Knots signmessage or a hardware wallet — 1…, 3… or bc1q…) and you get a private token. Re-run the one-liner with it and, from then on, only publications carrying your token are accepted for your address:
curl -fsSL https://b.pyblock.xyz:8443/join | PYBLOCK_TOKEN=<token> sh -s -- bc1q… "Name"
How do I get paid?
When a Carousel miner mines your template and finds the block, your 1% is written into the coinbase — on-chain, straight to your address, automatically. Non-custodial: PyBLØCK never holds your funds. Full split: 98% you · 1% node-runner · 1% fee.
📄 Read the Template Suppliers whitepaper →

—

—
Template height
—
Transactions
—
Fees in block
—
Block reward
—
—
On-chain split if this template wins:
— miner · — supplier · — PyBLØCK (98 / 1 / 1)
Mine this template · SV1 · BLAKE2b
stratum+tcp://pool.pyblock.xyz:23112
The Carousel rotates BLAKE2b miners across every active supplier template. ASIC :23112 · GPU :4445 · Username: YOUR_BTC_ADDRESS · Password: x