CleanSpark produces 593 BTC in August; secures Texas ERCOT status
- CleanSpark produced 593 BTC in August, ending with 13,703 BTC holdings
- Sandersville campus construction continues with $6.6 billion in contracted revenue
- ERCOT granted conditional batch zero classification for 885 MW in Texas
- Company sold 744 BTC via spot, calls, and basis trades at avg $65,420

*this image is generated using AI for illustrative purposes only.
CleanSpark Inc (Nasdaq: CLSK) produced 593 bitcoins in August 2026, maintaining a treasury balance of 13,703 BTC as of month-end. The data center developer also reported progress on its Sandersville campus, which carries $6.6 billion in contracted revenue, and received conditional batch zero classification from ERCOT for its Texas sites.
The company’s average daily production stood at 19.12 BTC, with a peak single-day output of 20.40 BTC. Year-to-date production for CY2026 reached 4,903 bitcoins. The operational hashrate of 50 EH/s exceeded the average operating hashrate of 38.3 EH/s, indicating periods of higher utilization within the month.
Fleet and Power Metrics
CleanSpark’s deployed fleet achieved a peak efficiency of 16.07 J/Th. The company utilized 808 MW of power from its contracted portfolio, which totals 1.8 GW under contract. This utilization level suggests significant capacity remains available for future expansion or increased load management.
| Metric | Value |
|---|---|
| Bitcoin produced | 593 |
| Operational Hashrate | 50 EH/s |
| Average operating hashrate | 38.3 EH/s |
| Deployed fleet | 201,269 |
| Utilized MW | 808 MW |
| GW under contract | 1.8 GW |
Treasury Activity
CleanSpark reduced its bitcoin holdings by 228 BTC during August, moving from 13,931 BTC on July 31 to 13,703 BTC on August 31. The reduction stemmed from multiple sale activities rather than pure spot market liquidations.
The company sold 77 BTC at spot prices. Additionally, it disposed of 500 BTC pursuant to call exercises and 244 BTC related to delta neutral basis trades. The average price per bitcoin sold across all transactions was $65,420. As of August 31, 3,951 BTC of the total holdings were posted as collateral or receivable related to derivative transactions.
| Activity | BTC Volume |
|---|---|
| Holdings as of July 31 | 13,931 |
| Bitcoin produced | 593 |
| Sold at spot | (77) |
| Sold via call exercises | (500) |
| Sold via basis trade | (244) |
| Holdings as of August 31 | 13,703 |
Infrastructure and Regulatory Updates
Construction is ongoing at the Sandersville campus, supported by $6.6 billion in contracted revenue from a high-investment grade tenant. In Texas, CleanSpark received notice of conditional classification by ERCOT for both its sites. This includes 585 MW of contracted capacity designated for batch zero baseload and 300 MW for batch zero studied load. CEO Matt Schultz stated the company remains fully committed to satisfying Governor Abbott’s audit directive with both ERCOT and the PUCT.
What the Numbers Show
The divergence between production and net treasury change highlights CleanSpark’s active hedging strategy. While the company mined 593 BTC, it reduced its holdings by only 228 BTC, meaning 365 BTC of new production was effectively offset by sales. The fact that 744 BTC were sold in total (spot, calls, and basis trades) against a production of 593 BTC reveals that the company is also drawing down existing reserves to meet these obligations, rather than solely monetizing current output. Additionally, with 3,951 BTC held as collateral, nearly 29% of the total treasury is encumbered by derivative positions, linking treasury liquidity directly to derivatives exposure.
How might CleanSpark's significant drawdown of existing reserves to meet derivative obligations impact its long-term treasury strategy and financial flexibility?
What are the potential risks associated with nearly 29% of CleanSpark's Bitcoin treasury being encumbered as collateral for derivative positions?
Could the conditional ERCOT classification for Texas sites lead to operational delays or additional compliance costs before full baseload capacity is achieved?

































