BitFuFu reported mining 167 BTC in September, down 4% from August. Lower cloud-mining output more than offset a gain in self-mining. Its disclosure also details the unresolved risks surrounding a proposed Ethiopian acquisition. Comparable September figures attributed to CleanSpark and Canaan could not be confirmed against primary disclosures.
- BitFuFu reported mining 167 BTC and holding 1, 388 BTC at month-end.
- Self-mining increased, but cloud-mining output fell by more.
- A supplier threatened to enforce claimed security rights over assets at the proposed Ethiopian site.
- CleanSpark and Canaan figures remain unconfirmed here.
BitFuFu’s mining mix shifts
In its October 13 operating update, BitFuFu reported producing 167 BTC in September, compared with 174 BTC in August, a 4% month-over-month decline. Average daily output stayed at 5.6 BTC. The company said its operating figures were unaudited.
The shift in production mix explains the decline. Self-mining generated 98 BTC, up from 88 BTC in August. Cloud mining produced 69 BTC, down from 86 BTC. The 10 BTC increase in self-mining did not make up for the 17 BTC drop in cloud-mining output.
BitFuFu reported holding 1, 388 BTC at the end of September, up from 1, 373 BTC in August. Production measures how much Bitcoin was mined during a period. A treasury balance measures holdings at a specific point in time. The company did not provide a full reconciliation of the 15 BTC increase.
Other operating figures point to a smaller managed footprint. Total hashrate under management fell to 19.4 exahashes per second (EH/s) from 20.6 EH/s, while power capacity under management dropped to 324 megawatts from 344 MW. Self-owned hashrate remained at 3.8 EH/s. The reported reduction came from third-party suppliers and hosting customers. Average fleet efficiency held at 16.7 joules per terahash.
The release does not explain what drove the capacity changes or whether they were linked to the Ethiopian dispute. It also offers no detail on the contracts behind its cloud-mining category, so the figures should not be read as output solely from machines BitFuFu owns and operates.
The Ethiopian acquisition remains unresolved
BitFuFu’s proposed acquisition of a majority stake in a business that operates an 80 MW mining facility in Ethiopia had not closed as of the October 13 disclosure. The company said required conditions remained unsatisfied or unwaived.
BitFuFu reported paying the sellers US$4.1 million and deploying about 13, 700 Bitmain Antminer S19-series machines at the site. It said the machines represented about 1.57 EH/s and had a net book value of US$1.74 million as of September 30.
According to BitFuFu, the dispute is between the target company and its electricity supplier, not directly between BitFuFu and the supplier. On September 28, the supplier issued a notice threatening to exercise security rights over collateralized equipment and other assets unless it received a disputed payment within 10 days.
The notice was a threat to enforce claimed rights. It does not show that the supplier seized the machines or that its claim was tested or upheld. BitFuFu said that, to the best of its knowledge, the target had not paid the disputed amount as of the October 13 disclosure. The company did not identify the amount or report the dispute’s outcome. The 10-day period had passed by the time of the disclosure, but the release did not say whether the supplier had acted.
BitFuFu said it was considering ending the deal, pursuing arbitration, recovering payments and retrieving its machines. These were options under consideration, not completed actions. The company acknowledged a material risk that the acquisition might not close on the contemplated terms, within the anticipated timeframe or at all.
BitFuFu also said it expected the incremental impact to be minimal and that it could reallocate resources. That is management’s assessment, not an independently established outcome. The deal remains exposed to an unresolved power-supply dispute, and the release does not explain how the supplier’s claimed rights could affect BitFuFu’s machines.
CleanSpark and Canaan: figures need primary-source confirmation
September figures attributed to CleanSpark put production at 529 BTC, down from 593 BTC in August. Its month-end Bitcoin holdings reportedly stood at 13, 530 BTC, compared with 13, 703 BTC a month earlier. The same account says the company sold 2 BTC on spot markets and delivered another 700 BTC through call-option exercises, at an average price of $72, 928 per Bitcoin for those transactions.
CleanSpark’s primary disclosures did not confirm those figures or transaction details. The difference between spot sales and option-related deliveries matters. The available information does not explain the contracts’ terms or establish that all 700 BTC were physically delivered. The arithmetic is correct: 702 BTC sold or delivered minus 529 BTC mined equals 173 BTC, the reported treasury decline. But that is only a partial reconciliation. It does not show that no other transfers or accounting items affected the balance.
CleanSpark’s reported shift from monthly to quarterly mining updates, along with details of its Georgia data-center lease and financing, also needs confirmation against company filings or releases. The available accounts give two different financing figures: a $2.227 billion proposal and a $2.276 billion completed offering. They do not explain why the figures differ or whether the proposed terms remained unchanged at closing. There is not enough verified information to resolve that discrepancy responsibly.
Figures attributed to Canaan put September production at 44 BTC, matching August, and its treasury at 1, 875 BTC, up from 1, 868 BTC. Canaan was also reported to have brought an 8 MW Nordic district-heating project online and converted cryptocurrency into cash for share repurchases. These operational and treasury claims could not be confirmed against the company’s October 15 release, so they should not be treated as established results here. September Bitcoin production figures from another miner are another reminder to check each company’s results against its own disclosures.
Company disclosures are primary sources for management’s reports, not independent audits. BitFuFu’s release supports its statements about September operations and the Ethiopian deal, but labels its operating metrics unaudited. CleanSpark’s and Canaan’s reported figures also need to be checked against their own disclosures before they can support a reliable comparison.
Key questions and answers
-
How much Bitcoin did BitFuFu report mining in September?
It reported 167 BTC, down from 174 BTC in August. Self-mining rose to 98 BTC, while cloud-mining output fell to 69 BTC.
-
Did the Ethiopian supplier take BitFuFu’s machines?
BitFuFu reported receiving notice that the supplier might enforce claimed security rights over collateralized assets, but did not say the supplier had taken possession. Its October 13 disclosure did not state the dispute’s outcome.
-
Could BitFuFu’s Ethiopian acquisition fail to close?
Yes. BitFuFu said required conditions remained unsatisfied or unwaived and disclosed a material risk that the deal might not close. The company was considering termination, arbitration, payment recovery and the return of its machines.
-
Which figures were checked against primary disclosures?
BitFuFu’s September operating and acquisition figures are supported by its October 13 company release, which labels the operating metrics unaudited. The CleanSpark and Canaan figures discussed here could not be confirmed against their primary releases. None of the figures should be described as independently audited.
