ASIC Hosting Responsibilities: Host vs Hardware Owner

ASIC hosting responsibilities should be divided clearly between the facility and the hardware owner before any miner is shipped. This guide explains who normally controls power, cooling, network, pool settings, repairs, insurance, payments and equipment return, and why the signed hosting terms remain decisive.

Start with the contract and the responsibility matrix

Reassess ASIC hosting responsibilities whenever network conditions, firmware, tariffs or official guidance changes.

ASIC hosting responsibilities are not created by a general industry custom. They are defined by the signed quotation, hosting terms, site schedule and any service plan. One facility may provide only power, cooling and basic monitoring, while another performs pool configuration, cleaning and repairs. Treat every material task as either included, chargeable, owner-controlled or expressly excluded.

Build a responsibility matrix before shipping. Include equipment identity, delivery, electrical connection, cooling, network, firmware, pool and wallet settings, monitoring, restart authority, curtailment, cleaning, diagnosis, repairs, warranty work, insurance, incident reporting, storage and return. Name the party that acts, the party that pays and the approval needed.

The matrix should point to the controlling contract clause rather than replacing it. If a sales email conflicts with the executed terms, resolve the discrepancy in writing. Record authorised contacts and an escalation route so urgent operational instructions do not depend on an informal message from an unverified account.

What the hosting facility normally controls

When reviewing ASIC hosting responsibilities, separate measured facts from forecasts so the result can be reproduced.

The facility normally controls the site: electrical distribution, rack or container position, cooling plant, physical access, fire and security systems, network connection and operating procedures. It decides how to balance circuits, respond to site alarms and isolate equipment when safety or maintenance requires it. A host cannot promise that the public grid, internet carrier or manufacturer will never fail, but it should state how it monitors and responds.

The host should receive and identify equipment, document visible condition and commission it against an agreed acceptance process. Commissioning can include serial records, power-up, network discovery, accepted hashrate, temperatures and alarm checks. Where the facility provides insurance, the terms should identify insured value, exclusions, excess, claim evidence and the owner’s contribution.

Site access remains controlled by the host. The Mining Shop UK’s current hosting terms restrict ordinary customer visits for safety and security, with a stated exception for customers above the contractual capacity threshold. Remote visibility, reports and incident communications therefore need to provide enough evidence without giving customers unsafe physical or unrestricted network access.

What remains with the hardware owner

No conclusion about ASIC hosting responsibilities should rely on a single revenue snapshot or an undated specification.

The owner normally remains responsible for choosing the hardware, confirming that it is lawful to operate, providing accurate ownership and serial information, paying invoices and giving valid pool and wallet details. It should protect its pool, wallet and account credentials and verify addresses independently. A host should not be expected to recover cryptocurrency sent to a wrong address supplied by the owner.

Commercial outcomes also remain with the owner. Mining revenue changes with network conditions, fees, exchange rates and hardware performance. Hosting makes power and operational services available; it does not guarantee profitability, a bitcoin price or a fixed payback. The owner should retain tax, accounting and regulatory records appropriate to its circumstances.

The owner must disclose third-party warranty restrictions, non-standard firmware, prior repair history and special cooling requirements. If it sends used or third-party hardware, the site may require testing, cleaning, parts or a siting fee before rack-in. Shipping to the facility should be tracked and insured under the contract’s risk allocation.

Configuration, firmware and pool authority

Pool URL, worker name and payout destination are small fields with large consequences. The responsibility matrix should state whether the owner enters them, the host enters supplied values, or the host manages them under a separate service. Require a controlled process for changes, confirmation of the final address and a record of who authorised it.

Firmware and tuning need separate approval rules. Supported manufacturer firmware may be part of ordinary maintenance; third-party firmware can alter power, temperature, fees and warranty position. The host should not install an unapproved image merely because it promises more hashrate. The owner should not push remote changes that breach site power limits or defeat thermal controls.

Repairs, warranty and chargeable work

A host may perform an initial diagnosis when a machine fails, but diagnosis, repair and manufacturer warranty are different services. The contract should say whether basic inspection is included, when a diagnosis fee applies, who approves a quotation and what happens if the owner declines work. A site may need to keep the machine powered down until safe repair is agreed.

