bePYBLØCKᛒ
BLAKE2b · Whitepaper

Template Suppliers

Publish your own node's block template to the pool in one command — and earn 1% on-chain when a miner finds your block.

Node Knots ≥ 29.4 rc4Rule blake2bReward 1% coinbaseCustody none
Abstract

A Template Supplier is anyone who runs a BLAKE2b full node and lets the Carousel serve their block template to miners. You decide what the block contains; miners on the rotation build on it; if one finds the block, your 3% is paid straight into the coinbase, to your address, with no custody in between. Supplying takes a single command, needs only bitcoin-cli and curl, and turns your sovereign transaction selection into a share of real block rewards.

1 Why supply templates

Every block is a statement about which transactions matter. In a normal pool, one operator makes that statement for everyone. Supplying inverts it: your node, your policy, your block. You are not renting hashrate — you are contributing a clean, valid template that miners can choose to build on, and being paid when they succeed.

The more independent suppliers there are, the more plural block construction on the chain becomes. Each supplier is one more party the network does not have to trust a pool operator to be.

2 Requirements

3 Publish in one command

One line registers you and starts publishing:

curl -fsSL https://b.pyblock.xyz:8443/join | sh -s -- YOUR_BTC_ADDRESS "Your Name"

The script auto-detects your node (it tries bitcoin-cli RPC ports 8342 → 9332 → 8332, then the default) and confirms it can produce a BLAKE2b template with getblocktemplate '{"rules":["segwit","blake2b"]}'. On success it prints your supplier card and begins the publish loop. Your name is optional — see §5 for how identity is resolved.

Miners then reach your template through the Carousel:

stratum+tcp://pool.pyblock.xyz:30110

4 The clean-template policy

PyBLØCK relays only spam-free, sovereign blocks. Before it starts, the join script inspects your own getblocktemplate and checks whether any transaction carries an OP_RETURN output. If your node accepts data carriers, every template you publish is rejected.

Set datacarrier=0. Add it to bitcoin.conf and restart before joining. This is not cosmetic — it is the property that makes a Carousel block worth mining: no arbitrary data, no pay-to-include, just the transactions a sovereign node chose on merit.

5 How publishing works

The command installs a small background loop that pushes your node's current template to the pool over HTTP. It is block-driven:

  1. On every new block — it republishes immediately, so your template is always built on the current tip.
  2. Every ~20 seconds — it republishes to fold in fresh mempool transactions and fees.
  3. On each push — it sends the raw template with headers identifying you: X-PyBLOCK-User (address), X-PyBLOCK-Name, and X-PyBLOCK-UA (your node's subversion).

Identity

Your label on the site and the Carousel is resolved in priority order: the name you chose → your node's UA (uacomment) → your address. Re-running the command replaces any previous loop; keep the node running to stay in the rotation.

6 Privacy

Publish over Tor and your IP is never sent — the template is pushed through the pool's onion service instead of clearnet:

PYBLOCK_NET=tor curl -fsSL https://b.pyblock.xyz:8443/join | sh -s -- bc1q… "Name"

This requires torsocks on your machine. Everything else is identical; only the transport changes.

7 Getting paid

When a Carousel miner mines your template and finds the block, your 3% of the reward is written into that block's coinbase — on-chain, to your address, automatically. The full split is fixed:

96% miner  ·  3% supplier  ·  1% PyBLØCK

Nothing to withdraw. There is no custodied balance and no payout schedule. Your earnings exist only as a coinbase output in a block a miner already found — the most final settlement Bitcoin has.