CryptaCount
EN
EnglishENDeutschDEEspañolESFrançaisFRItalianoIT日本語JA한국어KONederlandsNLPolskiPLPortuguêsPT
Log in Start Free

US Law Enforcement Drops Opposition to CLARITY Act: What Firms Should Watch

CryptaCount Editorial · · 7 min read
AML / KYC / LICENSING US Law Enforcement Drops Opposition toCLARITY Act: What Firms Should Watch

A significant political barrier to the CLARITY Act cleared on 4 July 2026, when the Major County Sheriffs of America (MCSA) told the Senate Banking Committee it had shifted from opposition to neutral on the bill. The change, triggered by partial concessions on Section 604's DeFi liability shield, brings the legislation one step closer to a full Senate floor vote — with real consequences for how accounting firms and compliance teams model regulatory risk around digital asset clients.

US Law Enforcement Drops Opposition to CLARITY Act: What Firms Should Watch

What the CLARITY Act Contains and Why It Stalled

Market structure scope

The CLARITY Act is a broad US crypto market structure bill that has cleared the Senate Banking Committee, largely along party lines, and has been awaiting a full Senate vote since May. It carries bipartisan support in principle, but its Senate path has been blocked by two separate pressure points: banking sector lobbying over stablecoin provisions, and law enforcement concerns over DeFi liability language.

The stablecoin flashpoint

Banking groups have argued that certain stablecoin provisions in the bill could function like an unregulated deposit product, potentially pulling trillions of dollars away from the traditional banking system. That fight remains unresolved and continues to be the bill's largest structural obstacle in the upper chamber.

Section 604: The DeFi Liability Clause at Issue

What Section 604 does

Section 604 incorporates language from the Blockchain Regulatory Certainty Act. Its purpose is to protect software developers and protocol operators from legal liability for illicit activity carried out by third parties using their decentralized platforms. Proponents argue this kind of safe harbor is essential for US-based DeFi development to remain competitive globally.

Why the MCSA originally objected

In a letter dated 14 May, the MCSA warned that Section 604 as originally drafted could create a structural loophole. The concern was specific: if developers cannot be held liable for how their platforms are used, law enforcement agencies investigating crypto-facilitated fraud, ransomware, narcotics trafficking, terrorism financing, and child exploitation could find their legal tools significantly weakened. The MCSA president, Bob Gualtieri, argued that state and local agencies investigate these crimes daily and need the authority to trace illicit proceeds and recover assets.

What changed

According to the MCSA's letter to Senate Banking Committee chair Tim Scott and Senator Elizabeth Warren, some of its May concerns regarding Section 604 were addressed in subsequent negotiations. The MCSA has not withdrawn its broader policy positions but no longer formally opposes the bill's passage. That is a meaningful distinction in legislative terms: neutral is not endorsement, but it removes a named obstacle that commentators had flagged as one of the more credible roadblocks to floor consideration.

Outstanding MCSA Demands

Section 309 and the Treasury DeFi study

The MCSA has attached conditions to its neutrality. Its central remaining ask is that the bill be amended so that state and local law enforcement agencies are explicitly included in Section 309. That section requires the Treasury Department to study decentralized finance and associated illicit finance risks. As the bill currently stands, the MCSA argues that the study's scope and the resulting policy recommendations could be shaped without meaningful input from the agencies that handle the majority of ground-level crypto crime investigations.

Resources, training, and technology

Beyond legislative text, the MCSA is pressing Congress to fund training, technology, and operational partnerships for state and local agencies dealing with digital asset-enabled crime. The argument is that federal frameworks that impose new analytical obligations — or that shift liability away from protocol developers — need to be matched by commensurate investment in investigative capacity at the state level. That request falls outside the bill's current text and would likely need separate appropriations action.

Legislative Timeline and What Comes Next

Senators supporting the CLARITY Act are actively working to bring it to a floor vote this month, with the stated aim of passing the legislation before the US midterm elections in November. The removal of MCSA opposition is being read by bill supporters as a meaningful clearing of the path, though the stablecoin banking dispute remains the dominant near-term obstacle.

