Before you store an ASIC miner
Store the exact machine according to its own manufacturer documentation, not a temperature range copied from another miner. Keep the equipment identity, packaging condition, storage location and release decision together. An air-cooled unit waiting for a rack and a hydro unit removed from a cooling loop need different handling records.
This guide is for the unpowered interval between receipt and deployment, or between removal and relocation. It is not a repair procedure, a promise of remaining service life or a universal preservation specification. The tables combine two clearly identified manufacturer examples with an original LeedMiner planning worksheet. No warehouse trial or customer inspection is claimed.
Separate three questions
Ask what the manufacturer permits, what actually happened to this unit, and who will approve the next step. Those answers belong in different fields. A published limit is not a measurement of your warehouse. A clean-looking carton is not a record of its transport history. A planned installation date is not confirmation that the receiving site is ready.
Start with a folder or asset record for each serial-numbered machine. Give the record a named owner. If a batch shares one storage location, link the location log to each unit rather than copying a reassuring sentence into every record. Exceptions should remain visible when the batch moves.
Storage limits are model-specific
The BITMAIN S21 User Guide, March 2025, section 5.1.1 separates storage from operation. The figures below are S21 examples, not specifications for S21 XP, S21 Pro or hydro variants.
| Document scope | Storage conditions stated in that document |
|---|---|
| BITMAIN S21, March 2025 guide | −20 to 70°C; 10–90% relative humidity, non-condensing |
| WhatsMiner hydro-cooling guidance | −40 to 70°C; short-term 5–95% RH and long-term 30–69% RH, non-condensing |
The second row comes from WhatsMiner's installation and deployment Q&A, questions 9–11. It also requires draining liquid when storage or transport exceeds two hours. Treat this as hydro-specific guidance; use the exact model's draining procedure and ask support about any uncertainty.
These examples show why one warehouse label saying “ASIC storage approved” is inadequate. Record the manufacturer, full model suffix, cooling method, document revision and applicable section. If two documents appear inconsistent, keep both references and obtain clarification instead of choosing the wider range. Do not infer an unlimited storage duration from a temperature table.
Keep packaging evidence with the unit
BITMAIN's return-for-repair packaging guidance favors original packaging and model-matched foam; it warns against bare-machine transport. Its context is repair returns, not a guarantee covering every shipment or warehouse arrangement.
For your own receiving record, photograph the carton, labels, cushioning and visible condition before discarding anything. Use file names that connect the images to the correct unit and date. Keep a brief description of what was observed, separate from assumptions about who caused it. If packaging is replaced, record what changed and which packing instruction the replacement follows.
Do not call an unopened box “inspection passed.” A more useful status is “received, external packaging recorded, internal inspection pending.” That wording tells the next person exactly what evidence exists without implying that the machine has been powered, tested or accepted. Remove personal addresses from copies shared outside the receiving team.
A practical storage record
The following is an editorial worksheet, not a manufacturer certificate. It is designed to leave an auditable handover between purchasing, receiving and the installation team. Fill it with actual observations; use “not recorded” where evidence is missing.
| Record field | What to retain | Decision it supports |
|---|---|---|
| Equipment identity | Full model, cooling type, serial number and asset ID | Correct document and unit matching |
| Document basis | Official URL, revision, section and retrieval date | Which handling requirements apply |
| Receipt condition | Dated exterior observations and original photographs | Whether further inspection is needed |
| Storage assignment | Location, responsible person and entry date | Who owns the next check |
| Environment record | Actual readings, measurement times and instrument reference | Whether conditions need review |
| Exceptions | Missing evidence, observed damage and support reference | Why release is on hold |
| Release record | Reviewer, date, destination and unresolved items | Whether a move or installation is approved |
Agree on the review cadence before the equipment is left unattended. The appropriate interval depends on the applicable documentation and the site's conditions; this article does not invent a universal daily, weekly or monthly requirement. The useful outcome is a named person who knows when to inspect the record and what triggers escalation.
Keep original observations when correcting a record. For example, if a location was entered incorrectly, append the correction and reason rather than rewriting the history as if the first entry never existed. Separate administrative corrections from changes to the machine itself.
Treat relocation as a new handover
A move to another room, warehouse or host should create a new location entry, not erase the earlier one. Record departure, arrival, transport packaging and the person receiving the unit. If custody changes, agree who retains the original documents and how the receiving team can retrieve them.
For a proposed ASIC hosting arrangement, ask where equipment waits before commissioning, who records receipt, how exceptions are reported and what evidence accompanies a later return. These are questions to resolve with the provider, not statements that every hosting plan includes the same services.
Compare a purchase or relocation schedule with site readiness before committing to a move. Keep “delivered,” “stored,” “installed” and “running” as separate milestones. A tracking notification establishes a logistics event; it does not establish operating performance. Likewise, a storage record should not be presented as a hashrate test.
Release to deployment, not straight to power-on
BITMAIN's general ANTMINER precautions call for checking visible damage and loose heat sinks, disconnecting power during installation or maintenance, and avoiding use of apparently damaged equipment. Follow the current model instructions and qualified installation review rather than treating this article as electrical installation guidance.
Use the storage worksheet to prepare that review. Hand over the unit identity, relevant manual, condition record and outstanding questions together. If a question remains unanswered, retain an explicit hold reason and a responsible contact. Do not replace missing evidence with a generic “ready” checkbox simply because the scheduled installation date has arrived.
If firmware work is proposed, keep it as a separate maintenance decision and use the Antminer firmware preflight checklist. Storage alone is not evidence that an update is required. For equipment selection, the Antminer S21 XP product page is a separate model reference; the S21 storage figures above must not be assigned to it by name similarity.
Before arranging a shipment, contact LeedMiner with the full model, cooling method, intended storage interval and destination. Request the applicable documentation and clarify any missing handling information. Keep commercial availability and warranty terms separate from technical handling instructions.
