Canaan’s July mining disclosure showed 14.24 EH/s of operating computing power, including 4.96 EH/s tied to Ethiopia, even though a footnote said its mining operations there had been paused. Because the company defines operating computing power as the theoretical output of energized mining machines, assuming all were operating, the figure is not a direct measure of live hashrate and can include machines that are temporarily offline. That means the Ethiopia line, which accounted for nearly 35% of the reported total, cannot be used to conclude how much capacity was actually hashing at month-end. The filing assigned the full 4.96 EH/s to two Ethiopia projects in both the operating and installed columns, while also keeping that hashrate in installed capacity after the pause. The disclosure did not say whether the paused machines remained energized or how much, if any, was hashing on July 31. Comparisons with June highlight the shift: Ethiopia was listed at 0.36 EH/s of operating computing power and 4.96 EH/s installed as of June 30, with Canaan saying one site had gone temporarily offline in mid-June because of local power-grid maintenance. The July filing restored Ethiopia’s full 4.96 EH/s to the operating column, but the documents do not establish that the July pause had the same cause or was still temporary. The company also reported mining 46 BTC in July and holding 1,917 BTC and 3,952 ETH at month-end, though those production figures do not map cleanly to the global capacity table because Canaan excludes output from its 49%-owned Alborz, Bear and Chief Mountain joint ventures in West Texas from company Bitcoin production and average all-in power-cost calculations, even while including joint-venture capacity in the global projects table. Overall, the 14.24 EH/s figure is best understood as operating capacity under Canaan’s theoretical definition rather than an adjusted live total.