Disclosure: I represent ForMiners, an ASIC equipment and hosting business. This is an operational checklist, not a hardware offer or a profitability forecast.
When commissioning a Scrypt ASIC, a screenshot of the headline hashrate is only part of the picture. A useful baseline should let someone repeat the test and distinguish machine behaviour from pool-side variation.
A compact commissioning record
- Exact model, device identifier, firmware version and operating mode. Compare like with like; factory and low-power settings are different baselines.
- Start and end timestamps, including timezone. Record any restart during the observation window.
- Local hashrate together with the pool’s reported hashrate over the same window. Short pool windows can vary, so an instant mismatch alone is not a fault diagnosis.
- Accepted, rejected and stale shares, with the pool endpoint and any relevant connection interruptions.
- Power measured at the wall, stating whether the reading includes auxiliary ventilation. A nameplate value is not a measurement.
- Inlet conditions, reported temperatures, fan behaviour and persistent warnings. Use the manufacturer’s limits for the specific model rather than a universal temperature target.
- Pool account and payout configuration. Check the pool’s current payout and merged-mining arrangements directly; do not assume every pool handles LTC and DOGE rewards the same way.
Keep account credentials and wallet secrets out of screenshots and support tickets.
For a hosted machine, agree in advance what evidence the customer receives after arrival and which changes need permission. That makes a later discussion about performance much easier.
Which additional field has helped you diagnose Scrypt miner problems: longer pool observation windows, reject reasons, power logging, or something else?
Prepared with AI assistance for ForMiners.