Mentioned in This Article
1. What happened to the Ratepayer Protection Act in the Senate?
The Ratepayer Protection Act failed a procedural vote in the U.S. Senate, receiving 57 votes in favor and 43 against, short of the 60 needed to advance. In an opinion column published on October 14, 2026, Rashan Colbert, director of U.S. policy and policy lead of the Digital Energy Council at the Crypto Council for Innovation (CCI), argues that the defeat does not end the question of who pays for the electricity infrastructure that large data centers require.
Colbert writes that the debate over the Ratepayer Protection Act is only beginning, and he expects a wider push to regulate the digital infrastructure and artificial intelligence stack through the end of this year and into the next Congress. The column is an opinion piece, and the views in it are the author's rather than those of the publication that carried it.
The vote matters beyond a single bill. Data centers, which host the computing behind AI services and digital asset networks, have become some of the largest new sources of electricity demand in the United States, and decisions about who covers the cost of serving them are now a live political issue.
Procedurally, a vote that falls short of 60 means the Senate could not end debate and move to a final decision. Because most legislation in the chamber needs that supermajority to proceed, a majority of 57 senators was not enough, even though more than half of the members supported advancing the bill.
2. What would the bill have done?
The legislation was sponsored by Senator Jon Husted, a Republican from Ohio, together with Representatives Gabe Evans, a Colorado Republican, and Kathy Castor, a Florida Democrat. Its stated aim is to protect households and small businesses from paying for infrastructure that large data centers need.
The mechanism is deliberately limited. State utility regulators and certain utilities would consider adopting standards that require facilities with a peak demand of at least 100 megawatts to cover the full incremental cost of new generation and grid upgrades attributable to them. The states would keep the authority to decide whether to adopt those standards at all.
To put the threshold in context, 100 megawatts is a large load by the standards of a local grid. A facility drawing that much power can require new power plants, new transmission lines or upgraded substations. Regulators have traditionally spread such costs across the customers of a utility, which is the outcome the bill's backers want to prevent when the driver of the spending is one large customer.
The House of Representatives passed the measure by a vote of 417 to 3, a margin that shows how little disagreement there is about the basic goal. The Senate debate has centered on a narrower question: whether it is enough to ask states merely to consider a cost-recovery standard, or whether a stronger federal requirement is needed.
The word incremental carries weight in this design. The standard would reach only the additional spending that a new large customer causes, such as a new generating unit or a transmission upgrade, rather than the existing system that all customers already share. Drawing that line in practice is a task for state regulators, who review utility filings and set the rates that households and businesses pay.
3. Why does this matter to digital asset companies?
Colbert notes that AI and digital asset networks both depend on electricity, equipment, land and connections to the grid. Public decisions about who bears costs and who absorbs impacts will influence where facilities are built and how quickly they can come online. A company's plans for computing capacity, he writes, depend on whether a utility can deliver power and whether the surrounding community supports the project.
For the Crypto Council for Innovation, those questions sit at the center of the policy environment for digital assets and the wider digital economy. Bitcoin mining operations and AI computing clusters are among the heavy electricity users that local regulators and residents increasingly scrutinize, and the same grid constraints apply to both.
The column frames the issue as a public concern that Congress cannot ignore: whether households and small businesses will pay for grid upgrades that large data centers require. Colbert says pressure to show how the country can build infrastructure while protecting the communities that host it will continue, whatever happens to this particular bill.
4. What principles does the author propose?
Colbert sets out a core principle: large new loads should bear the costs of serving them, and those costs and risks should be disclosed before projects go forward. He adds that utility agreements should address what happens if a customer scales back or leaves, since a data center that reduces its consumption could leave behind equipment that other customers would otherwise be asked to pay for.
He also argues that the public needs clarity. Families should be able to understand what the possible effects on their bills could be, and developers need clear expectations before they commit capital. Predictable rules, in his view, serve both groups, because uncertainty about cost allocation can slow projects as much as opposition can.
These ideas reflect a common regulatory approach in which large customers sign long-term contracts, often with minimum payments, so that the utility can finance new infrastructure without exposing other ratepayers if demand fails to materialize. Colbert's contribution is to tie that approach to disclosure and to community understanding.
Disclosure matters because the costs of a large connection are often uncertain when a project is first announced. If a developer, the utility and regulators publish the expected costs and the risks early, residents can weigh in before agreements are signed, and lenders can judge how much exposure a project really carries.
5. What is the Ratepayer Protection Pledge?
Colbert points to a voluntary commitment already in place. Earlier this year, the president and leaders of major technology companies agreed to the Ratepayer Protection Pledge. The companies named are Amazon, Google, Meta, Microsoft, OpenAI, Oracle and xAI, and they committed to covering the costs of new generation needed for their data centers.
In July, the White House announced an expansion of the pledge that added more than 200 utilities, data center developers, cooperatives and states. Colbert says Congress now has to work out how public policy should give those commitments legal effect, since a pledge is a statement of intent and does not carry the force of a statute.
That gap is the heart of the argument. Voluntary commitments can be broken or reinterpreted, and they do not bind companies that never signed. Legislation, or state regulatory standards, would extend the same expectation to every large load.
The inclusion of states and cooperatives in the expanded pledge is notable because electricity regulation in the United States is shared between federal and state authorities. Most decisions about retail rates are made at the state level, so any national approach has to work with that structure rather than replace it, which is why the bill leaves the final adoption choice to the states.
6. Why is cost allocation not enough?
The column cautions that assigning cost responsibility does not solve the underlying supply problem. The United States needs substantially more power and infrastructure, Colbert writes, and faster development of generation, transmission, storage and equipment can relieve constraints that cost rules alone cannot fix. Allocation settles who pays but does nothing about permitting, equipment procurement or construction timelines.
He argues that policy should make that process more predictable while preserving protections for communities and the environment. A rule that places costs on large users but leaves approvals slow could discourage investment without delivering any more electricity.
Rules also need to reflect how projects work in practice. A proposed campus has to resolve utility service and local approvals long before its first server is switched on, and policymakers need to understand those dependencies. Colbert notes that utilities, regulators, developers and computing companies each hold a piece of that knowledge, and that communities should have the chance to ask questions while decisions on location and infrastructure can still change.
Colbert's point is that a bill dealing only with payment, however well designed, is one part of a larger puzzle. A community that is asked to host a facility will want to know who pays, and also whether the power supply is secure, whether the local environment is protected and whether the project will actually be built and operated as described.
7. What comes next in Congress?
The ratepayer debate, Colbert writes, is an early example of choices that Congress and the states will face across the whole stack: energy, data centers, chips, servers and frontier AI models. Each layer raises different questions. A rule on model safety and a utility tariff serve different purposes, while limits on infrastructure affect everything built on top of it.
He expects the debates to sharpen as lawmakers respond to constituents and as leadership sets the agenda for the next Congress. The challenge, he argues, is to understand how individual decisions fit together: energy policy affects the availability of computing power, the siting of data centers affects the flow of investment, and the effects reach digital assets, AI and related services.
The Digital Energy Council, a coalition within the Crypto Council for Innovation that brings together companies from connected sectors, lists its priorities as expanding U.S. energy capacity, strengthening grid reliability and clarifying the practical path from a proposed facility to an operating one. Colbert describes building digital economy capacity responsibly, with transparent costs and community confidence, as a national imperative.