42/100

Emerging evidence

ProblemPublished recordBusinessProblem Space

Nvidia’s Jensen Huang expected to testify before Congress amid calls for crackdown on China chip exports – live

Truvace record
TRV-2026-2882raw data (JSON)
Version
v1Published
First published
Evidence type
News report
Sources
1 sourceJournalism
sha256
5dfed1f4648c…check it

US commerce secretary Howard Lutnick will testify before Congress on the Nvidia scandal. US lawmakers have called for clarity on what the Donald Trump’s administration knew about Nvidia chief Jensen Huang’s extramarital affair with a woman accused of spying for China. “Secretary Lutnick has proactively agreed to appear voluntarily before the Banking Committee to address their questions,” Kristen Eichamer, a spokesperson for Lutnick, told NBC News. Lutnick has come under scrutiny as the commerce department was ma…

The problem

Megaspeed, a Singapore-based cloud firm that bought nearly $5bn of Nvidia AI chips and hardware over three years, is under scrutiny for allegedly steering them to China despite US export rules, prompting congressional demands for answers from Commerce.

What this doesn’t fix

The diversion of chips to China is alleged and still under investigation by Malaysia, Singapore and US officials; no finding of wrongdoing is reported.

Sources

1 on file
  1. The Guardiantheguardian.com
    Journalism2026-11-13

Cite this record

v1

Truvace Impact Record TRV-2026-2882, v1: “Nvidia’s Jensen Huang expected to testify before Congress amid calls for crackdown on China chip exports – live.” Truvace, 2026-11-13. /record/TRV-2026-2882 (accessed on the day you copy it). sha256 5dfed1f4648cd988…

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. Publishedv15dfed1f4648c…

    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-2882 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.