Fleet Pool: Setup Guide for Datacenters

Fleet Pool is a PPLNS pool dedicated to one datacenter: every block the pool finds is divided among your clients by the work each one did recently, and every part is written straight into the block’s own coinbase transaction, at each client’s address. We take a fixed 1% of each block. Nobody holds a pool wallet and there is nothing to withdraw.

Fleet Split and Fleet Group are solo mining: a client waits for a block, which can take years. Fleet Pool spreads every block over everyone who worked in the window, so a client with 2 PH/s in a 100 PH/s datacenter receives a part of almost every block the pool finds. Over many years the expected value is the same as solo mining; what changes is how often each client receives something, and how much each time.

Version 1.0 · 1 November 2026 · Bitcoin (BTC). Fleet Pool opens on request for datacenters with at least 100 PH/s committed; a pilot with fewer machines is possible. Each datacenter receives a written agreement. For the comparison with Fleet Split and Fleet Group, see SoloFury Fleet: Split, Group and Pool. Numbers on this page use the network difficulty of 1 November 2026 (148.36 T).

Key takeaways

• PPLNS (Pay Per Last N Shares): each block is divided by the work in a window of recent shares, weighted by difficulty. The window holds the work of one network difficulty, and a share leaves it after 90 days at most.
• The coinbase of a pool block has 1% to us and 99% to the clients in proportion to their work in the window. Payouts are outputs of the coinbase, at each client’s address.
• A part below 5,000 satoshi becomes a credit and is paid in a following block. Nothing is lost and nothing goes to the pool.
• Access is by IP: the pool ports open only to the addresses of your datacenter. The username is the client’s Bitcoin address; there is no invitation and no signature.
• Each client follows their share, balance and payouts on a private page reachable with their address.
• Coming: a fixed quota of every block for you, a Fleet Pool view in the operator console, Telegram alerts and public Fleet Pool terms. Until then you have the agreement, the client pages and our support at [email protected].

How Fleet Pool works

A pool divides each block among the miners who worked to find it. The question is which work counts. In Fleet Pool it is the last part of the work sent by your machines, called the window.

The window

Every accepted share enters the window with its difficulty: a share at difficulty 250,000 counts 250,000 times a share at difficulty 1. The window holds the most recent work, up to a total equal to one network difficulty, which is the work needed on average to find one block. When new work arrives, the oldest work leaves. A share also leaves after 90 days, even if the window is not full.

How long the window lasts depends on the hashrate of the pool. With 100 PH/s it holds about the last 73.8 days of work; with 200 PH/s about 36.9 days. Below about 82 PH/s the 90-day rule comes first.

When the pool finds a block, each client receives a part equal to their share of the window. Nothing restarts at a block: the window keeps sliding. A new client starts with a small share that grows as their work accumulates; a client who stops keeps a share that shrinks as newer work pushes theirs out.

The coinbase of a pool block

The block reward is the subsidy, 3.125 BTC today, plus the transaction fees of the block. The coinbase divides it like this:

Example: a client with 2% of the window receives 2% × 3.125 BTC × 99% = 0.061875 BTC, plus 2% of the transaction fees after our 1%. All outputs of a block sum exactly to the reward.

Credits and debits

A coinbase output below 5,000 sat is not created. Today a coinbase has room for about 285 client outputs; for a larger fleet we raise that room before you start. When a part cannot be an output, the pool does not keep it: the value of the parts left out is spread over the clients who are paid in that block.

• The client left out receives a credit equal to their part. At the next block the credit is added to their new part, and they are paid when the total reaches 5,000 sat, even if they no longer mine.
• The clients who received that extra value get a debit of the same amount, which is taken from their next payouts.

Credits and debits always sum to about zero, and every client sees their balance on their page. A credit of an address that has sent no shares for 90 days is offset against open debits; it never goes to us.

Example: a Bitaxe at 1.2 TH/s in a 100 PH/s pool has about 0.0012% of the window. Its part of a block is about 3,700 sat, below the threshold: it becomes a credit. At the next block credit and new part add up to about 7,400 sat, and the Bitaxe is paid in that coinbase.

Confirmations and orphans

Balances move only when a block has 3 confirmations. If a block is orphaned, it paid nobody and nothing changes: the window and the balances stay as they were. The outputs of a block can be spent after 100 confirmations, about 17 hours, like any coinbase.

Before you start

• Your committed hashrate and the number of clients. Fleet Pool is for datacenters with at least 100 PH/s committed; for fewer machines ask us for a pilot.
• The outgoing IP addresses of your datacenter: the public addresses your machines use to reach the internet. They must be fixed.
• One Bitcoin address per client, from a wallet the client controls: bc1q…, bc1p…, 1… or 3…. Exchange deposit addresses are not suited: many exchanges do not credit coinbase outputs.
• Where your machines are: today Fleet Pool runs on our server in Atlanta (US East); on request it runs on a node closer to your datacenter.

