Bitmain in the Customer's Seat: The New Hosting Fights

What Happened

Most people know Bitmain as the company that makes Antminers. Less familiar is Bitmain as a hosting customer in the United States, with its own machines placed at third party sites. Court fights in 2025 and 2026 made that footprint public, and they touch many of the issues that come up in disputes between hosts and fleet owners.

In a Texas bankruptcy case, Bitmain said it had about 2,700 Antminers worth roughly $5.5 million at a host called Orb Energy. In its filing, Bitmain alleged that the host diverted more than 99 bitcoin in mining rewards and damaged hardware with unauthorized software and firmware, and it moved to pull its machines out of the bankruptcy. These are allegations made in a court filing, and the sources cited here do not report a ruling on them.

In a separate arbitration, Data Center Dynamics reported that Bitmain won $4.5 million in a dispute with a host over early termination of a 6,400 machine contract in Mississippi. Meanwhile an Iowa company sued Bitmain going the other direction, alleging quality problems with 5,000 refurbished rigs, and another dispute in Tennessee involves more than 7,000 S21 machines.

Why I Follow This Story

I follow these cases because they put the manufacturer on the customer side of a hosting relationship. Bitmain wrote the warranty terms that apply to its machines, including a provision that unauthorized firmware voids coverage. In the Orb Energy filing, Bitmain alleged that a host loaded unauthorized firmware onto its machines and damaged them. That places a familiar warranty question inside a hosting dispute, with the machine maker as the complaining party.

The reward diversion allegation touches a question that also came up in the Block Mining halving case: who controls the pool settings and payout addresses on hosted machines. Pool configuration determines where mining rewards are paid, which is why access to those settings is often a focus in hosting disputes.

Issues This Case Raises

• Firmware authority. Hosting agreements vary on who may install firmware on customer machines and what permission is required. Bitmain's filing treats unauthorized firmware as damage. Some hosts take the position that firmware changes improve performance or were made with customer approval. I describe the tradeoffs in Third Party Firmware: The Good, the Bad, and the Voided Warranty.
• What refurbished means. The Iowa suit turns on the definition. Some purchase agreements include acceptance testing, such as running machines at rated hashrate for a defined burn in period before payment is final, while others rely on a general description. Buyers and sellers can read a general description very differently.
• Visibility into pool settings. Some hosting arrangements give owners direct visibility into which pool and payout address each machine uses; others keep that access with the host for operational reasons. What the contract provided, and what each side could see, can become central facts in a reward diversion claim.
• Early termination. The reported Mississippi award shows that early termination terms can carry real money. Hosts point to the cost of building and energizing capacity, and customers point to their need for flexibility. How a contract prices that tradeoff varies.

Questions about whether firmware affected a machine, whether refurbished units met a specification, or where mined coins went are usually examined through logs, pool records, and hardware diagnostics. Those topics are covered on the ASIC hosting expert witness page.