Your pool pays a wallet. This tells you which machine earned it.

Most operators close that gap in a spreadsheet once a month, reconciling a pool CSV against a power bill by hand. It works, it takes a day, and it is wrong in ways nobody can see. That spreadsheet is what this replaces.

Break-even hashprice is a property of a machine and its power rate, not of your fleet. JouleBook ranks every machine by how far below water it is and gives you the list.

Export the list as CSV and act on it however you already act on things. JouleBook does not curtail anything itself — see the limitations below.

A pool pays one wallet for the work of many machines. JouleBook splits each payout across the machines that were actually running during the window it covers, weighted by the work each of them did:

share(machine) = (hashrate × active_hours)
                 ÷ Σ(hashrate × active_hours)

attributed_sats = floor(payout_sats × share)

Every satoshi is accounted for. The split is computed in integer satoshis and the remainder from rounding goes to the largest holder, so the parts always sum to exactly what the pool paid — never one satoshi more or less.

Where telemetry exists the hashrate is measured. Where it does not, nameplate is used and the result is labelled ESTIMATED on every screen and in every export. It is never quietly presented as measured.

The full method, including what happens with no telemetry

JouleBook computes what the network paid out for the work your fleet actually did, compares it to what your pool credited, and reports the difference as the fee you really incurred. It follows your pool’s payout scheme — FPPS, PPS+ and PPLNS pass transaction fees through, so the baseline includes them.

When there is not enough network history to state a fee honestly, it says so instead of printing a number. That refusal is the feature.

Foreman, Braiins and Hive OS answer is my fleet healthy. They do it well, and several of them are free. JouleBook answers a different question — is my fleet profitable, machine by machine — and expects to sit beside them.

Nothing about installing JouleBook changes your operations stack. It reads your pool payouts and, optionally, your telemetry. It writes nothing to your hardware.

Where JouleBook fits beside a fleet manager

Free for one site and 25 machines, permanently — not a trial. Above that, $5 per site per month on Starter and $12 on Pro. A 500-machine site costs the same as a 50-machine one.

Full pricing, in USD and INR

• No control over your miners. JouleBook never reboots, curtails, switches a pool, or writes anything to your hardware. It is read-only with respect to your machines by design, which also means a bug here cannot cost you hashrate.
• No monitoring or alerting. It will not page you when a miner goes down. That is what your fleet manager is for, and it is probably already doing it better than a new product would.
• Not a replacement for your accountant. JouleBook produces the per-machine figures and the exports your accountant needs — including a QuickBooks journal and an India Schedule VDA sheet. It does not file anything and it is not tax advice.

• How to calculate per-machine profitability

  The formula worked through with real numbers, the two places a hand-built sheet usually goes wrong, and a working spreadsheet with the formulas already in it.

• Break-even hashprice by ASIC model

  What hashprice each common machine needs to cover its own electricity, from the S9 to the S21, at four power rates — and the unit conversion that makes most attempts wrong by a factor of a thousand.

• What your effective pool fee actually is

  How to measure it correctly, including the baseline mistake that makes an honest FPPS pool look like it is paying you a bonus.