A Bitcoin miner setup is complete when the machine operates safely, contributes accepted work, and can be recovered after a fault. Seeing fans spin or a local hashrate appear is only the beginning. A disciplined commissioning process protects the equipment and produces a baseline for future troubleshooting.
This is a planning and software-configuration checklist, not a substitute for your model's installation manual or a qualified electrical assessment. Do not energize equipment with damaged connectors, uncertain supply requirements, or an unapproved cooling arrangement. Start with our Bitcoin mining overview to understand the workflow, then use these stages to organize a controlled first run.
Identify the exact delivered unit
Record the manufacturer, full model name, serial number, cooling variant, power-supply details, and included accessories. Match those details to the purchase record. Inspect packaging and accessible surfaces for shipping damage, and photograph any discrepancy before discarding materials. Do not open sealed components or disturb internal connections just to satisfy a generic internet checklist.
Retrieve the manual for that exact configuration from the manufacturer's verified support channel. Similar product names do not guarantee identical electrical, thermal, or startup requirements. As an example of model-specific documentation, BITMAIN's S19 and S19 Pro setup guide covers inspection, configuration, and administration for those models. Use your own current manual as the authority for your equipment rather than applying another device's limits.
Finish the site checks before startup
Confirm that the electrical installation has been assessed for the intended load and operating schedule. Keep the manufacturer's disconnect instructions available, particularly when equipment has more than one power input. Do not infer suitability from a connector shape, an adapter listing, or another miner's experience in a different building. Local requirements and actual equipment ratings matter.
Check that the installed cooling system matches the machine. Air-cooled, liquid-cooled, and immersion-oriented equipment are not interchangeable installation choices. Make sure intake and exhaust routes are unobstructed and that placement allows normal service access. Keep the surrounding area free of items that could interfere with airflow or access. Resolve uncertainties before power-on rather than using an initial run to discover an avoidable site problem.
Prepare a controlled management network
Set up a network arrangement in which the miner's management interface is not exposed directly to the public internet. Use a trusted router or managed network appropriate to the site, and document how you will identify the appliance. A reserved address or maintained device inventory can make recovery easier, but follow the equipment's supported network configuration process.
Keep management access separate from unrelated users where practical. Change default credentials through the documented interface, use a unique password, and store it in your normal secure credential system. Do not paste secrets into shared screenshots or support forums. If remote management is needed, use an authenticated access method designed for that purpose rather than forwarding the appliance's web interface to everyone on the internet.
Verify pool and payout information independently
Choose a pool based on documented terms, supported connection methods, payout arrangements, and the operational features you need. Obtain connection details from the pool's verified site, not from an unsolicited message or a preconfigured seller account. Record the endpoint, worker naming convention, and any required authentication without storing sensitive credentials in a public checklist.
Review payout details separately from worker connectivity. Some pools associate a worker with an account; others use a different documented arrangement. Do not assume the miner's local password is a wallet credential. Confirm that any payout address belongs to the intended recipient and that account settings are correct. A machine can successfully submit work while the destination or account configuration is still wrong.
Establish a stock configuration baseline
Begin with the manufacturer's supported operating settings. Avoid overclocking, unofficial firmware, or multiple simultaneous adjustments during initial acceptance. The objective is to confirm that the delivered equipment functions as specified under suitable conditions. A baseline contaminated by several untracked modifications is less useful when you later ask the seller or manufacturer for help.
Record firmware version, operating mode, start time, environmental observations, and the measurement tools used. Check which status fields refer to intake air, exhaust, board sensors, or chip estimates; those values should not be treated as the same temperature. When an unsupported or unavailable metric appears, preserve that state in the record instead of silently replacing it with zero. Missing information is a diagnostic clue, not a successful reading.
Confirm accepted work over time
Compare local status with the pool's record over a meaningful, aligned time window. A local hashrate reading can move differently from a pool-side estimate, especially during startup or short observation periods. Record connection changes, rejected shares, restarts, and interruptions alongside performance data. Do not treat one favorable minute as proof of sustained operation.
Watch for patterns rather than a single number. Repeated reconnections may point to a network or pool issue; declining output alongside a cooling warning suggests a different investigation. These are starting hypotheses, not diagnoses. Change one variable at a time when the manual and support process permit it, and keep the before-and-after evidence. Our monitoring guide explains how to make those records useful.
Set alarms that somebody can act on
Define a small initial set of alerts around connectivity, sustained output loss, manufacturer-reported faults, and missing telemetry. Each alert should have an owner and a first response. Avoid arbitrary universal temperature limits: use the model documentation and the actual meaning of each sensor. Decide how long a condition must persist before an informational event becomes an operational alert.
Treat stale data as a separate state. A dashboard showing the last known good reading after communication stops is not evidence that the miner is healthy. Record the timestamp and the expected reporting interval. Test the notification path without deliberately creating a hazardous condition. A safe test can use the monitoring software's test function or a controlled change in the reporting system rather than stressing the machine itself.
Prove that recovery is possible
Save the approved configuration and record the normal shutdown and restart procedures. A recovery plan should identify what happens after power loss, network interruption, firmware failure, or loss of access credentials. Where a restart test is appropriate, follow the manufacturer's instructions and coordinate it with the site's electrical and operating procedures.
Keep a separately stored copy of configuration notes, receipts, serial numbers, and support contacts. Do not depend on the failed miner to provide the only copy of its setup. Record how to remove pool credentials and other sensitive settings before a repair return or resale. The purpose is not to predict every fault; it is to prevent a routine interruption from becoming an improvised investigation with no reliable starting point.
Keep a commissioning timeline
Use one clock convention for device logs, pool observations, and your notes, including the time zone. Record the beginning and end of each test, who observed it, and any interruption. This makes a later support conversation much more concrete: the supplier can inspect a particular interval rather than guess which reading belonged to which change. Preserve unedited original logs alongside your summary, removing credentials before sharing them.
Close the commissioning record
End the initial run with a short acceptance report. Note what passed, what remains unresolved, what evidence was saved, and who is responsible for follow-up. A minor unresolved warning should remain visible rather than disappearing because the headline hashrate looks good. Keep the report linked to the exact machine and configuration tested.
Use the equipment buying checklist to confirm that acceptance matches the original purchase criteria. A successful setup creates both useful mining work and a dependable operating record. That record makes later maintenance, support, and replacement decisions easier to handle without guesswork.
