Two Thai businessmen sued Tether in the Southern District of New York on 2 September 2026. Nutthawat Rukthammachalern and Natthawat Kasamvilas say roughly $42.4 million of USDT across ten Ethereum addresses was blacklisted last October at the informal request of a Homeland Security Investigations agent, with no warrant and no court order, and that a federal magistrate judge in North Carolina issued a seizure warrant about three months later, setting out a plan for Tether to burn the restricted tokens, mint replacements and send them to a government-controlled wallet. They say they bought the USDT on the secondary market, never opened a Tether account, and they want access restored plus damages and the income earned on the reserves backing the tokens. Tether calls the case “a baseless attempt to interfere with Tether’s important work with global law enforcement”. All of that is an allegation, and a court will decide it, not us.
TL;DR
- Two Thai businessmen allege Tether froze $42.4m of USDT in October on an informal law enforcement request, with the seizure warrant arriving roughly three months afterwards.
- The freeze capability is not news; we covered the kill switch in April. What is new is that the plaintiffs say they never had any relationship with Tether at all.
- Platform discretion needs an account. Issuer discretion needs only the token, so you inherit it by being paid.
- Chainlink VRF verifies the proof on-chain before the callback fires, so a Satoshie outcome cannot be provisional and then justified later. That guarantee stops at the edge of the contract.
- No game contract can make a payout unfreezable if the payout is denominated in an asset somebody administers. That is the forty-fourth unasked half of fairness.
Give Tether its due first
A stablecoin that can freeze nothing is a better instrument for a thief than for a victim. The wider Justice Department matter this money is reportedly attached to involves more than $61 million tied to pig butchering, the scam where somebody spends months building a relationship in order to empty an account. Those victims are real, mostly not crypto natives, and their odds of recovery without an issuer able to act are close to zero. Freezing works, which is why it gets used.
Tether also freezes in public. The blacklist is a transaction: you can see it, timestamp it and count them, which is more than any bank will give you about the account it quietly restricted this morning. When we write about centralised control we usually complain that the control is invisible. This one is not. So this is not a post about a villain. It is about a property, and it is one on-chain gaming keeps leaving out of its fairness story.
The bit that is actually new
We wrote the kill switch post in April, when $344 million of USDT was frozen over Iran links. The existence of the capability has not been in question since. Two things in this complaint are new, and only one of them is the one everybody is arguing about.
The loud one is sequence. The effect is alleged to have landed in October, the legal instrument in January. Even if that proves perfectly lawful, and it might, it describes a system where the justification can arrive after the action. Compare it with the thing this platform runs on: a Chainlink VRF request produces a proof, the coordinator verifies that proof on-chain, and only then does the callback fire. No outcome is provisional while its proof is in the post, because the check sits in front of the effect rather than behind it. That is not code being more just than courts, which have appeals where code has none. It is a point about ordering, and ordering is a structural property you can read off a system instead of a virtue you have to trust.
The quiet one matters more. The plaintiffs say they never opened a Tether account. They bought tokens from somebody else, on the secondary market, and every control that then applied to them applied without a signup, a terms page, a tick box or a relationship of any kind.
Account-bound control versus asset-bound control
This series has spent forty-three instalments on discretion held by a platform: who can delay your payout, who can void a win, who can change the rules between the block where you staked and the block where you settled. All of that assumed a relationship. You chose the venue and accepted its terms, so the discretion came bundled with a decision you actually made.
Issuer control does not work that way. It travels with the asset, and you receive it by being paid, so the ordinary defence of reading the terms and picking a better operator never gets a chance to apply. Auditing the platform you play on answers a question about the platform. It says nothing about the token that platform pays you in.
For crypto gaming that splits the fairness stack into three layers, not the one the industry advertises. The draw, which Chainlink VRF settles and any stranger can recompute. The settlement, handled by escrow, resolution and payout in a single transaction, with no admin key and no window for a human to see the result and think about it. And the denomination, which neither of those touches, because whatever powers live inside the token you are paid in were minted long before you won it.
What Satoshie can honestly claim, and where it stops
Our claim is narrow and deliberately falsifiable. Stake escrow, VRF resolution and payout happen in one transaction. The coinflip is randomWords[0] % 2. The raffle is keccak256(VRF word + prior blockhash) % ticketsMinted, with ticketsMinted readable before you enter. The contracts are verified and immutable on Base with no admin key, no clawback and no setter that can move a payout, a fee or a win condition. Nobody here can pause your win, re-review it after seeing the number, or reverse it. If you think we can, read the bytecode; you do not need our cooperation to check.
That guarantee terminates at the edge of our contract, and this post exists to say so plainly rather than let the word trustless imply coverage it has never had. If your winnings are denominated in an administered token, whatever its issuer can do it can do to you after the payout lands, and there is no line of Solidity we could write to stop it. The responses available are honest but unglamorous: hold a settlement asset with no administrator and accept the volatility as the price, or keep the administered one and know exactly what came with it. Pretending the choice is not there is the only genuinely dishonest option.
The usual caveats stand. Our front end is an ordinary web app and the least trustworthy thing we ship, Base’s sequencer is operated by Coinbase today with forced inclusion at L1 as the backstop, and immutability means our own bugs are permanent, which is a trade rather than a free win.
Three questions worth asking tonight
- Who can freeze the token your winnings are paid in, and what has to exist before they can do it: a court order, a request, or a decision?
- Does your fairness check cover the asset, or only the draw? Verifying the randomness of a payout you cannot spend is a proof about the wrong step.
- If your balance were restricted tomorrow with no explanation, what is your first move, in which jurisdiction, and how many months does it take? Compare that with how long the restriction took.
Provable fairness answers one question completely: did the house cheat. It says nothing about whether somebody who was never part of the game can stop the money afterwards, on their own timetable, without having ever met you. That is the forty-fourth unasked half of fairness, and it lives in the asset, not the algorithm.
📷 Photo by Georg Bommeli on Unsplash
