The Freeze Function

On June 9 the public comment window closed on the anti-money-laundering rules that will put teeth in the GENIUS Act, the stablecoin law signed last July, whose full implementing rules take effect on July 18. The debate around all of it is a debate about money. How much reserve has to sit behind each token, and in what (one to one, in cash, insured deposits, and short Treasuries). Whether issuers can pay interest to the people holding the tokens (they cannot, not directly). And how many ordinary bank deposits get up and leave the moment a dollar of stablecoin starts looking like a better checking account than your checking account. The American Bankers Association has been waving around a $6.6 trillion figure for the deposits that could flee. Citi models the stablecoin float reaching as much as $3.7 trillion by 2030. It is a real fight, the numbers are enormous, and I understand why everyone is staring at them.

They are staring at the wrong feature.

The thing that makes a stablecoin dollar different from a bank dollar is not the yield and it is not the settlement speed. It is that the issuer can freeze one specific dollar, in one specific wallet, from a console, in about the time it takes to ship a config change. Tether and Circle both build a blacklist function directly into the token, and it is not a bug or an exploit or a backdoor somebody found. It is a documented capability they describe to regulators as a feature. Tether has used it to freeze more than four billion dollars across better than seven thousand addresses, in coordination with OFAC and U.S. law enforcement. Circle's numbers are smaller, a hundred-odd million across a few hundred wallets, and it froze one of its first big batches the day the Treasury sanctioned the Tornado Cash addresses in 2022. A dollar sitting in USDT has exactly one switch in front of it, and that switch has already been thrown more than seven thousand times.

Now hold that up against the gloriously boring thing it is replacing. A dollar inside the American banking system sits in one of roughly four thousand three hundred separate FDIC-insured institutions, each with its own charter, its own ledger, its own compliance department, its own failure domain. There is no master console. An individual bank can freeze an individual account, sure, and does. But to freeze all of it at once, every dollar in the country, you do not push a config change. You need the state, and you need it to do something extraordinary.

We know exactly what that looks like, because it has happened, precisely once, and it took the entire machinery of the federal government to pull off. At one in the morning on Monday, March 6, 1933, Franklin Roosevelt signed Proclamation 2039 and suspended every banking transaction in the United States. Congress passed the Emergency Banking Act on the 9th, and only after Treasury examiners had gone bank by bank did the system come back, 12,756 of them reopened by March 15. The reason that operation needed a presidential proclamation, an emergency act of Congress, and the better part of two weeks instead of an afternoon is that the money was spread across more than twelve thousand institutions, and there was no single place to reach in and stop it. The friction was the whole point. The fragmentation that everyone now calls inefficient was the thing that made a national freeze require an act of national will.

Programmable money deletes the friction. It rebuilds the single switch of 1933, makes it surgical enough to hit one wallet instead of all of them, and makes it fast enough to throw before you have finished reading the sentence that authorized it. And we have decided to call that progress, and to call the twelve-thousand-ledger mess it replaces backward. Slow settlement, redundant charters, no central console, a system so fragmented it took Congress to halt it. Every one of those inefficiencies is a place where universal control is expensive and slow. None of them was a defect we never got around to fixing. They were the only thing standing between "your money" and "your money, conditional on staying off a list maintained by a company in a console you will never see." You do not feel the redundancy of four thousand banks until somebody has swapped it for one freeze function, and by then feeling it does not help you much.

This is the same lesson the cloud keeps teaching, denominated in dollars instead of GPUs. A single control plane is a single point of seizure, and it does not much matter whether the thing it controls is your compute, your data, or your checking account. Centralizing the ledger does not just make payments faster. It manufactures a switch that did not used to exist, hands it to whoever holds the keys, and bills the convenience back to you as a feature.

A bank run used to take a crowd. A bank holiday used to take an act of Congress. The GENIUS Act has a great deal to say about the reserves behind the dollar and nothing at all to say about who holds the switch in front of it. Both are worth arguing about. Only one of them can freeze your money before you finish this sentence.

Want to learn how intelligent data pipelines can reduce your AI costs? Check out Expanso. Or don't. Who am I to tell you what to do.

NOTE: I'm currently writing a book based on what I have seen about the real-world challenges of data preparation for machine learning, focusing on operational, compliance, and cost. I'd love to hear your thoughts!