The model name is the start of the inventory
Our S19j Pro catalogue has separate AML, BB, CV and XIL builds. Keep the exact model and confirmed board together in your inventory, then use the catalogue for the current file choice
The board identifies the software route. It does not establish a hashrate or efficiency advantage
If a board is unconfirmed, keep that device outside the ready-to-roll group and follow our identification guide. Do not guess from the machine beside it
Confirm the control boardMake groups that answer a real rollout question
Start with confirmed model and board, then record the current build, profile, condition and operating environment. Split the group again when those differ materially
Two sets with the same board can still need separate records because their starting profiles or conditions differ
Give each group an identifier, a count and a pilot device. Now ask: what have we observed for this configuration, and which comparable machines could join the next limited batch?
| Group record | What it helps decide | What it does not establish |
|---|---|---|
| Confirmed board | The S19j Pro catalogue file choice | Identical performance |
| Starting conditions | Which devices are comparable | The result of an untested group |
| Pilot A/B record | The next limited follow-up | A result for the entire fleet |
| Group count | The size of a calculated scenario | Profit already measured across the group |
Keep one A/B pair with each pilot
Record the pilot before and after: profiles, comparable windows, measured power, hashrate source, fees and any errors or restarts. Keep the measurement boundary and hashrate basis consistent within the pair
A good observation on one device does not prove the result of its entire group. Size the next limited batch to what you can observe and support
Keep an unexplained failure visible in the status. A favourable average elsewhere does not turn that machine into a passed pilot
Run the calculator once per comparable group
Run a separate comparison for each group's measured or clearly labelled estimated profiles. Enter only that group's count: the calculator extends one pair across the count you supply
When combining group scenarios, use the same period and units, with explicit revenue and tariff assumptions. Keep untested groups separate
The calculator assumes 24 operating hours and constant inputs. Assess different downtime or extra costs separately. Its fleet number is a scenario, not an outcome already measured on every machine
Build a small rollout ledger
Use one entry per comparable group. Confirm the board and add known inputs; the form does not detect hardware. Add more groups in your own records if needed
Your entries stay on this page. Copy the record to keep it. Keep the detailed A/B observations beside each group
Give every group a next step
Give each group a useful status: board unconfirmed, baseline missing, repeat comparison, issue under review, or ready for a limited follow-up
With a complete record, identify the next comparable machines and keep their outcomes separate from the original pilot. With missing data, gather the observation. With an unexplained problem, bring us the group, model, board, builds and relevant log
Use the catalogue for the board-specific choice and the calculator for the group's scenario. Keep observed results separate from planned actions in the ledger