The United States Congress is currently the staging ground for a fundamental debate over the future of the digital economy, centered on the tension between national security surveillance and the preservation of open-source innovation. At the heart of this conflict is the "CLARITY Act" and its precursor, the Blockchain Regulatory Certainty Act (BRCA). While proponents argue these bills codify long-standing regulatory distinctions that protect software developers, critics—most notably Carole House, a former official on the White House National Security Council—warn that the legislation creates dangerous "loopholes" for illicit finance. This policy struggle hinges on a single, evocative principle: "Accountability follows power." The interpretation of this phrase will likely determine whether the U.S. remains a hub for decentralized technology or pivots toward a model of mandatory financial reintermediation.
The Legislative Landscape: CLARITY and the BRCA
The CLARITY Act, which recently passed the House of Representatives, represents one of the most significant attempts to provide a comprehensive regulatory framework for the digital asset ecosystem. Central to the bill is Section 109, a provision derived from the Blockchain Regulatory Certainty Act. This section seeks to provide a "safe harbor" for developers and providers of blockchain services who do not take control of consumer funds.
Unlike traditional financial regulations that often categorize entities based on their status—such as "bank" or "broker"—the BRCA-style provisions within the CLARITY Act establish a functional test. Under this test, a developer or service provider is deemed "non-controlling" if they lack the legal right or the independent, unilateral ability to initiate or execute transactions involving a user’s assets without that user’s specific approval.
This distinction is designed to protect three specific categories of actors:
- Software Developers: Those who write and publish code for decentralized protocols or self-custody wallets.
- Non-Custodial Service Providers: Entities that provide the interface or infrastructure for transactions but never touch the "private keys" that control the assets.
- Network Miners and Validators: Individuals or entities that provide the computational power to secure a decentralized network without acting as financial intermediaries for specific users.
The Critique of "Forced Reintermediation"
The opposition to these protections, articulated by Carole House and other national security hawks, rests on the premise that any powerful software system capable of moving value must have an identifiable intermediary. This "intermediary-by-design" philosophy suggests that the government should be able to compel a central party to monitor, report, and block user transactions.
Critics of this view argue that such a requirement is not merely about "accountability" but represents a radical departure from traditional American legal standards. If applied consistently, this logic would require every piece of software—from encrypted messaging apps to web browsers—to be built with a "backdoor" or a central kill switch. In the context of blockchain, this would effectively ban truly decentralized systems like Bitcoin, which operate specifically because they lack a central administrator.
The debate essentially boils down to two options for the future of U.S. tech policy:
- The BRCA Approach: Regulate the points of control (exchanges, custodial wallets) where intermediaries actually possess the power to stop money laundering and fraud.
- The Reintermediation Approach: Mandate that all software be redesigned to ensure a controllable intermediary exists, even if the technology’s primary value proposition is the absence of such a central point of failure.
A Chronology of Regulatory Precedent: FinCEN and the Bank Secrecy Act
The argument that the CLARITY Act creates a new "loophole" is challenged by a decade of existing federal guidance. The Financial Crimes Enforcement Network (FinCEN), the bureau within the Treasury Department responsible for administering the Bank Secrecy Act (BSA), has long maintained a distinction between "money transmitters" and "software providers."
- 2014 FinCEN Guidance: In an administrative ruling, FinCEN stated explicitly that the "production and distribution of software, in and of itself, does not constitute acceptance and transmission of value." This ruling established that simply giving someone the tools to move their own money does not make the tool-maker a financial institution.
- 2019 FinCEN Guidance: Under a different administration, FinCEN reaffirmed this position, noting that the application of money-transmission law depends on the "underlying activities" a person performs, rather than the labels or technology used.
- The Current Standard: Throughout both Democratic and Republican administrations, the prevailing standard has been that "control" is the trigger for regulation. A person who accepts a customer’s money and transmits it for them is an intermediary; a person who publishes software that allows a user to transact independently is not.
Proponents of the CLARITY Act argue that Section 109 is not a radical deregulation but a codification of this "regulatory common sense." By turning FinCEN’s administrative guidance into statutory law, Congress would provide the "certainty" needed for American developers to build without the fear of being arbitrarily classified as an unregulated bank.
Comparative Analysis: From Hawala to Visa
To understand the stakes, it is helpful to contrast decentralized software with traditional payment networks. Critics like House often compare decentralized protocols to "hawala" networks (informal value transfer systems) or established giants like Visa and Mastercard. However, blockchain advocates point out a fundamental technical difference.
Visa and Mastercard are centralized operators. They establish network rules, admit or exclude participating banks, monitor every transaction on their rails, and possess the unilateral power to deny access to their infrastructure. Hawala dealers, while informal, rely on a coordinated network of human agents who accept instructions and arrange transfers. In both cases, there is a "who" for the government to subpoena or regulate.
In contrast, a developer who contributes to an open-source project or publishes a self-custody wallet like MetaMask or Ledger does not possess comparable authority. Once the code is in the wild, the developer cannot "turn off" a user’s wallet or "censor" a transaction on the blockchain. Treating these developers like Visa is, according to proponents, like treating the author of an encrypted messaging app as a telecommunications carrier, or the creator of a web browser as the publisher of every website a user visits.
The Section 230 Analogy and the "Shadow Market" Risk
The debate has also drawn comparisons to Section 230 of the Communications Decency Act, the 1996 law that protected early internet service providers from being held liable for the content posted by their users. Critics argue that Section 230 was a "status-based" immunity that led to a lack of accountability for online harms.
However, a deeper analysis of the Section 230 history provides a cautionary tale for crypto regulators. When Congress added trafficking-related exceptions to Section 230 (via FOSTA-SESTA), the Government Accountability Office (GAO) found that instead of eliminating the illegal activity, the law caused platforms to move overseas. This fragmentation actually made it harder for law enforcement to gather evidence, as the activity migrated to less visible, less accountable foreign venues.
Blockchain advocates argue that imposing sweeping liability on U.S.-based developers will have the same effect:
- Jurisdictional Flight: Developers will move to regions with clearer protections (like the EU or Switzerland), depriving the U.S. of tax revenue and technological leadership.
- Loss of Visibility: If infrastructure is built entirely outside the U.S. regulatory perimeter, federal agencies will have less insight into global financial flows, not more.
- Innovation Chill: Small startups will be unable to afford the compliance costs of being treated as "financial institutions," leaving the market to a few entrenched monopolies.
Broader Implications: AI and the Financial Panopticon
Perhaps the most significant long-term impact of this debate concerns the development of Artificial Intelligence. As AI "agents" begin to perform economic tasks—such as purchasing server space or managing data portfolios—the question of who is responsible for their "autonomous" transactions becomes paramount.
If the "reintermediation" model wins, every AI developer could be held presumptively liable for every transaction their AI agent performs, unless they build in a way that allows for total government surveillance and control. This could lead to what civil liberties groups call a "financial panopticon," where no economic activity can occur without a government-approved intermediary watching in real-time.
Conversely, the BRCA approach suggests that liability should attach to conduct. If an AI developer uses an agent to commit fraud or evade sanctions, they should be prosecuted under existing criminal laws. However, the mere act of creating an autonomous agent should not, by itself, make the developer a regulated financial intermediary.
Conclusion: The Path Forward for U.S. Policy
The nonpartisan Congressional Research Service (CRS) has noted that the CLARITY Act does not abolish accountability; rather, it shifts it to where it is most effective. The bill creates new categories of federally regulated crypto intermediaries—including digital commodity exchanges, brokers, and dealers—and subjects them to the Bank Secrecy Act. These businesses would be required to implement anti-money laundering (AML) programs, monitor suspicious activity, and comply with U.S. sanctions.
By placing extensive obligations on businesses that control customer assets while protecting those who merely provide software, the CLARITY Act attempts to strike a balance between security and liberty. The "Accountability follows power" principle suggests that we should regulate the gatekeepers, not the architects of the gate.
As the bill moves through the legislative process, the outcome will signal whether the United States intends to uphold the liberal values of an open society or move toward a more restrictive, surveillance-heavy model of digital commerce. For the developers building the next generation of the internet, the "certainty" promised by the BRCA is not just a regulatory preference—it is a prerequisite for the survival of decentralized innovation on American soil.