Define a spending authority. Routine work below a written threshold may proceed without individual approval; anything above it should stop for a quotation unless immediate action is needed to protect people or property. Record parts, firmware state, pre-repair symptoms, post-repair tests and the remaining warranty. Used or refurbished parts should be disclosed where they are permitted.

Manufacturer warranty handling can require removal, packaging, international shipping and third-party evidence. Decide who pays, who bears transit risk and whether hosting charges continue while the unit is away. The Mining Shop UK’s hosting terms and repairs terms should be read together when its facility performs chargeable work.

Billing, curtailment and downtime

Hosting invoices can include reserved energy, metered energy, management, cooling, network, setup and other site-specific charges. The owner should know the billing period, payment deadline, deposit treatment, tariff-change notice and consequences of late payment. Turning a miner off does not necessarily stop a reserved-capacity charge if the contract commits power for a fixed term.

The facility may curtail or underclock equipment for grid events, site limits, negative operating conditions or safety. The contract should identify when owner instruction is required and when the host can act immediately. At The Mining Shop UK, the owner may request power-down or underclocking, while the site retains operational authority needed to balance infrastructure within manufacturer tolerances.

Uptime reporting must exclude agreed categories consistently. Hardware faults, owner configuration, wallet or pool errors and force majeure may be treated differently from site-controlled downtime. If a service credit or equivalent hashrate remedy applies, document the measurement window, calculation, timing and whether it is the exclusive contractual remedy.

Termination, storage and return of equipment

The exit process should be designed before installation. Confirm notice period, fixed energy commitments, outstanding invoices, de-racking, packaging, collection or shipping, insurance and the condition report. The owner should keep delivery details current and respond promptly to collection notices.

Unpaid or uncollected hardware cannot remain indefinitely. Hosting terms may provide a free or charged holding period, daily storage and a statutory process for uncollected goods. Those steps must follow the contract and applicable law; they should not be improvised after the relationship breaks down. The host should retain notices and inventories.

Before return, reconcile serials, accessories, replaced parts, firmware and recorded damage. Decide whether the owner or host buys transit insurance. A signed handover or tracked delivery record closes the custody chain and reduces later dispute about when risk transferred.

Common hosting-responsibility mistakes

• Assuming monitoring includes repairs, tuning and pool management.
• Giving wallet-change authority through an informal or unverified message.
• Installing third-party firmware without checking site limits and warranty terms.
• Treating power-down as automatic cancellation of reserved energy charges.
• Ignoring shipping risk, insurance excess and manufacturer warranty logistics.
• Using an uptime percentage without defining exclusions and measurement method.
• Waiting until termination to discuss de-racking, storage and equipment return.

Review the matrix whenever the site, machine, firmware, tariff or service plan changes. Store it with the signed terms and commissioning record. Operational clarity is more valuable than a broad claim that the host ‘handles everything’.

Frequently asked questions

Who owns a hosted ASIC miner?

The customer normally retains title to customer-owned hardware unless a separate sale, finance, abandonment or uncollected-goods provision lawfully changes that position. Read the signed terms.

Who chooses the mining pool and wallet?

Usually the owner supplies and verifies them, although a managed service may configure approved values. The authority and verification process should be written.

Can a host change a miner's power profile?

A host may need operational authority for safety and infrastructure balancing. The contract should define permitted profiles, owner requests and circumstances requiring immediate action.

Who pays for a hosted miner repair?

It depends on warranty, cause and service plan. Diagnosis, parts, labour, shipping and hosting during repair should be addressed separately.

Does switching off a miner stop hosting charges?

Not always. Reserved energy or fixed-term charges may continue under the contract even when the device is powered down.

Conclusion

Clear ASIC hosting responsibilities protect both the facility and the hardware owner. The host operates the site; the owner remains responsible for its hardware choice, commercial outcome, credentials and payments except where a managed service says otherwise. Put every material task, approval and cost into a responsibility matrix linked to the contract, then keep commissioning, change and incident records throughout the placement.

Next steps

Read The Mining Shop UK’s hosting terms and request a site-specific quotation and responsibility schedule before shipping equipment or reserving power.