Even with Gunfire Behind Bars, Why Do American Small Towns Oppose AI Data Centers?
On April 7, voters in Festus, Missouri, recalled four of eight city council members over the approval of a $6 billion AI data center project at the end of March. The project, led by Clayco's data center development arm CRG, spans 360 acres and has an undisclosed Fortune 100 end user (codenamed Project Cumulus).
The city council signed off on the project without a public hearing, leading local residents' group Wake Up JeffCo to sue the city government and CRG in St. Louis County court, with a recall petition against the mayor underway. According to Tom's Hardware, around the same time, Indianapolis councilman Ron Gibson's home was shot at multiple times late in 2025, with a "No Data Centers" note left at his doorstep.
Festus is not alone. Recently, Indianapolis councilman Ron Gibson's home was sprayed with 13 bullets in the dead of night, waking his 8-year-old son. A handwritten note at the door read, "No data center allowed." The FBI is investigating. Jordyn Abrams, a researcher at George Washington University's extremism program, points out that data centers are becoming targets for anti-tech, anti-government extremists.

Ron Gibson shooting scene
The advocacy group Data Center Watch, in its Q2 2025 report, has updated the number of organized opposition groups from 142 a year ago (in 24 states) to 188 (across 40 states). The value of halted or delayed projects has risen from $64 billion to $162 billion. On April 1, 2026, Port Washington, Wisconsin, passed the first-ever nationwide referendum explicitly targeting a data center, with 66% of voters in favor of adding a mandatory referendum threshold for projects receiving over $10 million in TIF subsidies.
All these events collectively answer the same question: Will the true bottleneck of AI capacity expansion be at the county and city ballot boxes?
Backlash in Full Swing
Plotting the events of the past 23 months on a map of the United States, two tiers of backlash are apparent. One is at the state level, with eight states having submitted or passed data center pause bills, including Maine (passed 82-62 in the House, extending to 2027), Vermont (paused until July 2030), Virginia (introduced by Democratic Delegate Irene Shin, paused until 2028), Georgia, Maryland, South Dakota, Wisconsin, and Minnesota. This tier represents legislative action, with the broadest impact but slowest progress.

Another type is at the municipal or county level, with a more intense and vigorous backlash. The Chandler City Council in Arizona unanimously rejected Active Infrastructure's $2.5 billion project in December 2025 (lobbied by former U.S. Senator Kyrsten Sinema). The Tucson City Council in the same state is currently reviewing data center zoning restriction regulations, with public feedback open until the end of April 2026. Hays County/San Marcos in Texas rejected a $1.5 billion project in a 5-2 vote. Other locations include Cascade Locks in Oregon, Chesterton in Indiana, Catlett Station in Virginia, Peculiar in Missouri, and Lansing in Michigan. According to Data Center Watch, at least 10 states have seen direct rejections at the city government level or developers withdrawing their plans.
Over half of the high-conflict incidents are concentrated in the Midwest and South Central regions. This area has been a hotspot for data center siting due to the relative grid capacity surplus over the past decade. Now, the backlash is concentrated in the same region. From another perspective, the suppliers are moving from the "power plant surplus states" and encountering the most politically sensitive layer of local politics.
$60 Billion — Not in the Same League
The financial scale of Festus makes the $60 billion figure impossible for the city council to digest normally. According to local newspaper myleaderpaper citing municipal budget documents, Festus's FY2025 general fund plus public safety operational budget is $17.64 million, total municipal expenses in FY2024 were $37.41 million, and an estimated year-end reserve of $28.09 million for FY2025.
The $60 billion data center project is around 340 times the annual operating budget, equivalent to $450,000 per resident in a city with 13,200 residents. In relative terms, this is not a local development project up for discussion but rather a small town being plugged into a capital pipeline completely unrelated to itself.

