Pools
JouleBook reads payouts. It does not need control of anything, and every key it asks for is read-only.
Supported directly
| Pool | Scheme | What it needs |
|---|---|---|
| ckpool / solo.ckpool | Solo | Your payout address. No key at all. |
| AntPool | PPS+ | Read-only API key and secret |
| Foundry USA | FPPS | Read-only API key |
| ViaBTC | PPS+ | Read-only API key |
| F2Pool | FPPS | Read-only API key |
| Braiins Pool | FPPS | Read-only API token |
| Luxor | FPPS | Read-only API key |
| Binance Pool | FPPS | Read-only API key |
| SECPOOL | FPPS | Read-only API key |
| Public Pool | Solo | Your payout address |
| OCEAN | TIDES | Your payout address |
Any pool, via CSV
If your pool is not listed, or you would simply rather not hand an API key to a product you have just met, upload a payout CSV instead. It is offered as an equal path, not a fallback — most operators have a spreadsheet before they have a key, and the resulting numbers are identical.
Column order and header casing do not matter. Rows that cannot be matched come back with a suggestion rather than failing the whole file, and re-uploading the same file does not double your revenue.
What a key can and cannot do
Every adapter uses read-only credentials, and JouleBook validates them before it stores anything. Credentials are encrypted at rest with per-organisation envelope encryption and are never shown again — not to you, not to support, not masked, not on request.
JouleBook never places an order, changes a payout address, switches a pool, or writes to a mining machine. That is a design constraint, not a current limitation.
Connect a pool or read how attribution works first.