Software developer Michael Lewellen has escalated his legal battle against the United States Department of Justice (DOJ) by filing a formal reply brief in the United States Court of Appeals for the Fifth Circuit this past Monday. The case, which centers on the interpretation of 18 U.S.C. § 1960, represents a pivotal moment for the burgeoning cryptocurrency development sector. At the heart of the dispute is Lewellen’s project, "Pharos," a non-custodial software platform designed to facilitate decentralized crowdfunding. Lewellen is seeking a declaratory judgment to establish that the act of publishing and operating such software does not classify a developer as an unlicensed money-transmitting business under federal criminal statutes.
The appeal arrives at a time of significant regulatory uncertainty. With the failure of the Blockchain Regulatory Certainty Act (BRCA) to pass through Congress, the legal landscape for software developers has become increasingly precarious. By challenging the DOJ’s broad application of anti-money laundering (AML) laws to neutral software development, Lewellen aims to secure a judicial precedent that would shield developers from what he characterizes as the "credible threat of prosecution" currently looming over the industry.
Chronology of the Legal Conflict
The roots of this litigation trace back to the Northern District of Texas, where Lewellen initially filed a pre-enforcement challenge against the DOJ. The move was prompted by growing concerns within the developer community regarding the DOJ’s aggressive stance on cryptocurrency tools, specifically those facilitating peer-to-peer transactions.
The situation intensified following the issuance of a memorandum by then-Deputy Attorney General Todd Blanche. This internal policy document addressed the DOJ’s enforcement priorities regarding cryptocurrency, which the district court subsequently cited as evidence that Lewellen lacked standing to sue, arguing there was no immediate, credible threat of prosecution. Finding that the plaintiff had not alleged a specific enforcement action taken against him, the district court dismissed the case. Lewellen’s current appeal to the Fifth Circuit argues that the lower court fundamentally misunderstood the purpose of a pre-enforcement challenge: to clarify one’s legal standing and obligations before a potential criminal indictment occurs, rather than waiting for the state to act.
The Conflict Between FinCEN and the DOJ
A central tension in the case involves the disparate interpretations of money transmission by different federal agencies. In 2019, the Financial Crimes Enforcement Network (FinCEN) issued guidance clarifying that mere software development does not constitute money transmission. The guidance emphasizes that the core element of money transmission is the custody and control of customer funds. Under this framework, developers who create non-custodial tools—where the software enables interaction between parties without the developer ever touching or controlling the underlying assets—should fall outside the scope of money-transmitting business (MSB) regulations.
However, the DOJ has consistently adopted a more expansive, and at times contradictory, interpretation. In the high-profile prosecutions of the developers behind the Samourai Wallet and the Tornado Cash privacy tool, the DOJ pursued charges under 18 U.S.C. § 1960 despite arguments that the defendants never exercised custody over user assets. The DOJ’s position has effectively sidelined the FinCEN guidance, treating it as non-authoritative in the context of criminal enforcement. This divergence has created a "regulatory trap," where developers are caught between guidance suggesting their actions are lawful and a prosecutorial practice that treats their code as a criminal enterprise.
Core Arguments Presented in the Reply Brief
In his latest filing, Lewellen articulates four primary legal arguments to support his position that he is entitled to seek declaratory relief.
First, Lewellen asserts that he has standing to sue because the DOJ’s interpretation of the law is sufficiently broad to encompass his specific conduct. He argues that he should not be forced to endure an investigation or face indictment simply to challenge a statutory interpretation that effectively criminalizes his profession. He notes that the Fifth Circuit must accept his factual allegations regarding the functionality of Pharos as true during this stage of the proceedings.
Second, he cites the ongoing prosecutions of Tornado Cash and Samourai Wallet developers as objective proof that his fear of prosecution is reasonable. The DOJ has countered that Lewellen cannot be both "law-abiding" and simultaneously fearful of prosecution, suggesting that such fear is generalized. Lewellen’s brief rebuts this, arguing that the government has demonstrated a willingness to "overread" the law, and that he does not need to mimic the exact activities of those previously prosecuted to fall within the crosshairs of the DOJ’s expansive reading of § 1960.
Third, Lewellen highlights the DOJ’s persistent refusal to provide a formal "disavowal of prosecution." While the government has stated in court that "the mere creation and launching of software is not a crime," it has failed to clarify whether it considers the publishing of non-custodial software without registration to be a criminal act. By refusing to confirm that such conduct does not constitute operating an unlicensed money-transmitting business, the DOJ maintains a state of perpetual legal jeopardy for developers.
Finally, Lewellen attacks the reliance on the Blanche memo as a shield against judicial oversight. He argues that the memo is merely an expression of internal, discretionary enforcement priorities that can be revoked or ignored at any moment. Furthermore, because the memo was issued after the litigation commenced, it cannot retroactively cure the legal standing of the complaint.
Broader Implications for the Technology Sector
The outcome of this case holds significant implications for the future of decentralized technology in the United States. If the Fifth Circuit sides with the DOJ, it effectively confirms that the executive branch has the authority to criminalize the publication of software based on how users might employ that code, regardless of whether the developer maintains custody of funds or facilitates the movement of money in the traditional sense.
Industry analysts observe that this could lead to a "chilling effect" on open-source development. Many programmers may choose to avoid building tools that interact with financial protocols if they face a credible risk of being labeled an unlicensed MSB. This legal uncertainty could force innovation to migrate to jurisdictions with clearer, more developer-friendly frameworks, potentially depriving the U.S. of a competitive edge in the global digital economy.
Moreover, the case underscores a growing legislative void. The failure of the Clarity Act and the limited scope of the proposed BRCA have left the courts as the primary venue for defining the boundaries of digital asset regulation. As Coin Center and other advocacy groups have noted, the current statutory language of 18 U.S.C. § 1960 was drafted in an era that predates modern decentralized finance, and applying it to software code requires a stretch that many legal scholars find problematic.
Conclusion and Future Outlook
As the case moves forward, the focus will remain on whether the federal judiciary will intervene to check the DOJ’s expansive use of criminal statutes against software developers. The Fifth Circuit’s decision will likely serve as a foundational precedent for how anti-money laundering laws interact with the First Amendment rights of coders. For now, Michael Lewellen remains in a state of legal limbo, waiting to determine if his contribution to the crowdfunding ecosystem is a protected act of technological innovation or a violation of federal criminal law. The resolution of this matter will undoubtedly signal to the developer community whether the United States will continue to embrace an environment of innovation or prioritize a restrictive, enforcement-heavy approach to digital infrastructure.
