Verified Platforms
Quick Links
Where to Stay Secure
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Writing code that moves money does not make you a money transmitter. Holding someone else's money does.
That distinction is the entire fight in Washington right now, and it is not academic. It decides whether the non-custodial wallet on your phone, the node running in your closet, and the DeFi front-end you opened this morning stay legal to run in the United States.
So are crypto developers money transmitters? Under current U.S. law the answer turns on one fact, and it is not whether your code moves value.
This walkthrough follows Tao, Kodex's bridge between structure and instinct, who ships a little open-source code on the side and woke up convinced it could be read as a felony. Reading the statute with him is Lilith, a twenty-year cybersecurity veteran and decentralization advocate whose first question about any system is always the same: who holds the keys.
Tao slides his laptop across the desk. A headline sits open: a developer, convicted, over software that strangers used to move their own coins.
"If they can do that to him," he says, "what stops them from doing it to me?"
Lilith does not answer the fear.
She answers the mechanism.
"Start with what the law actually measures," she says. "Then we will know which side of the line you are standing on."
The federal hook is a statute called 18 U.S.C. section 1960. It makes it a crime to run an unlicensed money transmitting business. The word doing the work is business, and underneath it sits a definition that decides everything: a money transmitter is someone who accepts and transmits funds for other people.
Accepts. As in takes hold of.
"Read it twice," Lilith says. "It is about possession. Whether at any point you take control of someone else's money and pass it along."
FinCEN, the Treasury bureau that enforces this, said as much in plain language back in 2019. Its guidance on convertible virtual currency drew the line at control. A business that accepts and transmits value is a transmitter. A person who only writes or supplies the software that others use to move their own funds is not. The test is custody. Not cleverness, not how much value flows through the thing you built, not how useful it is. Custody.
Tao turns that over. "So the wallet I contribute to never touches anyone's coins. The keys live on the user's device. We could not move their funds if a court ordered us to."
"Then under the 2019 reading, you are not transmitting anything," Lilith says. "You wrote a tool. They held their own money."
This is the part worth carrying out of the room. It is the backbone of how crypto gets regulated in 2026, and the deeper idea lives in who controls a token: control is the thing the law follows. When you cannot move it, freeze it, or seize it, you do not control it. And what you do not control, you are not transmitting.
It is a clean line on paper.
The trouble is that a courtroom blurred it.
The case on Tao's screen is Tornado Cash. In 2025 a jury convicted Roman Storm, one of its developers, on a count tied to running an unlicensed money transmitting business. Tornado Cash was immutable, non-custodial code. It never held anyone's funds. People mixed their own coins through a smart contract that Storm could not stop.
"He never took custody," Tao says. "That was the whole design."
"And he was convicted anyway," Lilith says. "That is why every builder I know went quiet for a week."
The prosecution ran a different theory than the 2019 guidance. Not custody, but facilitation. The argument: by writing and promoting software that moved value for others, the developer was in the money transmitting business, custody or not. Call it code as conduct. If it holds, the act of publishing becomes the crime.
A detailed legal reading of the cases walks through why that theory strains the statute. Section 1960 was built around control, and the older convictions it leans on involved people who actually handled customer cash. Storm handled none.
Then the picture shifted, in a useful direction. The Justice Department later signaled it would not approve section 1960 charges where the software is truly decentralized, only automates peer-to-peer transfers, and gives no third party custody or control.
That sounds like relief.
It is not safety.
"Guidance is not law," Lilith says. "A policy memo can be rewritten by the next administration on a Tuesday. Storm was still convicted. The line moved into a gray zone, and gray zones are where careful people stop building."
Tao goes quiet. He is not afraid of a memo. He is afraid of the version of this where the memo is gone and the conviction is the precedent that stays.
That is the fear Section 604 is meant to retire.
Section 604 of the CLARITY Act is the Blockchain Regulatory Certainty Act, folded into the larger market-structure bill. Stripped to its job, it does one thing: it writes the custody line into statute. A developer, a node operator, or a validator who does not control user funds is not a money transmitter for the act of writing or maintaining software.
"It takes the 2019 guidance and makes it hard to delete," Lilith says. "Not a memo. A law."
The Cato Institute, arguing the no-custody principle is sound policy, puts it plainly: you should not carry a money transmitter's liability for building a tool you cannot use to touch anyone's money. The protection is aimed at the non-controlling builder, the person whose code runs without them.
Tao exhales for the first time. "So if it passes, the wallet is safe."
"If it passes intact," Lilith says. "Read those last two words carefully."
Where the bill actually stands is its own story: the Senate vote mechanics cover committee versus floor. What matters in this room is smaller. Section 604 is not law yet. It is text inside a bill that has cleared a committee and is waiting.
Waiting is not the same as winning.
A carve-out is only as strong as its exceptions. Section 604 protects non-controlling developers, but a separate criminal-liability clause still reaches anyone who knowingly facilitates illegal activity. On its face that is reasonable. No one is asking for a safe harbor for laundering. The risk lives in the word knowingly and in how far a prosecutor can stretch it. If publishing open code that someone later misuses can be read as knowing facilitation, the exception can swallow the protection whole.
"That is the Storm theory wearing a different hat," Lilith says. "Write the shield, then leave one door open wide enough to drive the old argument back through."
The fight over that door is live. In January, two senior members of the Senate Judiciary Committee, Chuck Grassley and Dick Durbin, sent a letter opposing Section 604 as written. In June, a meeting at the Eisenhower Executive Office Building brought FinCEN, law-enforcement officials, and members of Congress together to debate weakening it. Days later more than sixty crypto executives, alongside Coin Center and the Solana Institute, pressed the Senate to keep it intact.
Tao does the math out loud. "So even if the part that protects me passes, the part that could undo it is being argued over right now."
"And committee approval is not the finish line," Lilith says. "The bill cleared the Banking Committee fifteen to nine and went onto the Senate calendar. The floor needs sixty votes, not a simple majority, and the calendar before the August recess is short. A bill can have the support to advance and still die of arithmetic and time."
Committee passage is momentum.
It is not law.
Tao asks the question he actually walked in with. "Forget the developers for a second. The tools I use every day. Could they just disappear?"
"That depends entirely on which side of the custody line each one sits," Lilith says. "So let us sort them."
She lays them out in a grid.
| Tool | Who holds the keys | Who can move your funds | Money transmitter under the custody test? | What Section 604 says |
|---|---|---|---|---|
| Custodial exchange (Coinbase-style) | The company | The company | Yes, it takes custody of your funds | Unaffected, it already transmits |
| Non-custodial wallet (MetaMask-style) | You | Only you | No, it never holds your funds | Protected, the maker cannot move your money |
| Node or validator | No user funds held | No one, it relays and confirms | No, it processes the network | Protected, non-controlling infrastructure |
| DeFi front-end | You, through your own wallet | Only you, the contract self-executes | No, when it never takes control | Protected, while it stays non-custodial |
The line is custody, every time.
"Look at the second column," Lilith says. "Wherever the answer is only you, the maker of that tool was never a money transmitter under the real test. The custodial exchange already lives under money-transmission rules and will keep doing so. The wallet, the node, the front-end were never on that side of the line, unless someone forces them onto it."
This is the same control question that decides whether your USDT can be frozen: when an issuer can reach into your balance and move it, that is custody, and custody is exactly what carries the obligations.
Tao studies the MetaMask row. "So self-custody is the protection."
"Self-custody is the protection," Lilith says. "If the only person who can move your money is you, then no one is transmitting it for you. Not even the people who wrote the wallet."
If Section 604 dies, nothing switches off overnight. You can still self-custody. The risk is colder than a ban: builders of U.S.-facing non-custodial tools keep working under the Storm shadow, some leave, some never start, and the surface of what you can reach from inside the United States narrows quietly.
Not a wall. An erosion.
You feel a ban the day it lands. You rarely notice an erosion until the tool you wanted is already gone.
By now Tao has stopped asking whether he is a criminal. He is asking the better question: how do I tell, for any tool, which side of the line it sits on.
"Three questions," Lilith says. "Run them before you trust anything that holds value."
That last question is the whole test compressed. Non-custodial means you hold the keys. It means the side of section 1960 the statute was never written to reach.
This is the reading discipline the Survival Framework is built on: judge a tool by what it can do to you, not by the name on the front door.
Tao closes the laptop. The headline is still under there. The conviction is still real, the bill still unfinished, and none of that resolved while they talked.
What changed is what he knows to look for.
"The law is still moving," he says. "But the question I ask about any tool is not moving at all. Who can touch my money."
"That one never changes," Lilith says. "Learn to answer it, and you will always know which side of the line you are standing on, whatever the Senate decides."
Not for writing software, under the test FinCEN set out in 2019. A money transmitter accepts and transmits funds for other people. A developer who builds non-custodial code that never takes control of user funds is not transmitting anything. The line is custody, and writing code does not cross it.
No statute makes writing crypto code a crime. The Justice Department has said code written without intent to break the law is not itself a crime, and has indicated it will not pursue money-transmission charges over truly decentralized, non-custodial software. The caution is that this is policy, not settled law, and one developer, Roman Storm, was convicted on a facilitation theory in 2025.
Section 604 is the Blockchain Regulatory Certainty Act, folded into the CLARITY market-structure bill. It would write into statute that a developer, node operator, or validator who does not control user funds is not a money transmitter for building or running software. It codifies the custody line so a change in policy cannot erase it.
He was convicted in 2025 on a count tied to operating an unlicensed money transmitting business, over the Tornado Cash software. That software was non-custodial and never held user funds, which is why the case alarmed builders. The theory treated publishing and promoting the code as the conduct, rather than requiring custody.
A non-custodial wallet keeps the keys on your device, so only you can move your funds. That places it on the protected side of the custody line, and Section 604 is written to keep it there. The real risk is not your wallet being switched off, but U.S.-facing builders facing enough legal uncertainty that fewer of these tools get made.