Contrasting this with Festus residents' median per capita income of approximately $35,000 in non-metro Missouri sheds light on the issue. Any decimal in the data center contract is greater than the entire community's lifetime disposable income per capita. Local officials lack the experience to balance such numbers. The criticism of the Festus City Council resolution being dubbed "not open for public hearing" is technically due to the fact that such projects typically involve commercial confidentiality clauses (with neither the developer nor end customer identities disclosed), rendering normal city council procedures unable to review confidential contracts. This is a structural flaw, not an oversight by individual council members.
Due to the difference in scale, splitting a data center contract into a size that can be handled by a local council is inherently unfeasible. That's why in the past 12 months, the rebound path has not been resolved within the legislative process but through the use of three external weapons: recalls, lawsuits, and referendums. In a rare case, Festus saw its four city council members recalled, a lawsuit filed by a residents' group in St. Louis County Circuit Court, and the initiation of a mayor recall petition, with all three paths triggered simultaneously.
A Data Center Consuming a Small Town
The power usage of an AI data center is best understood by comparing it to a small town in the United States. A fully loaded 200 MW AI data center, with an 86% load factor, consumes about 1,500 GWh annually. In comparison, a small U.S. town of 100,000 residents consumes approximately 420 GWh per year (based on the U.S. Energy Information Administration's EIA average annual residential electricity consumption of 10.5 MWh per household, assuming 2.5 people per household). The data center consumes electricity 3.6 times that of the town's residents. And this is only for electricity, not accounting for cooling and associated water usage.
Water usage, on the other hand, presents a more intuitive comparison. Based on the U.S. Geological Survey's typical residential water use (100 gallons per person per day), a town of 100,000 residents consumes around 36.5 billion gallons of water per year. In contrast, a hyperscale AI data center such as Google's Council Bluffs (the largest Google data center in the U.S.) consumes 500 million gallons of water per year. In absolute terms, the data center's water consumption is 13.7% of the town's usage. However, in a different perspective, it is equivalent to the water consumption of 14,000 people for a whole year. In a small town with a population of 10,000 to 50,000, this means allocating a significant portion of the city's water supply system to a single user. According to Lawrence Berkeley Lab's 2024 Data Center Energy Report, U.S. data centers consumed 17 billion gallons of water directly for cooling in 2023 and 211 billion gallons of water indirectly (for power generation). Direct water usage is expected to double or even quadruple by 2028.

The most commonly heard protest slogan is "our well will run dry." Looking at the numbers, this is not an emotional expression. In 2023, Loudoun County in Virginia (the county with the most concentrated data centers in the U.S.) had a potential water usage of 8.99 billion gallons by data centers, accounting for around 10% of the county's total water usage, according to local water supply data cited by Sierra Club and Grist. If at the county level it's already significant, the numbers at the town level would be even more extreme.
Planned Capacity in Development, Entering Rebound Window
The true capacity of U.S. data centers that have actually been commissioned is approximately 50 GW, according to FERC and Wood Mackenzie 2025 Q4 data. The planned pipeline totals 241 GW, with 33% in active development (around 80 GW) and another 67% (around 161 GW) yet to be initiated. BloombergNEF predicts an additional 97 GW of capacity to be added in the U.S. from 2025 to 2030, with the data center electricity demand peaking at 106 GW by 2035. All these numbers point to one fact: the vast majority of the capacity is still on the drawing board and not yet implemented.

According to data revealed by Sightline Climate via TechRadar, of the 16 GW originally scheduled to come online in 2026, 30% to 50% are expected to be canceled or delayed. Meanwhile, Data Center Watch's data shows that from May 2024 to March 2025, over 10 months, $64 billion worth of data center projects were stopped or delayed due to organized opposition. In the single quarter of 2025 Q2, this figure was $98 billion corresponding to 20 projects. The amount blocked in a single quarter has exceeded the cumulative total of the previous 10 months.
This sets up a timing mismatch. Capital has already committed to doubling U.S. data center capacity over the next five years, but the new capacity has to navigate through each level of county and city approvals. The more planned capacity there is, the larger the surface area that can be held back by rebound. Cases like Festus were able to escalate from a city council vote to recall and lawsuits within a month not because it was unique but because the number of opposition organizations increased by 46 in a year (according to the Data Center Watch 2025 Q2 report) and shared templated legal tools across states, including TIF subsidy referendums, zoning litigation, and legislator recalls. Whether a long-term power agreement signed by a cutting-edge lab will materialize depends on which counties these contracts land in and which residents are watching those county councils.
The bottleneck in AI capacity expansion, stepping out of power contract negotiation for the first time, appeared on the recall vote cast by 13,200 people.
You may also like

Hyperliquid Ten Thousand Character Feature: Jeffrey's Billion Dollar Gold Mining Story

SaaS Churn | Rewire Daily News

There may not be a rate cut this year

CoinGecko Spot Report: Overview of 12 Major CEX Spot Markets, Only 32% of New Tokens Outperforming IEO Price

The Sky is the Limit: Wearing Only One Outfit, Cutting My Own Hair, and Giving Billions to Strangers — The Story Behind Hyperliquid

Atlético Madrid vs FC Barcelona: 90 Minutes to Destroy a Dream or Write History
Atlético Madrid vs FC Barcelona Champions League second leg is do-or-die. Full Atlético Madrid vs FC Barcelona lineups, stats, timeline — plus who chokes and who conquers.

Chinese-funded institutions retreat from Hong Kong stablecoins

Morning Report | Strategy invested $1 billion to increase its Bitcoin holdings last week; Aave passed a $25 million grant proposal; Coinone was shut down and fined for violating anti-money laundering obligations

Found a "meme coin" that skyrocketed in just a few days. Any tips?

TAO is Elon Musk, who invested in OpenAI, and Subnet is Sam Altman

The era of "mass coin distribution" on public chains comes to an end

Soaring 50 times, with an FDV exceeding 10 billion USD, why RaveDAO?

1 billion DOTs were minted out of thin air, but the hacker only made 230,000 dollars

After the blockade of the Strait of Hormuz, when will the war end?

Before using Musk's "Western WeChat" X Chat, you need to understand these three questions
The X Chat will be available for download on the App Store this Friday. The media has already covered the feature list, including self-destructing messages, screenshot prevention, 481-person group chats, Grok integration, and registration without a phone number, positioning it as the "Western WeChat." However, there are three questions that have hardly been addressed in any reports.
There is a sentence on X's official help page that is still hanging there: "If malicious insiders or X itself cause encrypted conversations to be exposed through legal processes, both the sender and receiver will be completely unaware."
No. The difference lies in where the keys are stored.
In Signal's end-to-end encryption, the keys never leave your device. X, the court, or any external party does not hold your keys. Signal's servers have nothing to decrypt your messages; even if they were subpoenaed, they could only provide registration timestamps and last connection times, as evidenced by past subpoena records.
X Chat uses the Juicebox protocol. This solution divides the key into three parts, each stored on three servers operated by X. When recovering the key with a PIN code, the system retrieves these three shards from X's servers and recombines them. No matter how complex the PIN code is, X is the actual custodian of the key, not the user.
This is the technical background of the "help page sentence": because the key is on X's servers, X has the ability to respond to legal processes without the user's knowledge. Signal does not have this capability, not because of policy, but because it simply does not have the key.
The following illustration compares the security mechanisms of Signal, WhatsApp, Telegram, and X Chat along six dimensions. X Chat is the only one of the four where the platform holds the key and the only one without Forward Secrecy.
The significance of Forward Secrecy is that even if a key is compromised at a certain point in time, historical messages cannot be decrypted because each message has a unique key. Signal's Double Ratchet protocol automatically updates the key after each message, a mechanism lacking in X Chat.
After analyzing the X Chat architecture in June 2025, Johns Hopkins University cryptology professor Matthew Green commented, "If we judge XChat as an end-to-end encryption scheme, this seems like a pretty game-over type of vulnerability." He later added, "I would not trust this any more than I trust current unencrypted DMs."
From a September 2025 TechCrunch report to being live in April 2026, this architecture saw no changes.
In a February 9, 2026 tweet, Musk pledged to undergo rigorous security tests of X Chat before its launch on X Chat and to open source all the code.
As of the April 17 launch date, no independent third-party audit has been completed, there is no official code repository on GitHub, the App Store's privacy label reveals X Chat collects five or more categories of data including location, contact info, and search history, directly contradicting the marketing claim of "No Ads, No Trackers."
Not continuous monitoring, but a clear access point.
For every message on X Chat, users can long-press and select "Ask Grok." When this button is clicked, the message is delivered to Grok in plaintext, transitioning from encrypted to unencrypted at this stage.
This design is not a vulnerability but a feature. However, X Chat's privacy policy does not state whether this plaintext data will be used for Grok's model training or if Grok will store this conversation content. By actively clicking "Ask Grok," users are voluntarily removing the encryption protection of that message.
There is also a structural issue: How quickly will this button shift from an "optional feature" to a "default habit"? The higher the quality of Grok's replies, the more frequently users will rely on it, leading to an increase in the proportion of messages flowing out of encryption protection. The actual encryption strength of X Chat, in the long run, depends not only on the design of the Juicebox protocol but also on the frequency of user clicks on "Ask Grok."
X Chat's initial release only supports iOS, with the Android version simply stating "coming soon" without a timeline.
In the global smartphone market, Android holds about 73%, while iOS holds about 27% (IDC/Statista, 2025). Of WhatsApp's 3.14 billion monthly active users, 73% are on Android (according to Demand Sage). In India, WhatsApp covers 854 million users, with over 95% Android penetration. In Brazil, there are 148 million users, with 81% on Android, and in Indonesia, there are 112 million users, with 87% on Android.
WhatsApp's dominance in the global communication market is built on Android. Signal, with a monthly active user base of around 85 million, also relies mainly on privacy-conscious users in Android-dominant countries.
X Chat circumvented this battlefield, with two possible interpretations. One is technical debt; X Chat is built with Rust, and achieving cross-platform support is not easy, so prioritizing iOS may be an engineering constraint. The other is a strategic choice; with iOS holding a market share of nearly 55% in the U.S., X's core user base being in the U.S., prioritizing iOS means focusing on their core user base rather than engaging in direct competition with Android-dominated emerging markets and WhatsApp.
These two interpretations are not mutually exclusive, leading to the same result: X Chat's debut saw it willingly forfeit 73% of the global smartphone user base.
This matter has been described by some: X Chat, along with X Money and Grok, forms a trifecta creating a closed-loop data system parallel to the existing infrastructure, similar in concept to the WeChat ecosystem. This assessment is not new, but with X Chat's launch, it's worth revisiting the schematic.
X Chat generates communication metadata, including information on who is talking to whom, for how long, and how frequently. This data flows into X's identity system. Part of the message content goes through the Ask Grok feature and enters Grok's processing chain. Financial transactions are handled by X Money: external public testing was completed in March, opening to the public in April, enabling fiat peer-to-peer transfers via Visa Direct. A senior Fireblocks executive confirmed plans for cryptocurrency payments to go live by the end of the year, holding money transmitter licenses in over 40 U.S. states currently.
Every WeChat feature operates within China's regulatory framework. Musk's system operates within Western regulatory frameworks, but he also serves as the head of the Department of Government Efficiency (DOGE). This is not a WeChat replica; it is a reenactment of the same logic under different political conditions.
The difference is that WeChat has never explicitly claimed to be "end-to-end encrypted" on its main interface, whereas X Chat does. "End-to-end encryption" in user perception means that no one, not even the platform, can see your messages. X Chat's architectural design does not meet this user expectation, but it uses this term.
X Chat consolidates the three data lines of "who this person is, who they are talking to, and where their money comes from and goes to" in one company's hands.
The help page sentence has never been just technical instructions.

Parse Noise's newly launched Beta version, how to "on-chain" this heat?

Is Lobster a Thing of the Past? Unpacking the Hermes Agent Tools that Supercharge Your Throughput to 100x

Declare War on AI? The Doomsday Narrative Behind Ultraman's Residence in Flames
Hyperliquid Ten Thousand Character Feature: Jeffrey's Billion Dollar Gold Mining Story
SaaS Churn | Rewire Daily News
There may not be a rate cut this year
CoinGecko Spot Report: Overview of 12 Major CEX Spot Markets, Only 32% of New Tokens Outperforming IEO Price
The Sky is the Limit: Wearing Only One Outfit, Cutting My Own Hair, and Giving Billions to Strangers — The Story Behind Hyperliquid
Atlético Madrid vs FC Barcelona: 90 Minutes to Destroy a Dream or Write History
Atlético Madrid vs FC Barcelona Champions League second leg is do-or-die. Full Atlético Madrid vs FC Barcelona lineups, stats, timeline — plus who chokes and who conquers.