Step 1: Write to us

Send to [email protected] your committed hashrate, the outgoing IP addresses, the location of the datacenter and the number of clients. We reply with the written agreement for your datacenter: fee, payout threshold, window, coinbase room, access, support and how changes are announced.

Step 2: We open access to your addresses

The pool ports accept connections only from the IP addresses in your agreement. We add them on our servers and on the network firewall in front of them, then send you the host and the ports. Machines from any other address cannot connect.

Inside your network, the pool does not check who mines: every machine that connects is paid on the address it uses as username. You decide which machines mine on Fleet Pool and with which addresses. Tell us when your outgoing addresses change: until we update the list, machines from a new address cannot connect.

Step 3: Configure the machines

Each machine needs three values. The host is the one in our reply.

The part before the first dot is the address that is paid; the part after it is only a name for the machine and shows up on the client page. All machines of a client use the same address.

Pool 2 and pool 3. While a machine mines on another pool, its shares do not enter the Fleet Pool window. If you want a backup, you can set our public solo server btc.solofury.com:6060 with the same username: there a machine is paid only for a block it finds itself. Any other pool works too; it pays by its own rules.

Step 4: Check the machines

Open the client page solofury.com/fleet-pool/?addr=<client address>. Within a few minutes of the first shares it shows the hashrate, the machines online and the share of the window. The share starts small and grows day by day while the client’s work fills the window.

If a machine does not appear after 10 minutes, check that it connects from an address in your agreement, that the URL has the right port, and that the username starts with a valid Bitcoin address.

Step 5: Give your clients their page

Send each client the link to their page and the Fleet Pool guide for hosted miners, in their language. The page shows only the data of the address in the link: share of the window, hashrate, machines online, balance, total paid, an estimate of their part if the pool found a block now, and every payout with its block.

Anyone who has the link can see that page, like any miner page of the site. The list of all clients and their shares is not public.

Step 6: When the pool finds a block

1. The block reaches the network with the coinbase already divided: 1% to us, the clients’ parts at their addresses.
2. After 3 confirmations, about 20 minutes, each client page shows the payout in “Your payouts”, with the block height and the share. Parts below 5,000 sat show as “to balance”.
3. After 100 confirmations the bitcoin can be spent from each client’s wallet.

Every output is on the blockchain: any block explorer shows the coinbase of the block with all its outputs.

Step 7: A client joins or leaves

A new client needs only machines that mine with their address from your network. There is nothing to sign and nothing to change on our side. Their share starts at zero and grows as their work enters the window.

A client who leaves just stops mining. Their work stays in the window until newer work pushes it out, or for at most 90 days, and each block until then pays them a shrinking part. A credit below 5,000 sat is paid by a following block if it reaches the threshold; after 90 days without shares it is offset against open debits.

Step 8: Follow the pool

Today you follow Fleet Pool from the client pages: each one shows the pool’s state (miners in the window, size of the window) and the client’s own numbers. For a summary of the whole fleet, ask us: we send you the shares and balances of your addresses.

What is coming

These parts of Fleet Pool are not live yet. We write them here so that you know what to expect; there are no dates.

• Your quota. A fixed share of every block for the operator, written in the agreement and paid as its own output of the coinbase, as in Fleet Split and Fleet Group. Until then, your own machines can mine in the pool with your address like any client.
• Fleet Pool in the console. A view in the operator console with every address of your fleet, its share, balance and payouts, and the blocks of the pool.
• Telegram alerts for you and your clients: a block found, machines offline, payouts.
• Public Fleet Pool terms next to the Fleet terms. Today each datacenter has its written agreement.

Rules in one table

What the numbers say

With 100 PH/s the pool finds about 4.95 blocks a year on average. A client with 2 PH/s in that pool has about 2% of the window and receives about 0.0619 BTC per block, about 0.31 BTC a year on average, before transaction fees. These are averages: the pool can find two blocks in a week and then none for several months. Solo mining and PPLNS give the same expected value over many years; PPLNS makes each client’s payouts more regular.

The fee is 1%. An FPPS pool pays every day whether it finds blocks or not, and charges more for it, often 2% to 4%. With Fleet Pool your clients accept irregular payouts in exchange for a lower fee and payouts written directly into the blocks.

How we work

• Non-custodial payout. Every part is an output of the coinbase we build; the network creates the bitcoin at each client’s address.
• Nothing kept by the pool. Parts too small for the coinbase become credits and are paid later; they never go to our fee.
• Numbers you can check. Every payout is on the blockchain, with the block height on the client page.
• Announced changes. Updates that may interrupt mining are announced ahead by email; security fixes are applied at once and announced afterwards.

Conclusion

Fleet Pool gives the clients of your datacenter a part of almost every block the pool finds, written into the block itself at their own address, with a 1% fee. Access is by IP, the username is the client’s address, and each client has a page with their share and payouts. The operator quota, the console view and the alerts are coming.