The debate over the future of digital asset regulation in the United States has reached a critical juncture as lawmakers and policy experts clash over the extent of liability that should be imposed on software developers. At the heart of this dispute is the "Creating Legal Accountability for Regulating Intermediaries and Transparent Yield Act," or CLARITY Act, and its incorporation of the Blockchain Regulatory Certainty Act (BRCA). While proponents argue that the legislation provides necessary protections for those who write code but do not control assets, critics contend that such protections create dangerous loopholes that could undermine national security and financial oversight. The central philosophical disagreement hinges on a singular, potent slogan: "Accountability follows power."
The legislative battle focuses on Section 109 of the House-passed version of the CLARITY Act. This section establishes a functional test to determine whether a person or entity qualifies as a "money transmitter" under federal law. Specifically, it posits that a developer should only be held liable as a financial intermediary if they possess the legal right or the unilateral, independent ability to control, initiate, or effectuate transactions involving a user’s assets. This distinction attempts to separate those who provide the "pipes" of the digital economy—software authors and infrastructure providers—from those who actually manage the money flowing through them.
The Legislative Context and the BRCA Framework
The CLARITY Act represents one of the most significant attempts by the U.S. House of Representatives to bring order to the often-chaotic cryptocurrency sector. By integrating the BRCA, the bill seeks to codify long-standing regulatory interpretations that have existed within the Treasury Department’s Financial Crimes Enforcement Network (FinCEN). Since 2014, FinCEN has maintained a distinction between the production of software and the transmission of value. In its 2014 administrative ruling, the agency stated that the "production and distribution of software, in and of itself, does not constitute acceptance and transmission of value."
This position was further refined in 2019 guidance, which clarified that the application of the Bank Secrecy Act (BSA) depends on the underlying activities performed by a person rather than the labels attached to the technology they use. Proponents of the CLARITY Act argue that codifying these principles is not a radical shift but rather "regulatory common sense." They suggest that without these protections, the United States risks a "chilling effect" on innovation, where developers might be held responsible for the actions of any individual who happens to use their open-source code for illicit purposes.
However, critics like Carole House, a former member of the White House National Security Council, argue that this approach is insufficient. House’s critique centers on the idea that "accountability follows power" and that powerful software systems must have an identifiable intermediary that the government can compel to monitor and control users. From this perspective, the absence of a central point of control is not a feature of decentralization, but a "loophole" that bad actors can exploit to evade sanctions and launder money.
A Chronology of Digital Asset Regulation and Policy
To understand the current friction, one must look at the timeline of how the U.S. government has approached software and financial intermediation over the last three decades:
- 1996: The enactment of Section 230 of the Communications Decency Act. This provided a "safe harbor" for internet service providers and platforms, ensuring they were not held liable for the content posted by third parties. It is widely credited with allowing the modern internet to flourish.
- 1997: The Clinton administration releases the "Framework for Global Electronic Commerce." This directive urged the federal government to recognize the decentralized nature of the internet and cautioned against "inflexible and highly prescriptive regulations" that might stifle new electronic payment systems.
- 2014: FinCEN issues its first major ruling regarding virtual currency software, establishing that developers who do not engage in the exchange or transmission of currency are not "money services businesses" (MSBs).
- 2019: FinCEN releases comprehensive guidance on virtual currency business models, reaffirming that MSB status is a functional determination based on control over assets.
- 2023-2024: The CLARITY Act and the BRCA gain momentum in the House of Representatives, passing with bipartisan support as part of a broader push to define the roles of the SEC and CFTC in the crypto space.
The Functional Test vs. Status-Based Regulation
The core of the CLARITY Act’s developer protection is its "functional test." Unlike "status-based" regulation, which might regulate an entity simply because it identifies as a "crypto company," the functional test asks: Does this person possess the unilateral ability to control the financial transaction?
This distinction is vital when comparing decentralized systems to traditional financial networks like Visa or Mastercard. Traditional networks are managed by identifiable operators who establish rules, admit or exclude participants, and have the power to deny access to their infrastructure. Similarly, "Hawala" networks—traditional informal value transfer systems—rely on a coordinated network of human agents who accept instructions and arrange transfers.
In contrast, a developer who publishes a self-custody wallet or contributes to an open-source protocol like Bitcoin does not possess the same authority. Once the code is released, the developer often has no way to "turn off" the software for a specific user or to "freeze" assets held in a decentralized smart contract. Proponents of the BRCA argue that imposing financial institution-style obligations on these developers is equivalent to treating the creator of a web browser as the publisher of every website a user visits, or holding the developer of encrypted messaging software liable as a telecommunications carrier.
The Section 230 Analogy and the Risks of Over-Regulation
The debate frequently invokes Section 230 of the Communications Decency Act as a cautionary tale. Critics of the CLARITY Act suggest that broad protections for developers could lead to the same types of "lawless" environments they associate with early social media. However, legal analysts point to the Government Accountability Office (GAO) findings regarding recent exceptions to Section 230, such as those related to sex trafficking (SESTA-FOSTA).
The GAO found that after these exceptions were implemented, many platforms moved overseas or into the "dark web," making it harder for law enforcement to gather evidence. The illicit activity did not cease; it simply migrated to venues with less visibility and zero accountability. Proponents of the CLARITY Act argue that the same logic applies to crypto: if the U.S. imposes impossible-to-meet surveillance requirements on decentralized infrastructure providers, those providers will move to jurisdictions outside of U.S. reach, leaving law enforcement with fewer tools, not more.
Broader Implications: From Crypto to Artificial Intelligence
The outcome of the CLARITY Act debate will likely set a precedent that extends far beyond the realm of digital finance. As artificial intelligence (AI) becomes more integrated into the global economy, the question of developer liability is becoming paramount. If a developer creates an autonomous AI agent that a user then employs for an illegal transaction, should the developer be held responsible?
The "accountability follows power" principle suggests that if an AI developer maintains control over the agent or directs its transactions, they should be liable. However, if the developer merely publishes the underlying code for others to run on their own hardware, holding them responsible for every autonomous action performed by the user would represent a radical shift in legal theory. Critics of the current legislative language warn that protections for crypto developers might "leak" into the AI space, while supporters argue that these protections are essential to prevent the government from mandating that all software include "backdoors" or "kill switches."
The Financial Panopticon vs. The Open Society
Ultimately, the disagreement over the CLARITY Act is a clash of visions for the future of the internet. One vision, described by critics of the bill, is an online financial system where every piece of technology must contain an intermediary that the government can compel to identify, monitor, and control its users. Proponents of this view see it as the only way to maintain national security in a digital age.
The opposing vision, championed by the authors of the BRCA and the CLARITY Act, is one of "forced reintermediation" vs. "permissionless innovation." They argue that the absence of centralized control is not a defect but a security feature—a way to protect users from private monopolies, data breaches, and government overreach. They contend that while a person who commits fraud or launders money should always be held answerable for their conduct, responsibility cannot follow power that a person does not actually possess.
As the CLARITY Act moves through the legislative process, the stakes remain high. The decision will determine whether the United States continues to follow the pro-innovation, decentralized framework that allowed the early internet to flourish, or whether it will pivot toward a more centralized, surveillance-heavy model for the next generation of financial and computational technology. For now, the "functional test" remains the primary mechanism by which Congress hopes to balance the need for law enforcement with the preservation of technological freedom.
