55/100

Moderate evidence

ProblemPublished recordClimateProblem Space

‘Elonville’: US residents say Musk’s xAI offered to buy homes if they don’t sue over datacenter noise

Truvace record
TRV-2026-2890raw data (JSON)
Version
v1Published
First published
Evidence type
Investigative reporting
Sources
1 sourceJournalism
sha256
e2bcecd95875…check it

People in a Mississippi neighborhood, many of whom dislike a nearby power plant central to Elon Musk’s artificial intelligence ambitions, have received a stark offer – to sell their houses to his company and make way. Real estate agents have been going door to door in Southaven, Mississippi, on behalf of xAI, touting a deal to purchase houses as long as the owners agree to not join a lawsuit against the company over the power plant’s noise. (Musk’s AI company officially became SpaceXAI in July and has lately bee…

The problem

Residents of Southaven, Mississippi, say xAI's subsidiary MZX offered to buy their homes only if they stay out of a class-action noise suit over the datacenter's 69 gas turbines; MZX had bought five homes since 9 October, according to DeSoto county records.

What this doesn’t fix

xAI did not respond to questions about the buyout numbers and denies the noise claims, and the 418-home target comes from a realtor's recorded remarks; no on-site air pollution monitoring has been done.

Sources

1 on file
  1. The Guardiantheguardian.com
    Journalism2026-10-28

Cite this record

v1

Truvace Impact Record TRV-2026-2890, v1: “‘Elonville’: US residents say Musk’s xAI offered to buy homes if they don’t sue over datacenter noise.” Truvace, 2026-11-13. /record/TRV-2026-2890 (accessed on the day you copy it). sha256 e2bcecd95875391b…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv1e2bcecd95875…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2890 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.