A used ASIC miner handover is complete when the receiving team can identify the machine, administer it through an approved route and verify where its new work is going. Receiving a password or seeing a hashrate screenshot is only part of that process. Establish which access belongs to the device, which belongs to a mining service and which belongs to the hosting operator before changing anything.
This guide proposes an access-handover record for equipment you are authorized to receive and manage. It is separate from a condition inspection, warranty lookup or purchase agreement. No customer credentials or completed customer handovers are presented here. The real facility photographs provide operating context, not evidence of a particular security assessment.
1. List the access that changes with the equipment
Start with one identified unit and the people responsible for it. Record the exact model, private asset reference, installed firmware and current location. Ask the outgoing operator to describe the normal management route: local interface, approved remote service, hosted portal or a combination. A browser bookmark alone does not explain who controls the account behind it.

Use a small responsibility table. Keep actual secrets in the receiving team's approved credential system and put only a reference in the handover document. A shared list of passwords becomes difficult to control as soon as it is copied into email, tickets or chat history.
| Access layer | Handover question | Useful completion evidence |
|---|---|---|
| Miner administration | Who can change the device settings? | Receiving operator can sign in through the approved route |
| Pool connection | Which account and worker will receive new work? | Intended configuration and fresh activity agree |
| Pool account | Who owns and administers the service account? | Account owner confirms the intended access scope |
| Hosting or remote management | Which users, roles or integrations remain necessary? | Responsible provider confirms the access arrangement |
The distinction is visible in BITMAIN's 19-series interface guide: pool configuration, network configuration and system password controls are separate areas. Use that document only for the interface it describes. Another model or firmware may organize these functions differently.
Do not ask a seller to hand over an unrelated personal pool account merely because a miner previously used it. Agree which receiving account should be configured and how the outgoing operator will close their own involvement. Existing balances, payout destinations and account recovery belong to a separate account process. Our payout-address verification guide covers that separate scope.
For hosted equipment, the customer may receive portal visibility while the facility retains device administration. Record that arrangement explicitly. The acceptance question is whether the agreed role works, not whether every participant has the broadest possible permissions. Keep the physical identity record linked to our worker and asset-register workflow, without treating a worker label as proof of ownership.
2. Plan the access change before resetting the miner
Agree a handover window and preserve the necessary operating details privately. Identify who can recover access if the network configuration changes and who must approve any interruption. Do not combine an access transfer with overclocking, an unplanned firmware experiment or a broad fleet reset. Each additional change makes the result harder to explain.

A factory reset is a model-specific operation, not a universal handover button. BITMAIN's reset guidance distinguishes interface procedures and physical-button methods, including model-specific applicability. Read the procedure for the actual unit and installed software. This article deliberately does not supply one button duration for every Antminer.
Similarly, an update does not necessarily clear the outgoing configuration. BITMAIN's online-upgrade tutorial explains a retain-settings choice and warns that a network change can affect the address used to reconnect. Decide what the supported procedure preserves before starting. Use our firmware download checklist when a firmware operation is actually required; access transfer alone is not evidence that an update is needed.
Record the result you need: a receiving operator can authenticate, required settings are known, and the old operator no longer has access that should have ended. Changing a device password does not by itself review a hosting portal, remote-management account or pool service. Assign those account-side checks to their respective owners and follow each service's supported controls.
BITMAIN's security guidance recommends changing the miner password and obtaining firmware from its official source. Its guidance also treats suspected compromise as a separate response case. Do not describe a routine password change as a malware clearance certificate. If settings unexpectedly revert or work appears at an unexplained destination, keep the handover open and involve the responsible support team.
The Antminer S21 XP below illustrates a precise catalog reference. It does not identify the controller, condition or access history of a particular used unit, and the 19-series interface cited above is not an S21 procedure.
Antminer S21 XP 270 TH/s

Air-cooled Bitcoin miner. Confirm the identity and installed software of the actual unit before maintenance.
3. Verify receiving access and close each open item
Have the receiving operator verify their own access through the agreed route. Record the observation time and unit reference, rather than attaching a screenshot containing a password. Where a service supports reviewing users, roles or active sessions, have its account owner confirm the appropriate state. Mark unsupported or unverified checks explicitly instead of assuming a device reset completed them.

Next, compare the configured pool and worker with fresh activity in the intended account. Confirm each relevant pool entry, including standby entries, rather than checking only the first row. Our backup-connection verification guide explains why a saved address and an observed fallback are different evidence. An old dashboard average cannot establish exactly when new work started.
| Closing check | Record | Keep open when |
|---|---|---|
| Receiving access | Operator, unit reference, approved route and time | The expected operator cannot use the agreed role |
| Mining destination | Configured identity and newly observed activity | The destination or worker is unexplained |
| Outgoing access | Owner confirmation for each applicable service | A role, integration or credential remains unresolved |
| Exceptions | Specific issue, responsible person and next check | Only a generic “done” message is available |
Keep access acceptance separate from performance acceptance. A successful login does not demonstrate stable hashrate, and a working miner does not demonstrate that former service permissions were reviewed. Likewise, neither outcome settles physical condition or manufacturer coverage. Follow the separate serial-number warranty check for that evidence.
For a batch, close records per unit and account scope. Do not mark twenty machines transferred because one password worked. Retain the historical operator and effective handover time, but remove unnecessary secret copies according to your own retention process. Give the receiving team a clear support contact and a list of unresolved items they can act on.
Discussing a used-miner purchase or hosting arrangement? Contact LeedMiner with the model, proposed handover scope and access questions. Share sensitive equipment records privately; never include wallet seeds, private keys or account recovery codes in the inquiry.





