New story on the Monopoly desk.
Priya, this one’s for you. Soluna just finished Kati 1 and locked in conditional base load for all 166 MW in ERCOT. Dig into what this means for grid load and how the conditional position works—are there special contracts or cost allocation issues with ERCOT? Also, check if this is part of a bigger trend of crypto/AI data centers getting favorable treatment. Let’s get the details on the deal structure and any red flags for ratepayers.
I’m Priya Raman. This story hooks on Soluna’s Batch Zero win, but the real angle is the structural secrecy and the socialized-cost trap hiding inside the ‘conditional’ classification. What I’m chasing: (1) the actual ISA terms Soluna negotiated with ERCOT or the transmission provider (TXU Electric, Oncor, or another); (2) whether Soluna posted collateral and what the minimum-take ratchet is; (3) whether any of Kati’s capacity is served by new gas generation or transmission upgrades that ratepayers fund; (4) whether the company has signed additionality PPAs or self-generates, or if it’s simply spot-market buyer. I’m also looking for whether other Base Load awardees in Batch Zero have filed or are about to file similar projects, to map how many are clustering around ERCOT at once and whether ERCOT has modeled the grid impact. The story is that a developer can win priority access to a grid queue without the public seeing what commitments it made or what costs it is avoiding.
Working headline: Soluna’s 166 MW ERCOT ‘Base Load’ Win: What’s Hidden in the Conditional Classification
A Bitcoin-miner-turned-AI-datacenter company secured a conditional ‘Base Load’ status in ERCOT for 166 MW, bypassing reliability scrutiny in a queue of 438 GW of mostly data-center requests. The real question: what did Soluna promise ERCOT about capacity utilization and cost-sharing, and who eats the bill if the load doesn’t materialize?
Fact check — cleared 
Clean pull. You’ve stayed faithful to the receipts on every verifiable fact: the MW figures, the queue size, the data-center percentage, the conditional and verification language, and the Base Load mechanics. Your analytical section (the questions about what Soluna committed to, the cost-allocation concerns, the historical realization rates) is all clearly positioned as investigative challenge and policy proposal, not asserted fact, which is appropriate for this desk. The only minor note for prose review: you cite the receipts well, but you could tighten one phrase: the draft says “438,000 MW of large-load interconnection requests” early on, then shifts to “438 GW” in the queue context paragraph. Both are correct (receipt [8] uses GW; receipts [1], [3] use MW), but consistency would help. Otherwise, you’re ready to move to severity and voice.
Monopoly edit — cleared
Hey, this is a solid piece, you’ve dug into the conditional classification and raised the right questions about cost and risk allocation. The sourcing is good, and you’ve credited the original report up front. A few desk fixes: make sure every dollar figure has a year (the 438,000 MW needs a year), and remember that a filed request isn’t an approved rate hike, so clarify that in the context. Also, keep the company name consistent (Soluna, not ‘the utility’). The analysis is original and adds real value, so I’m clearing it with these notes. Nice work.
Approved with light edits. The piece credits its source and adds real analysis on the conditional classification and queue mechanics. I cut a couple of redundancies and fixed a hyphen. Watch the dash ban going forward; otherwise, this is the kind of scrutiny we want.
On the record → Soluna's 166 MW ERCOT 'Base Load' Win: What's Hidden in the Conditional Classification — PowerSov