A federal judge in the Northern District of Texas has dismissed a developer’s lawsuit seeking a declaratory ruling that his non-custodial crypto donation platform would not violate federal money-transmitter laws. The ruling leaves the core legal issue unsettled and preserves uncertainty for developers building software that facilitates value transfers without taking custody of user funds.
The decision turned on standing rather than on the substance of the underlying legal question. Instead of deciding whether non-custodial software falls within federal money-transmitter statutes, the court concluded that the plaintiff had not shown a credible and imminent threat of prosecution.
Court Dismisses the Case Without Reaching the Central Legal Question
Chief U.S. District Judge Reed O’Connor granted the government’s motion to dismiss after finding that Michael Lewellen had not demonstrated a sufficiently concrete enforcement risk. Lewellen had asked the court to preemptively confirm that Pharos, his crypto donation platform, would not trigger money-transmitter obligations because it was designed to operate without custodial control over user funds.
In reaching that conclusion, the court pointed in part to a Department of Justice memo titled Ending Regulation By Prosecution. The judge treated that internal policy statement as weakening the argument that Lewellen faced a realistic near-term risk of criminal enforcement. Because of that, the court found there was no justiciable controversy serious enough to support the declaratory relief he was seeking.
The dismissal was entered without prejudice, which is a meaningful detail. That means the lawsuit did not fail on the merits and the legal question can return to court later if a more concrete enforcement threat or actual prosecution emerges. For now, though, the boundaries of federal money-transmitter law as applied to non-custodial tools remain undefined.
Industry Support Shows How High the Stakes Have Become
The case drew support from some of the most prominent organizations in the crypto policy and DeFi advocacy space. Groups including the Blockchain Association, Paradigm, the DeFi Education Fund and the Uniswap Foundation backed the effort, reflecting how broadly the issue resonates across the industry.
Those organizations argued that a DOJ memo is not enough to give developers meaningful protection. Their position is that an internal enforcement policy can change at any time and does not carry the force of a binding judicial ruling or a statutory safe harbor. In that sense, the court’s reliance on the memo may have resolved the standing issue in this specific case while doing little to reduce practical anxiety across the developer community.
That anxiety has not emerged in a vacuum. Industry concern has been shaped by earlier prosecutions involving developers tied to Tornado Cash and Samourai Wallet, cases that many in the crypto sector view as evidence that writing decentralized software can still attract criminal scrutiny. The court distinguished those matters by emphasizing the money-laundering allegations involved there and by noting that Lewellen had disavowed any intent to facilitate illicit transfers.
Developers Are Still Left to Manage the Risk Themselves
The ruling changes very little for teams building non-custodial products. Without a definitive interpretation from the courts, developers and compliance teams must still evaluate whether their software design, user flows and operational policies could be characterized as facilitating money transmission under existing law.
That leaves two immediate priorities. First, firms need to document with precision how their products separate facilitation from custody; second, they need to prepare for the possibility that enforcement will arrive before legal clarity does. Internal policy memos may offer a signal about current prosecutorial posture, but they do not provide durable legal protection.
The court has delayed the answer rather than delivered one. The dismissal preserves the industry’s ability to fight the issue again in a future case, but it also means the legal ambiguity surrounding non-custodial software remains firmly in place.