For compliance and accounting professionals, the relevant watch points are: whether Section 604's final language preserves or narrows the developer liability shield; how Section 309's Treasury study is scoped; and whether any floor amendments introduce new AML obligations on DeFi protocols, custodians, or intermediaries that would translate into reporting or record-keeping requirements for clients.

Firms that rely on robust crypto accounting software workflows need to track these developments closely. Any expansion of AML obligations on DeFi participants — or any clarification of developer liability — will reshape how transactions on decentralized protocols are classified, documented, and reported. Digital asset accounting software configurations may need to reflect new counterparty status categories if the bill imposes licensing or registration requirements on previously unregulated entities.

AML and Compliance Implications for Accounting Firms

DeFi transaction classification

If Section 604 passes in its current form, developers of non-custodial protocols would retain significant liability protection. For accounting and audit teams, that means the compliance burden for transactions flowing through those protocols stays with the end user or the intermediary — not the protocol itself. Firms advising clients with DeFi exposure should document that analysis now, before final legislative text is settled.

AML monitoring thresholds

The MCSA's push to include state law enforcement in the Treasury's DeFi risk study suggests that future AML guidance in this area may reflect a broader set of investigative priorities than a purely federal lens would produce. Firms building or reviewing AML monitoring frameworks for crypto bookkeeping software integrations should treat this as a signal that the illicit finance risk taxonomy for DeFi is still being written — and that state-level enforcement patterns will likely influence it.

For broader context on how US authorities are approaching sanctions and illicit finance risk in digital assets, see our coverage of OFAC SDN cryptocurrency addresses and compliance priorities and the Huione Group illicit marketplace and stablecoin AML risk analysis. Both illustrate how enforcement agencies are already operationalizing digital asset tracing well ahead of legislative clarity on DeFi liability.

US Law Enforcement Drops Opposition to CLARITY Act: What Firms Should Watch

FAQs

What does the MCSA shifting to neutral actually mean for the CLARITY Act's prospects?

It removes a named opponent from the public record. The MCSA had been cited by bill supporters as one of the more credible obstacles to Senate floor consideration. Neutral status does not guarantee passage, but it eliminates a specific lobbying counterweight that could have been used to justify further delay.

What is Section 604 and why does it matter for compliance teams?

Section 604 incorporates the Blockchain Regulatory Certainty Act, which would protect DeFi protocol developers from liability for how third parties use their platforms. For compliance purposes, this affects how firms assign counterparty risk on DeFi transactions. If developers are shielded, the compliance obligation sits elsewhere in the chain, which has direct consequences for transaction documentation and AML monitoring.

Does the CLARITY Act create any new reporting obligations for accounting firms or their clients?

The bill's final text is not yet settled. Current proposals focus on market structure and developer liability rather than directly creating new tax reporting obligations. However, if the bill imposes registration or licensing requirements on previously unregulated DeFi participants, that could trigger new counterparty due diligence and record-keeping requirements. Firms should monitor floor amendments carefully.

What is Section 309 and why is the MCSA focused on it?

Section 309 requires the Treasury Department to study DeFi and illicit finance risks. The MCSA wants state and local law enforcement explicitly included in that study's scope, arguing that federal-only analysis would miss the ground-level patterns that local agencies observe in crypto-related fraud, trafficking, and ransomware investigations.

When could the CLARITY Act become law?

Supporters are targeting a Senate floor vote in July 2026, ahead of the November midterm elections. The stablecoin banking dispute remains the primary obstacle. Even if the Senate passes the bill, House reconciliation and presidential signature would follow before it becomes law.

Source: Cointelegraph

US#defiGeneralProposedAML/KYC & Licensing

Related articles

AML/KYC & Licensing
AI Governance in Compliance: The Accountability and Control Gap Regulators Are Already Watching
AML/KYC & Licensing
US Senator Proposes Ethics Rule Barring Officials From Issuing Digital Assets
AML/KYC & Licensing
Five Crypto Financial Crime Typologies for FI Compliance Programs
AML/KYC & Licensing
Cross-Chain Bridge AML Risk: $540M Laundered Through RenBridge