The United States Senate is poised for a pivotal vote on the Clarity Act, a landmark legislative package designed to establish a comprehensive framework for the burgeoning digital asset industry. In a high-stakes effort to garner the 60-vote supermajority required to overcome potential procedural hurdles and ensure passage, drafters have introduced significant, last-minute revisions to the Blockchain Regulatory Certainty Act (BRCA). These changes, while preserving critical protections for non-controlling blockchain developers, represent a tactical retreat from previously sought shields against criminal liability under 18 U.S.C. § 1960.
The revisions mark a delicate compromise in a legislative process that has spanned years. Advocacy groups, most notably the non-profit organization Coin Center, have long championed the BRCA as a necessary bulwark against regulatory overreach. While the amended text retains the core mission of the bill—to clarify the legal status of developers who do not exercise custody over user funds—the removal of explicit protections against specific criminal statutes introduces a new layer of ambiguity that developers and legal scholars will likely navigate for years to come.
The Legislative Objective: Defining Custody and Control
At the heart of the BRCA is a fundamental question: who constitutes a "money transmitter" in an ecosystem built on decentralized, peer-to-peer software? Under current federal law, entities that take control of user funds are generally subject to stringent anti-money laundering (AML) and know-your-customer (KYC) requirements under the Bank Secrecy Act (BSA).
However, the rapid rise of decentralized finance (DeFi) and self-custodial software has created a friction point. Developers who write and publish code—but do not participate in the transmission of assets or hold user keys—have increasingly found themselves in the crosshairs of regulators and prosecutors. By codifying a "control-based" approach, the BRCA aims to differentiate between centralized intermediaries, who function like traditional banks, and software developers, who merely provide the infrastructure for others to transact independently.
The revised language of Section 10604(c) of the bill clarifies that a qualifying "non-controlling blockchain developer or provider" cannot be categorized as a money transmitting business under 31 U.S.C. § 5330, nor as a money transmitter under FinCEN regulations, nor as a financial institution under Title 31. This statutory clarity is intended to provide a "safe harbor" for software development, self-custody tools, and infrastructure activities, effectively enshrining the principles articulated in FinCEN’s 2019 guidance into federal law.
Chronology of a Regulatory Struggle
The trajectory of the BRCA has been defined by a series of aggressive enforcement actions that have shocked the developer community. The following timeline outlines the evolution of this legislative effort:
- 2019: FinCEN issues guidance clarifying that software providers who do not exercise "control" over funds generally fall outside the scope of money transmission regulation.
- 2022: The Department of Justice (DOJ) ramps up investigations into software developers, leading to the indictment of individuals associated with privacy-enhancing protocols.
- 2023: Legal proceedings against the developers of Tornado Cash and Samourai Wallet highlight the vulnerabilities of open-source contributors, as prosecutors utilize broad interpretations of federal law to argue that the creation of privacy tools constitutes illegal money transmission.
- Early 2024: The DOJ, under the guidance of then-Deputy Attorney General Todd Blanche, issues a memo cautioning against pursuing digital-asset cases solely premised on "unwitting" regulatory violations, though this memo leaves significant gaps regarding criminal liability.
- October 2024: Ahead of the Senate vote, the Clarity Act undergoes final revisions, stripping the BRCA of its explicit protections against 18 U.S.C. § 1960 to secure broader support for the bill.
The 18 U.S.C. § 1960 Dilemma
The most contentious aspect of the current revision is the removal of explicit immunity from 18 U.S.C. § 1960. This statute, which criminalizes the operation of an unlicensed money transmitting business, has been the primary vehicle for federal prosecutions against developers.
The statute contains three subsections. Subsections (A) and (B) are largely tied to state licensing and federal registration requirements. By establishing in the BRCA that non-controlling developers are not subject to these registration requirements, the bill theoretically builds a strong defense against prosecutions brought under these two subsections; it is difficult for a prosecutor to argue that a developer is "unlicensed" if the law explicitly states they are not required to hold a license in the first place.
However, subsection (C) of Section 1960 remains the "wild card." Unlike the other subsections, (C) is not strictly contingent upon a failure to register. It is a broad, ambiguous provision that has allowed prosecutors to pursue criminal charges even when the regulatory status of the defendant is in question. The DOJ’s explicit decision to maintain the ability to use subsection (C) in the Blanche memo has left the open-source community in a state of continued apprehension.
Broader Economic and Legal Implications
The implications of this legislative shift are far-reaching. Proponents of the bill argue that even without the explicit criminal shield, the statutory recognition of the "control-based" principle is a victory. It establishes a baseline of regulatory sanity that will likely discourage the most aggressive forms of administrative overreach. If the bill passes, developers will have a clear, federal mandate to point to when faced with state-level or agency-level inquiries regarding their registration status.
Conversely, critics and legal experts note that the remaining ambiguity serves as a "chilling effect" on innovation. If a developer remains at risk of being charged under the catch-all provision of 18 U.S.C. § 1960(b)(1)(C), they may be disinclined to publish code that could be misused by third parties. This creates a risk-averse environment where only those with the financial resources to litigate against the federal government can afford to participate in the open-source ecosystem.
The judiciary is now expected to play a decisive role in resolving these tensions. Litigation, such as the case brought by Coin Center fellow Michael Lewellen against the DOJ, seeks a declarative judgment to confirm that the development of non-custodial software is not criminal conduct. As the Clarity Act moves toward a vote, this judicial path becomes the secondary, yet arguably more vital, frontier for developers seeking to ensure that software development remains protected speech and activity.
Looking Ahead: The Work Remaining
Regardless of whether the Clarity Act passes with the revised BRCA, the legislative and legal battles are far from over. The crypto-asset industry, represented by various advocacy groups, remains committed to pushing for a comprehensive, airtight protection against criminal liability.
The industry argues that the principle of "control" should be the universal standard across both regulatory and criminal law. If an individual does not possess the technical ability to move, freeze, or hold another person’s funds, they should not be treated as a financial intermediary. As the Senate prepares to cast its votes, the legislative record will reflect a significant step toward this goal, even as the specter of criminal liability continues to loom over the infrastructure of the future internet.
For now, the focus shifts to the Senate floor. The outcome of this vote will serve as a bellwether for how the United States intends to balance the demands of national security and anti-money laundering enforcement against the necessity of preserving a neutral, innovative environment for software development in the digital age.
