这个顺序没有人来挑选。它来自一条公开规则 — turn = agenda[(start + cycle) mod n]，其中 start = (height × 11) mod n — 议程每个区块冻结一次，正因如此接下来的七个轮次才能被预告。你可以自己重算：这个区块的议程就是上面的 21c4ef1d，工具已在仓库里发布。
不在这八个里并不代表你出局或损失了什么。你在本轮里 — 全部 2,434 个 — 你的轮次会到。这是"接下来是谁"的窗口，不是"谁拿到钱"的名单。
| Supplier | Status | Last picked | Blocks | Fees | |
|---|---|---|---|---|---|
| Loading… | |||||
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.
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.
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.