A stablecoin is not a bearer instrument. It is a permissioned ledger entry that happens to look like cash. That distinction just cost one payment company $2.76 million, and the lawsuit it filed against Tether is the first serious attempt to drag that distinction into a courtroom.
Here is the anatomy of the event, stripped of narrative. Conduit, a payment firm, held $2.76 million in USDT inside a wallet it describes — in its own filings — as an operational bank account. Not a treasury reserve. Not a speculation vehicle. The working settlement account it used to move money for clients. Tether blacklisted the address. The funds were not stolen. They did not depeg. They simply stopped being spendable, because a single function inside a single contract, controlled by a single company, decided so.
I want to establish the stakes before the technical detail, because the technical detail is where most coverage will lose the plot. This is not a hack story. It is not a depeg story. It is a governance story wearing a technical costume, and the costume is convincing enough that the industry will keep describing it as a "risk event" rather than what it actually is: an unresolved question about who owns the money sitting in your wallet.
The freeze mechanism at the center of this case is not a bug. It is a feature that every major fiat-backed stablecoin ships with. The dispute is not whether the capability exists — it obviously does — but whether the party wielding it owes anything to the party on the receiving end. That is a question of procedure and accountability, not cryptography. And procedure, as I have argued for years, is where decentralization either holds or quietly fails.
Let me lay out the context, because you cannot evaluate the lawsuit without understanding the architecture it is aimed at.
USDT runs on a contract that includes an address blacklist function. The issuer holds the admin key. When that key is exercised, the targeted address can no longer transfer, redeem, or otherwise move its balance. The tokens remain on-chain — visible, accounted for, and completely inert. Circle's USDC ships with the same primitive. This is not a Tether-specific design choice; it is the default posture of the entire fiat-backed stablecoin category. The difference between issuers is not whether they can freeze you. It is what they tell you when they do.
I have been auditing contract logic since I was eighteen, when I spent 120 hours tearing apart the Solidity of three ICO tokens and found integer overflow vulnerabilities in all three. The lesson from that work was never that code is trustworthy. It was that code is only as trustworthy as the assumptions baked into it, and the assumptions in fiat-backed stablecoins are explicitly centralized. A blacklist function is a centralized trust assumption written in Solidity. Nobody hid it. It sits in the contract, documented, callable by one party. The entire category is built on the premise that you trust the issuer not to use it capriciously.
That premise is now being tested. And the test is revealing that the industry never actually agreed on what "capriciously" means, or who gets to decide.
The mechanics matter, so let me be precise about what happened and what did not. According to the reporting, Tether froze the address. Conduit characterizes the freeze as unexplained — no notice, no stated cause, no path to appeal. The funds were not seized by a court order that Conduit could examine. They were frozen by an administrative action taken by a private company. Conduit is now suing to reverse it.
The technical essence is a single trigger: the blacklist function fired. That is a permission event, not a failure event. And this is the first structural insight I want to put in bold, because it reframes everything downstream: the risk to a stablecoin holder is not that the token loses its peg; it is that the token loses its mobility while keeping its peg. Your USDT is still worth a dollar. It is also, for practical purposes, not yours.
This is the ownership-versus-control separation that the stablecoin market has spent a decade papering over. You hold the token. Tether holds the switch. Ownership without control is not ownership; it is a claim on someone else's discretion. The ledger records your balance. It does not record your authority over it.
Now let me go one layer deeper, because there is a structural incentive here that almost no one is discussing and that I think is the actual engine of this dispute.
Tether's business model is straightforward: it holds reserves — predominantly U.S. Treasuries — against the outstanding supply of USDT, and it earns the interest on those reserves. This is real revenue, not token subsidy. When an address is frozen, the corresponding reserves do not go anywhere. They stay on Tether's balance sheet, and they keep generating yield. The frozen $2.76 million is still working for Tether. It is just not working for Conduit.
This is a structural interest misalignment, and it is the detail that should keep every treasury manager awake at night. A freeze costs the issuer nothing. In fact, it is mildly accretive — the frozen float keeps earning while the holder is locked out. There is no economic incentive for the issuer to unfreeze quickly, and there may be a modest incentive not to unfreeze at all. When you combine a discretionary power with a zero-cost exercise and no deadline for reversal, you have designed a system where the default outcome of a freeze is permanence.
I have seen this pattern before, in a different domain. In 2022, during the crash, my DAO hit a governance deadlock because of a flawed voting mechanism, and I had to execute an emergency plan that paused voting and replaced the mechanism with quadratic voting to prevent whale capture. The lesson I took from that fortnight — fifty-plus community calls, strict agendas, actionable updates — was not that emergency powers are bad. It was that emergency powers without a defined exit condition become permanent powers. Tether's freeze has an entry condition and no exit condition. That asymmetry is the whole problem.
Let me now turn to the trigger chain, because the reporting leaves a gap that the architecture fills in.
A freeze does not usually happen in a vacuum. Issuers rarely wake up and blacklist an address for no reason. The typical trigger is an inbound signal — either a law enforcement request or, more commonly, a risk flag from a blockchain analytics provider. Firms like Chainalysis and Elliptic score addresses and propagate risk labels, and those labels frequently become the operational basis for a freeze. This is what I call indirect freezing: the issuer pulls the lever, but someone else decides which addresses the lever points at.
The problem with indirect freezing is that it compounds the transparency deficit. Even if Tether were willing to explain the freeze, it might be acting on a third-party risk score that it cannot fully disclose, generated by a methodology it does not control, based on address clustering heuristics that the targeted party has no way to audit. The chain of accountability becomes a chain of subcontractors. And there is no formal appeals process at any link.
Based on my audit experience, I can tell you that clustering heuristics produce false positives. They always have. An operational wallet that receives funds from many counterparties — which is exactly what a payment firm's settlement account looks like — is structurally indistinguishable, to a heuristic model, from a mixing service. High fan-in, high fan-out, diverse counterparties. A payment company's working account is a textbook risk-score anomaly, not because anything is wrong, but because the model was trained to flag exactly that shape of activity. If that is what happened here, then the freeze is not a judgment about Conduit's conduct. It is a judgment about Conduit's transaction graph.
I am marking that inference as medium confidence, because the reporting does not confirm the trigger. But the architecture makes it the most probable explanation, and the fact that we have to infer it at all is itself the indictment. When a company loses access to $2.76 million and cannot determine why, the system has failed at the most basic level of due process.
Let me now widen the frame to the competitive landscape, because the freeze controversy is only interesting in comparison.
USDT is the largest stablecoin by supply and the deepest by liquidity. Its freeze capability has been exercised extensively — public records show Tether has frozen billions of dollars in aggregate across thousands of addresses. Its transparency around those freezes is, by the account in this case, minimal. Conduit's claim is essentially that it received no explanation and no recourse.
USDC, Circle's stablecoin, ships with the same freeze primitive but has historically been more forthcoming about its use. The 2022 Tornado Cash sanctions response is the canonical example: Circle froze addresses publicly, tied to a named regulatory action, and disclosed the basis. You can disagree with the action, but you could at least see the reasoning and identify the authority behind it. That is the difference between a discretionary freeze and a legible one.
DAI and its successor USDS occupy a third position. Their freeze capability is limited and mediated through governance — meaning that freezing an address requires a vote, a proposal, a process. That process is slow and politically fraught, but it produces a record. Every freeze is a decision someone signed their name to, and that signature is contestable through the same governance machinery that authorized it.
Conduit's own filings indicate it used both USDT and USDC. That detail is not incidental. It tells you that the firm had already diversified its stablecoin exposure and still got caught — which means diversification across issuers does not eliminate the freeze risk, it only distributes it.
The comparison produces a clean conclusion. The market does not lack freeze capability. Every major issuer has it. What the market lacks is a standard for how freeze power is exercised, disclosed, and appealed. Governance is not a feature; it is the foundation. And here the foundation is missing.
This brings me to the contrarian angle, where I want to push against the reflex that this case will trigger.
The instinctive response from the crypto-native audience will be to treat this as vindication — proof that centralized stablecoins are a trap, that the freeze power should be abolished, that the answer is decentralized stablecoins. I think that response is wrong, and I want to explain why carefully, because the pragmatic case is stronger than the ideological one.
Fiat-backed stablecoins are used by regulated payment firms precisely because they are compliant. The freeze capability is not an accident of design; it is a feature that makes the category palatable to the institutions and jurisdictions that give it legitimacy. If you strip the freeze power entirely, you do not get a freer stablecoin. You get a stablecoin that regulated counterparties cannot touch, which means you get a smaller, less liquid, less useful instrument. The freeze power and the institutional adoption are the same object viewed from two sides.
The real failure here is not that the freeze power exists. It is that the power has no procedural wrapper. There is no notice requirement. No stated-cause requirement. No time limit. No appeal mechanism. No separation between the decision to freeze and the decision to unfreeze. A private company holds a switch that can immobilize arbitrary capital, and the only check on that switch is the company's own judgment and the eventual possibility of litigation — which is exactly the remedy Conduit is now forced to pursue, at enormous cost, for a sum that a functioning process would have resolved in days.
The pragmatic fix is not abolition. It is standardization. A freeze should require a documented trigger. The issuer should be obligated to notify the affected party within a defined window. There should be a formal appeal path with a response deadline. And critically, there should be a defined maximum duration for a freeze absent a court order, after which the funds either unfreeze or the issuer must justify continued detention to a neutral arbiter. Efficiency without oversight is just faster risk — and a freeze power with no exit condition is the purest example of that principle I have encountered.
There is a second contrarian point, aimed at the crypto-native side of the room. The fantasy that decentralized stablecoins solve this is largely untested at the scale and liquidity that payment firms actually need. DAI and USDS have governance-mediated freezes, which is better on transparency and worse on latency. If you are a payment company moving client money, latency is not a philosophical preference; it is an operational requirement. A governance vote that takes days to unfreeze a false positive is not obviously superior to a discretionary freeze that takes hours. The tradeoff is real, and pretending it is not is how the industry keeps shipping ideology instead of infrastructure.
This is the same mistake I watch play out across the broader market. On-chain RWAs have been a three-year storytelling exercise because the participants keep insisting that traditional institutions should adopt public chains, when the institutions mostly need a settlement rail with clear rules and enforceable recourse. Layer 2s keep multiplying on the theory that more capacity is scaling, when the observable reality is dozens of networks slicing the same small user base and fragmenting already-scarce liquidity. In both cases, the missing ingredient is not more decentralization. It is better architecture. The freeze controversy is the same story in a different costume.
Let me return to the case itself and extract the forward-looking implications, because the outcome of this litigation has consequences that extend far beyond $2.76 million.
If the court sides with Conduit — or even if the litigation simply forces Tether to articulate a freeze-and-unfreeze procedure to avoid discovery — the precedent could reshape industry practice. A ruling that establishes an obligation to explain a freeze would function as a de facto due-process standard. It would not abolish the freeze power. It would wrap it in procedure. And that would be a genuine improvement, because a discretionary power with a documented process is a fundamentally different object from a discretionary power without one.
If the court sides with Tether, the opposite happens. The freeze power is confirmed as effectively unreviewable, and the industry learns that the only recourse against a freeze is litigation that costs more than most frozen balances are worth. That is a system where justice is priced, and where small holders are structurally excluded from it. The ledger remembers what the community forgets — and what the community has been forgetting, for years, is that the switch was always there.
I want to close on the structural point, because it is the one that will outlast this case regardless of the verdict.
A stablecoin is a claim on an issuer, mediated by a contract, denominated in a dollar. The contract is transparent. The issuer's discretion is not. Every holder of USDT — every payment firm, every market maker, every treasury desk — is running on the implicit assumption that the issuer will not exercise its discretion against them, and that if it does, there will be a way to contest it. This case is the first real stress test of that assumption, and the assumption is not holding up well.
The practical takeaway for anyone with material balances in fiat-backed stablecoins is not to flee to a decentralized alternative, most of which cannot yet carry the load. It is to price the freezability. A stablecoin balance is not cash; it is a claim with a tail risk attached, and that tail risk deserves a line item in every treasury model. Diversify across issuers, yes, but understand that diversification distributes the risk rather than removing it. Keep operational float lean. And demand — loudly, through whatever channels exist — that issuers publish their freeze procedures, because a procedure that is public is a procedure that can be enforced.
Trust the code, but verify the architecture. The code here is fine. It did exactly what it was written to do. The architecture — a single private switch, no notice, no appeal, no deadline, and a reserve that keeps earning for the issuer while the holder is locked out — is what failed. And the question the court will ultimately have to answer is not whether Tether had the right to pull the lever. It is whether anyone who pulls that lever owes the person on the other end an explanation. In the crash, only structure survives the chaos. We are watching, in slow motion, what happens when the structure was never built.
