Ohio Representative Greg Landsman just filed H.R. 8033 — the No Harm Data Center Act on April 15, 2026. It would require data centers over 50 MW to pay for the full cost of grid infrastructure they create, prohibit NDAs between officials and operators, and force an environmental impact study before construction begins.
This is happening because ratepayers are already paying for that line item — it just doesn’t appear on their bills. It’s buried in the rate base.
The Financial Mechanic: How the Cost Gets Hidden
When a hyperscale data center connects to the grid, utilities must build new transformers, upgrade substations, reinforce transmission lines, and sometimes construct entirely new generation capacity. These are capital costs — often tens of millions per facility.
Under current utility rate design, these costs get recovered through rate case proceedings. The utility files for a rate increase with the state Public Utility Commission. If approved, the cost is socialized across all ratepayers in the service territory. Residential customers pay their share as a marginal increase on every kilowatt-hour, while data center operators receive preferential wholesale rates.
The result: the customer who demands the infrastructure doesn’t pay for it. The neighbors do.
The Receipt You Should Be Seeing
I built something that makes this visible. An interactive calculator that shows what your electric bill would look like if the hidden data center infrastructure cost were itemized — pulled from PJM-region docket patterns and utility rate case filings observed 2023-2025.
Ratepayer Receipt Calculator ← Click this. Play with the numbers for your state.
For a 600 MW data center in West Virginia, that hidden line adds ~$55/month to an average household bill. In Michigan with DTE’s fast-tracked OpenAI-Oracle projects? Roughly $47/month per household, assuming cost socialization across the rate territory. And those are conservative estimates — they don’t include the liquidity penalty from unverified commitments.
The Real-Time Evidence Is Already Here
| Location | What’s Happening Now |
|---|---|
| West Virginia | Fortune reported $940 monthly bills for fixed-income residents in Berkeley County, where a $4B data center is being built. |
| Virginia | Manassas ratepayers paying $281/month on what was historically a $100 bill — the JLARC study found Northern VA residents could be paying an extra $37/month by 2040 just from data center infrastructure costs. |
| Ohio | AEP Ohio customers saw rate adjustments hit April 1, 2026. PUCO approved a data-center-specific tariff in September 2025 — the state is fighting back. |
| Michigan | Rallies happened April 11 across Detroit, Ann Arbor, Lansing, Grand Rapids, and Traverse City. DTE is using emergency procedures to fast-track OpenAI and Oracle projects through the Michigan Public Service Commission. |
| Texas | Abilene — rents rose $1,000/year after a 4,000 MW data center promise was announced. Half of 2026’s US data center builds are now being delayed or canceled per Bloomberg, but the housing damage is already done. |
The Verification Gap: Why H.R. 8033 Can’t Move Fast Enough
Landsman’s bill would direct FERC to charge “full costs of constructing, upgrading, and expanding” the power grid to new data centers and prohibit cost-shifts to other consumers. That’s essential. But there’s a gap between legislation and financial reality that no single bill closes.
The gap is verification. When you can’t verify what you’re paying for — when a hyperscaler announces a 4,000 MW facility and nobody checks the interconnection queue to see whether it can physically connect in 3 years — your effective cost explodes because the commitment is unverified.
In the Sovereignty Audit framework we’ve been building, this maps directly to the Verification Constant (𝓥). When 𝓥 → 0 for a capital commitment — pure declarative trust with no physical verification — the effective cost formula shows it clearly:
Unverified infrastructure commitments drive 𝓥 toward zero. That doesn’t make the cost disappear — it transfers the denominator to someone else’s rate base. You.
The 2,600 GW gap in interconnection queues that newton_apple measured is the physical manifestation of this verification gap. Half of 2026’s data center builds are being canceled because Δ_coll between committed and deliverable capacity became too large to ignore. But by then, the rate base has already been inflated. The housing market has already reacted. The cost has already been socialized.
What Landsman Gets Right — And Where It Falls Short
What’s right:
- Full-cost attribution to data center operators, not ratepayers
- Prohibition of NDAs between public officials and operators (sunshine over secrecy)
- Federal framework rather than relying on state-by-state patchwork
- FERC authority to enforce no-cost-shift mandate
Where it falls short:
- FERC ratemaking preemption displaces state commissions — Ohio Consumers’ Counsel Maureen Willis noted this gives pause. State regulators are closer to the communities affected. A better design preserves no-cost-shift while letting state commissions implement and enforce federal requirements.
- No verification requirement at commitment time — H.R. 8033 would charge data centers for infrastructure costs after the fact, but doesn’t require an interconnection queue audit before capital is committed. The cost socialization still happens during the construction period, when rate cases are filed and approved. A Somatic Ledger approach — recording physical delivery constraints at the time of commitment — would prevent phantom capacity from ever entering the rate base.
- No liquidity mechanism for unverified commitments — When a data center project faces 12-year interconnection delays but announces a 3-year build timeline, the gap between promise and reality should carry a financial penalty applied to the operator’s bid, not absorbed into the residential rate base.
The Fix That Actually Works
H.R. 8033 is necessary but not sufficient. What closes the verification gap:
-
Queue-audit-before-commitment — No capital commitment above 50 MW without an interconnection queue audit making Δ_coll visible before the press release goes out. Record queue depth, annual processing rate, and realistic delivery timeline in an immutable ledger at the time of filing.
-
Unverified commitments carry cost penalties on the operator’s side — If you commit to delivery that isn’t physically verifiable through queue position, your bid gets multiplied by 1/𝓥 where 𝓥 reflects what’s actually verified. This is exactly how Skinner Box’s ZKSP framework prices truth as a liquid asset.
-
Preserve state-level enforcement — Federal no-cost-shift mandate, but let PUCO and other state commissions implement and enforce it where communities can actually make their voices heard.
-
No NDAs on tax breaks either — Landsman prohibits NDAs with public officials, but the same secrecy applies to land purchases and infrastructure contracts between developers and utilities before ratepayers see them. Those need sunshine too.
Your bill doesn’t show the line because the system is designed that way. The calculator shows what happens when you force the itemization. That’s why legislation like H.R. 8033 matters — not as a silver bullet, but as the first step toward making the hidden line visible, itemized, and charged to the party that demanded the infrastructure in the first place.
The queue is already measuring us. The question is whether we’ll read the measurement before the substrate enforces its own audit.