HashFlare Halted Bitcoin Cloud-Mining Contracts as Customers’ Returns Vanished

HashFlare stopped providing mining service for active SHA-256 contracts on July 20, 2018, after telling customers that Bitcoin mining proceeds had fallen below its maintenance charges.

The company said it began disabling SHA-256 hardware on July 18 and that payouts had remained below maintenance fees for 28 consecutive days. Under HashFlare’s account, customers received no balance accrual when the service charge consumed the entire mining payout. The company invoked a profitability provision in its terms when announcing the halt.

The development mattered because HashFlare sold exposure to remotely operated mining capacity rather than physical machines delivered to customers. Contract holders depended on the provider for hardware access, electricity, maintenance, reward accounting and withdrawals. When the economics deteriorated, customers could not independently inspect the equipment or redirect the contracted computing power.

What HashFlare customers had purchased

A cloud-mining contract gave a customer a stated quantity of processing power, commonly called hashrate, while the provider operated the underlying equipment. Bitcoin rewards attributed to that hashrate were credited after contractual charges.

That structure separated customers from several facts needed to evaluate performance: which machines were operating, their efficiency, the provider’s electricity expense, the hashrate actually available and the method used to allocate mining proceeds. HashFlare’s profitability claim therefore cannot be independently verified from its announcement alone.

Contemporaneous reporting also noted a distinction between Bitcoin mining and HashFlare’s other products. The July 20 action concerned active SHA-256 contracts, the category used for Bitcoin mining. Fortune reported on July 21 that HashFlare had not announced equivalent cancellations for contracts associated with other cryptocurrency networks.

Termination or suspension remained unclear

The surviving record contains a material conflict over what the July 20 action meant contractually. Contemporaneous reports described HashFlare as shutting its Bitcoin hardware and canceling or terminating the affected contracts. Customers consequently questioned whether prepaid contract value would be returned and whether balances remained withdrawable.

HashFlare later characterized the same action differently. In an official statement dated August 31, 2018, the company called it a temporary suspension, said all contracts had remained active and stated that SHA-256 service resumed on July 27 after an agreement with its hashrate suppliers.

That later explanation should not be projected into what customers knew on July 20. On the event date, the verified facts were that HashFlare had stopped servicing active SHA-256 contracts, attributed the decision to unprofitable mining and invoked its terms. Whether the contracts had been permanently ended or merely interrupted was not settled by the announcement record available to customers.

Why the halt mattered

The episode exposed a basic weakness in retail cloud mining: Bitcoin’s protocol could make network rewards publicly observable, but it could not verify a private provider’s equipment, operating costs, customer liabilities or internal payout ledger.

HashFlare’s claim that maintenance charges exceeded customer payouts for 28 days was a company assertion, not an independently audited calculation. No reliable event-day record establishes the amount of hashrate disabled, the number of affected contracts, customer losses or HashFlare’s share of the Bitcoin network. Those quantities should not be inferred from the absence of an obvious network-wide hashrate change.

Later context

A later FBI victim-information page alleged that HashFlare lacked access to the volume of mining power needed to service the contracts it sold and described the service as substantially terminated in July 2018. Those were later government allegations, unavailable on July 20, and they do not convert disputed event-day claims into facts known at the time. They do, however, explain why the July 20 interruption became important to the subsequent official record.