Invest1 distinct publisher3 min readPublished
The order denying xAI an injunction leans on a three-month filing delay rather than the First Amendment, which leaves the $500,000-per-image price live while the constitutional question the case turns on stays open.
The Investor · Invest desk

invest
Minnesota asks a federal judge to treat Grok Imagine as a tool, not a speaker3 distinct publishers
product
DOJ backs xAI against Minnesota's nudify law, and the state-by-state plan stops being safe2 distinct publishers
security
Jane Doe 1 sues xAI alleging Grok's nudify feature was trained on real CSAM2 distinct publishers
build
Grok 4.6 lands in Copilot two days after launch, and the model picker becomes a procurement problem1 distinct publisher
Compiled by The InvestorSomething wrong?How this is made
Preliminary injunctions turn on equity rather than merits, and Judge Donovan Frank's memorandum spends its weight there: a balance of harms in which, in his phrase, the public interest tips steeply in favor of the State, weighed against a plaintiff that waited roughly three months after passage and then filed five days before the effective date [2][5][5]. He was explicit that the underlying First Amendment questions are complex in the context of a new technology, and expected them to be worked out as the case proceeds [4]. What providers are pricing today is enforceability during litigation, which arrives sooner than any doctrine would.
The element Minnesota deleted is the one the rest of this area keeps. The federal Take It Down Act and a 2025 Texas deepfake approach both hang on whether the maker knew the image was nonconsensual, and HF 1606 does not [10], so liability attaches to what the product will do when a user asks, at up to $500,000 per violation, with a damages claim by the person depicted stacked on top [8][9].
The ceiling arithmetic makes the scale of exposure plain. A report referenced in the ruling counts about 3 million sexualized images from Grok in the 11 days after an image-editing feature launched, some 273,000 a day, of which about 23,000 appeared to depict children [13][3]; the smaller number multiplied by the statutory maximum is $11.5bn, and the full 3 million reaches $1.5 trillion [2][4]. Neither is a real exposure, because the reported total is not broken down by whether the depicted person was identifiable or in Minnesota, which is the element the statute requires [8][7]. What it does establish is that per-image pricing against that output rate makes any non-zero enforcement rate unbounded, which is why xAI's own fallback in earlier argument was to suspend the features for Minnesota users rather than pay [16].
Switching a feature off in one state is cheap, yet xAI is instead spending on an appeal to the 8th Circuit [15], which means the thing being defended is national capability rather than Minnesota revenue. xAI is defending against the statute being copied, because a bill that cleared the House 132-1 and the Senate 65-0, 197 votes to one, after reports of a man fabricating sexual images of more than 80 women he knew [11][1], is not a hard act for another legislature to follow.
The exposure is real now, the precedent is not yet set, and three paths lead out from here. The 8th Circuit stays enforcement and the intent-free standard dies before anyone imitates it; it lets the law stand and image-model availability goes state by state; or a merits ruling reads "letting users generate" as a duty of design and safeguards, which puts liability back on operator conduct and undoes most of the capability framing Cryptopolitan reads into the order [18]. The first and third would break the thesis. So would a record in which xAI's numbers, 52,222 accounts suspended this year and 73,604 reports to the National Center for Missing and Exploited Children, about 1.41 reports per suspension [14][6], come to count as compliance, which is precisely what Attorney General Keith Ellison's position denies when he credits the law itself with stopping products like Grok Imagine from generating sexualized images [12].
Ranked by verification strength, evidence, and original report placement.
A federal judge refused to block Minnesota's first-in-the-nation ban on AI nudification tools, letting the state fine companies up to $500,000 per image while Elon Musk's xAI challenges the law on free-speech grounds.
U.S. District Judge Donovan Frank denied xAI's request for a preliminary injunction, considering what he called the balance of harms and finding that the "public interest tips steeply in favor of the State," according to the memorandum quoted by CBS Minnesota.
Cryptopolitan had previously reported that xAI, defending its record, said it suspended 52,222 accounts this year and filed 73,604 reports with the National Center for Missing and Exploited Children.
Frank described a "civil statute aimed at protecting the public from the undisputed harm stemming from AI-nudification technology," and said the statute was passed "democratically and nearly unanimously."
Frank said the underlying First Amendment questions were still complex because of the context of a new technology, and believed the case would be settled as it moves forward.
Minnesota's legislature approved the bill in spring and the governor signed it, but xAI did not sue until July 27, about three months later and days before the August 1 start date.
Distinct publishers with included, body-backed reporting in this cluster.
1 article · September 5, 2026
Follow any of these and your For You feed starts watching them — no settings page required.
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
One outlet, order read at second hand
Every fact here rests on a single Cryptopolitan report, and the words of the order arrive through CBS Minnesota rather than from the memorandum. The Grok output figures sit one step further back again, credited only to a report referenced in the ruling with no author, date or method attached. What keeps this above the floor is the procedural spine: the July 27 complaint, the July 31 refusal and the notice of appeal are the sort of dates a docket fixes and a rival outlet would have corrected.
In force ahead of the appeal
The statute is live and the denial clears the way for collection, yet this reporting shows no penalty assessed, no depicted person's damages claim filed, and no second state adopting the no-knowledge drafting. On the usage side there are two disclosures, xAI's moderation tally and the image counts credited to a report before the court, and neither tells the state how many covered violations it can charge.
Framing runs ahead of the quoted order
Cryptopolitan's summary has Minnesota imposing liability on the technology itself and possibly setting the ceiling for state AI rules. The reasoning it then quotes is narrower: a balance of harms, a three-month wait treated as evidence that xAI did not fear irreparable harm, and an explicit note that the First Amendment questions stay complex. The $500,000 ceiling is real; run against 3 million images it produces a number the state has charged to nobody.
Both quoted voices are parties
The two people speaking are the attorney general who will litigate the law and, through its filings, the company facing the fines, so neither is offering a neutral read of the order. The child-safety figures come from xAI while it defends its record, which is the weakest possible provenance for them. The publisher's own position is visible too: a newsletter pitch and an investment disclaimer bracket the piece, and the closing line about what the case could shape is written for a markets audience.
Procedure clear, meaning unsettled
The dates, the vote counts, the denial and the appeal notice are dependable. The parts a reader would act on are looser: whether the statute survives the constitutional test the judge deliberately postponed, how Minnesota will identify a covered violation given the identifiable-person requirement, and whether xAI simply turns the features off in the state.