How DeepSeek Claims Went Viral on X Before Nvidia's Selloff

Archive note: this investigation was researched and first published in August 2026. The event time marks The Kobeissi Letter's Sunday post. X view and repost counters below were captured on Saturday, August 22, 2026 and can continue to change.

Countdown to Nvidia's 17% drop: market-directed X framing accelerated on Friday, January 24—three calendar days before Nvidia fell 16.9% on Monday, January 27—and the largest cost-comparison posts landed on Sunday, one day before the selloff.

DeepSeek's market story was assembled in public. A technical result moved through prominent venture investors, founders, financial commentators and newsrooms, acquiring stronger claims at each step. The central accounting qualifier disappeared: $5.576 million was DeepSeek's estimate for the official V3 training work, not a complete budget for developing R1.

The high-reach posts

How traditional media amplified the compression

TechCrunch published a Sunday roundup at 20:49 UTC—one calendar day before Nvidia's drop—that embedded Andreessen, Khosla, Zschaepitz and Garry Tan. It reported the $5.6 million figure as the cost to train one DeepSeek model but did not carry the V3 paper's exclusion into the short comparison with U.S. competitors. The story also supplied the powerful App Store fact.

At 10:17 UTC on Monday, January 27—the selloff day—CNBC published its pre-market report. It described a free open-source model as having been developed in two months for under $6 million. Zschaepitz posted that wording and the link nine minutes later. This sequence shows information moving from X into news coverage and back to X with the stronger development-cost formulation intact.

After the close on the selloff day, Fortune said DeepSeek had made R1 in two months for under $6 million and linked to GitHub as support. DeepSeek's R1 repository did not make that all-in cost claim. The error survived even after Bank of America and Bernstein commentary, published earlier on Monday, had explained that the figure belonged to V3 and excluded research and experiments.

The correction arrived after the panic was underway

At 14:54 UTC on Monday, January 27—the selloff day—hedge-fund manager Gavin Baker published a detailed corrective thread. It accumulated 3,351,339 views and 1,408 reposts. Baker called the $6 million framing deeply misleading and separated inference efficiency from research history and cluster access. By then U.S. cash trading had been open for twenty-four minutes and Nvidia was already sharply lower.

Did the posts cause Nvidia's move?

The chronology supports an amplification mechanism, not a precise causal estimate. The most important posts appeared one to three calendar days before Monday trading, used market-directed language and were embedded or repeated by news outlets. Contemporaneous market reports identified DeepSeek's cost narrative and app ranking as catalysts. Those facts make the posts relevant evidence of how a common explanation formed.

The counters cannot establish how many impressions occurred before the opening bell. They also cannot isolate X from television, app rankings, analyst notes, crowded positioning or automated risk controls. Describing the episode as “X caused the selloff” would repeat the same compression this audit documents.

False, misleading, unsupported or opinion?

• False attribution: R1's total development cost was $6 million.
• Materially misleading: a $5.576 million V3 training estimate is directly comparable with $80 billion, $65 billion or $500 billion of corporate and national infrastructure plans.
• Unsupported: DeepSeek faked the number as a state operation, or possessed a specific hidden H100 inventory, without published evidence.
• Opinion: R1 was a “Sputnik moment,” the biggest threat to U.S. equities, or an extraordinary breakthrough.

“Disinformation” implies deliberate deception. The available record proves that false and misleading claims spread widely; it does not prove the intent of every account that repeated them.

Two engagement records must remain separate

The table above reports counters visible when MoveSurge captured the native X pages on Saturday, August 22, 2026, long after Nvidia's drop. A second evidence layer in the research handoff records lower-bound snapshots published in contemporary secondary coverage during the event. Neither layer reconstructs a minute-by-minute impression curve. Combining them would falsely move later engagement back in time.

The event-time values above come from contemporaneous secondary snapshots, not a official X historical export. “More than” remains a lower bound. The later native counters in the first table are useful for cumulative reach, while they cannot reveal what the opening-bell audience had already seen on Monday, January 27.

The technical compression had a repeatable shape

The transmission chart tracks three recurring losses of scope. “Comparable on selected reasoning tasks” became universal parity. “Open-weight with code/report” became fully reproducible open source. A documented 2,048-H800 V3 training setup became a story that DeepSeek had succeeded without advanced Nvidia chips. Each shorter formulation was easier to share and stronger as a market claim.

The cost story followed the same path. A V3 training-compute estimate became an R1 development budget, then became a comparison with annual U.S. capital plans. The false or misleading sentence did not need to originate with one malicious actor. Repetition across accounts and headlines was enough to make the compressed version feel settled. That is why this audit uses “false,” “misleading,” “unsupported” and “opinion” as separate labels. “Disinformation” is reserved for cases where intent to deceive can be established.

Reddit reveals what headline counts miss

Reddit scores are mutable and fuzzed, and the sample is not a representative survey. Its analytical value is thematic: engineers were already debating reproducibility and deployment on Monday, January 20—seven days before the drop—while memes, censorship and manipulation allegations dominated broader communities by Sunday and backlash continued after the selloff.

What the chronology can support

The record supports a feedback loop: technical claims reached X and Reddit; Sunday technology coverage embedded influential posts; Monday pre-market reporting retained the stronger development-cost wording; and that reporting returned to X while Nvidia was repriced. Timing and reach make this mechanism plausible and document how a common explanation formed.

The evidence does not allocate the 16.9% Monday decline among X, Reddit, television, app rankings, analyst notes, crowded positioning and automated deleveraging. It also cannot show that every account knew a claim was wrong. The useful result is a method for the next narrative: timestamp the native post, freeze the counter with its capture time, preserve the primary-source scope and align each qualitative event with market bars without treating correlation as causation.