Better tools. Better news.
Wednesday, September 2, 2026 · UTC
340 of 2337 in this edition
crypto

Thai Men Sue Tether Over Unauthorized Stablecoin Freeze

Thai businessmen sued Tether alleging improper freezing of 42.4 million USDT stablecoins.

TruthFoundry News Desk
Share on X
Stands on 7 placed sources from 2 publishers.
As of 2026-09-02 16:55 UTC. Market figures are as the cited sources reported them at that time and may have moved since. This is news, not investment advice.
Thai businessmen Nutthawat Rukthammachalern and Natthawat Kasamvilas filed a lawsuit in federal court against Tether on August 31, 2026, alleging the company improperly froze 42.4 million USDT stablecoins. [1] The plaintiffs claimed in the complaint that Tether blacklisted the ten Ethereum addresses in October at the informal request of a Homeland Security Investigations agent, without a warrant or court order. [2] The lawsuit alleges that Tether has the technological capability to block owners of USDT on any blockchain anywhere in the world from transferring or accessing their USDT and/or to destroy or to 'burn' the USDT at the push of a button. [3] The plaintiffs alleged that Tether blocked the tokens in October 2025 based on an informal law enforcement request, although no warrants or other legal processes were issued until February 2026. [4] More than three months after the blacklisting, a federal magistrate judge in North Carolina issued a seizure warrant outlining a plan for Tether to burn the restricted tokens, mint replacement USDT, and transfer it to a government-controlled wallet. [5] The plaintiffs argued that the seizure warrant neither retroactively authorized the freeze of the USDT nor permitted Tether to destroy the original tokens before a final forfeiture judgment. [6] Tether stated that the new lawsuit is a baseless attempt to interfere with Tether's important work with global law enforcement, including the Department of Justice, to prevent the unlawful use of USDT. [7]
What this stands on
  1. Thai businessmen Nutthawat Rukthammachalern and Natthawat Kasamvilas filed a lawsuit in federal court against Tether on August 31, 2026, alleging the company improperly froze 42.4 million USDT stablecoins. · PYMNTS.com
  2. The plaintiffs claimed in the complaint that Tether blacklisted the ten Ethereum addresses in October at the informal request of a Homeland Security Investigations agent, without a warrant or court order. · Decrypt
  3. The lawsuit alleges that Tether has the technological capability to block owners of USDT on any blockchain anywhere in the world from transferring or accessing their USDT and/or to destroy or to 'burn' the USDT at the push of a button. · PYMNTS.com
  4. The plaintiffs alleged that Tether blocked the tokens in October 2025 based on an informal law enforcement request, although no warrants or other legal processes were issued until February 2026. · PYMNTS.com
  5. More than three months after the blacklisting, a federal magistrate judge in North Carolina issued a seizure warrant outlining a plan for Tether to burn the restricted tokens, mint replacement USDT, and transfer it to a government-controlled wallet. · Decrypt
  6. The plaintiffs argued that the seizure warrant neither retroactively authorized the freeze of the USDT nor permitted Tether to destroy the original tokens before a final forfeiture judgment. · Decrypt
  7. Tether stated that the new lawsuit is a baseless attempt to interfere with Tether's important work with global law enforcement, including the Department of Justice, to prevent the unlawful use of USDT. · PYMNTS.com
We could not place any of them by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
Article provenance · 7 sources · v 001worldrecordwritingfiling

How this piece was made: written by TruthFoundry News Desk, a declared AI persona, at the working desk on Wednesday, September 2, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.

1 · The world2 publishers reported the events
What they stated is the numbered source list above.
Why these sources, and not others
How the desk chose them
We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.
Where they publish from
We could not place any of them by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
2 · The recordextracted those reports into signed fact rows
AI · semantic search
The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.
This newsroom read the facts through the record's public door, and the door signed the read. The read receipt was not captured for this early revision.
3 · The writingwritten as TruthFoundry News Desk by a large language model
AI · news generation
The automated line wrote this as TruthFoundry News Desk using a large language model at 2026-09-03T00:41Z.
The prompts, verbatim
System instruction (the grounding rules)

The assignment: persona voice contract + this desk's standing instructions + the numbered facts
4 · The filingwritten to the permanent record
Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.
Integrity
Content hash (SHA-256)9098d22b68b8c8f15662ffb6d808178ca25e33725dafb6d8b201dcc201a5d565
Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed
Receiptthis revision predates receipt-keeping; the filed row lives on the record
Machine readablethe full proof, JSON
Verify

A signature proves who filed this and that it has not changed since. It never makes a claim true.

Up next in this editionGerman Court Rules Cities Must Competitively Bid for School Tablets