US Prosecutors Seek Changes to CLARITY as Voting Window Tightens: Report

US law enforcement advocacy groups are asking the White House to revise provisions in the Senate’s proposed Digital Asset Market Clarity (CLARITY) Act, specifically targeting language that would affect how “developer” guidance is handled under the bill’s Blockchain Regulatory Certainty Act (BRCA) component. The push comes as Congress heads toward a month-long recess, tightening the timeline for any legislative movement.

According to a Tuesday report by Politico, the National Association of Assistant US Attorneys and the National District Attorneys Association sent a letter to the White House urging changes to BRCA provisions related to developers. The groups want adjustments to guidelines that, as described in the reporting, would not require developers to “create, expand, or modify criminal liability under Federal law.”

Key takeaways

• Law enforcement groups have proposed edits to BRCA language in the CLARITY Act, with a focus on how developer-related guidance intersects with criminal liability.
• White House crypto adviser Patrick Witt said the proposed language is far from the Trump administration’s position and suggested the effort was not the product of “productive negotiations.”
• Senator Catherine Cortez Masto is reported to be pressing the White House to address BRCA provisions before any Senate vote.
• Senate Majority Leader John Thune had not scheduled a CLARITY vote before the chamber’s August recess as of Wednesday, narrowing the odds of final passage soon.

Law enforcement groups press for developer-language revisions

The Politico report says the letter was sent by two US prosecutors’ organizations to the White House, requesting modifications to BRCA provisions inside the CLARITY Act. The specific change outlined in the reporting centers on language that would constrain how guidelines regarding developers might affect federal criminal liability.

While the letter’s request is framed around developer-related provisions, the underlying implication is broader: how Congress chooses to draw lines between regulatory guidance and criminal exposure for participants in the digital asset ecosystem. For developers and related technical contributors, the difference between “regulatory guidance” and “criminal liability” is not merely academic—it can influence how legal teams structure compliance programs and how risk is assessed for future product changes.

The timing also matters. Politico reported the proposals with only days left before the Senate moves toward a state-work period and a month-long recess, a window that tends to limit complex floor negotiations on contested bills.

White House response raises questions on negotiation dynamics

After coverage of the proposed changes surfaced, White House crypto adviser Patrick Witt commented on the matter via social media. As reported, Witt said the provisions were “not even close” to the Trump administration’s position and suggested the changes were not the result of “productive negotiations.”

That response signals the White House may view the law enforcement groups’ requests as misaligned with the administration’s drafting approach—or as an attempt to shift the bill without reaching a common negotiating position first.

Separately, Politico reported that Senator Catherine Cortez Masto has been pushing the White House to address BRCA provisions before any potential vote. If her position reflects broader Democratic concerns, the White House’s willingness to adjust BRCA language could determine whether CLARITY can clear remaining hurdles.

Ethics fight and legislative schedule complicate passage

Beyond the developer-language dispute, the CLARITY Act has faced pushback from many Democrats tied to ethics rules in the bill, including rules connected to US President Donald Trump’s crypto investments. The report cited that Trump’s investments netted him $1.4 billion in 2025.

As of Wednesday, Senate Majority Leader John Thune had not scheduled a vote before the Senate breaks for state work periods. According to the schedule cited in the reporting, state work periods are expected to run from Aug. 7 to Sept. 14, leaving a short stretch for any procedural steps that often determine whether major legislation can reach the floor.

One procedural reality highlighted by political observers is that even if CLARITY were ready to be taken up immediately, finishing the process before the recess could be difficult. Anne Kelley, a partner at Mercury Strategies, wrote on X that completing the required steps—cloture, an amendment process, a second cloture, and up to 30 hours of debate—would be extremely challenging without unanimous consent to waive process, which she said is rare on contested bills.

For investors and market participants, that procedural friction can matter as much as the policy itself. When deadlines compress and ethics and developer-language debates remain unresolved, the bill’s direction can become harder to predict, and timelines for regulatory clarity may slip—regardless of how markets initially react to policy headlines.

Why BRCA’s regulator-shift plan remains central

One of the major goals of the CLARITY Act, as described in the reporting, is to change the regulatory purview over digital assets away from the US Securities and Exchange Commission (SEC) and toward the Commodity Futures Trading Commission (CFTC). The CFTC is described as having fewer enforcement and oversight tools and resources compared with the SEC, while both agencies are reported to be understaffed at the leadership level—specifically noting only one CFTC chair and three SEC commissioners.

That regulator-shift is one of the core reasons CLARITY is likely to remain controversial. Different agency mandates can translate into different approaches to enforcement priorities, compliance expectations, and the practical meaning of “market structure” rules for tokens and exchanges. As a result, debates over “developer” provisions and ethics rules are not separate from the regulatory center of gravity—they interact with how policymakers think the bill should function and who should have authority.

It also raises an immediate question for readers: if BRCA language—particularly around developer-related liability constraints—is being negotiated through law enforcement input, what does that mean for the broader regulatory architecture lawmakers are trying to establish? For developers and firms building on-chain infrastructure, the answer could shape both legal exposure and how they interpret future compliance requirements as CLARITY moves (or stalls).

With the Senate calendar narrowing and political disagreements persisting, the next developments to watch are whether the White House signals openness to BRCA edits and whether Senate leadership can align procedural timing with remaining ethics and policy disputes. Until then, CLARITY’s fate may hinge less on consensus about the end goal and more on whether negotiators can reconcile competing views fast enough to move the bill before recess complicates the process again.