A data center project close to home raises concrete worries for neighbours. Opponents' most common words were water, resources, and environment (UVA NSI). When developers acknowledge that residents bear the physical burdens of compute infrastructure, they can reach those residents directly through a one-time cash payment. Residents then receive direct, dignified compensation for hosting national compute infrastructure in their backyards, and each household decides how to spend it. If a community must host the physical machinery of the modern economy, the people living alongside it deserve a direct share of the prosperity it generates.

  1. STATUS QUO

Data center electricity use is set to more than double by 2030 (IEA), and 63% of Americans oppose a new data center in their neighbourhood (Economist/YouGov, Aug 2026). A UVA National Security Institute (UVA NSI) survey of 3,234 adults (June 7-8, 2026) puts opposition at 66%, with fewer than 1 in 5 in support. A majority is opposed in every party and every age group. UVA NSI calls public support "costly and scarce."

The friction: residents carry the local costs (water, power, quality of life). The usual deal is a sales tax exemption for the developer, and community pledges, when offered, go to institutions such as schools and libraries, not households. This policy resolves that by paying households directly and setting enforceable limits on the resources residents worry about.

  1. THE POLICY
  • Household dividend: a one-time $10,000 payment to every household in the host community. This is the median one-time rebate opponents named in the UVA NSI survey, about $240 million for a median-sized county.
  • Income indexing: the payment scales with community median household income, because the price of support rises with income. Households earning $75K-$150K named a median of $25,000; upper-income households named $50,000.
  • Escrow first: at rezoning approval, the developer deposits the full dividend with an independent escrow agent. The money is paid out when construction begins.
  • Peak-demand pause: flexible workloads (model training, batch jobs) pause during local grid peak alerts. The developer pays 100% of any grid upgrades it triggers.
  • Water cap: the permit sets an annual water-use cap, and actual use is published monthly on a public dashboard.
  • Verification: the community commissions an independent opinion survey before and after the payment and publishes the results.
  1. THE IMPACT

Evidence (UVA NSI survey data):

  • Net support, not just less opposition: in UVA NSI's randomized experiment (1,991 participants, July 2-3, 2026), $10,000 household payments were the only $240M option that produced more supporters than opponents. Environmental pledges and school/library pledges did not.
  • Fewer opponents: after an investment pledge, opposition fell by 10 to nearly 20 points and support nearly doubled. Cash had the largest effect.
  • The effect holds near existing sites: among residents who already live near a data center, a school/library pledge cut opposition by 0.2 points on a 5-point scale, compared with 0.45 among residents with no data center nearby. Cash pledges showed no such drop.

Policy commitments (built into the permit):

  • Money stays local: about $240M goes directly to households in a median-sized county. Under a standard sales tax exemption, households receive no direct payment (our inference).
  • Ratepayers protected: residential customers pay none of the developer-triggered grid upgrades, and water use is public every month.

Honest limits: cash wins net support, not a majority, because at least 1 in 10 residents stay undecided. 7% of opponents say no price would change their mind, and costs climb steeply in large, wealthy communities. In UVA NSI's words: "Money can buy goodwill, but how it's spent matters."

Sources: UVA NSI, "The Cost of Public Opposition to Data Centers" (June 2026); UVA NSI, "What Americans Want From Data Centers" (Oct 2026); IEA and Economist/YouGov (Aug 2026), as cited in the Blackstart hackathon brief.

Built With

  • claude
Share this project:

Updates

Submission history