House leaders put three digital-asset bills on a July agenda

The leaders of two U.S. House committees and Republican House leadership announced on July 3, 2025 that the chamber would devote the week beginning July 14 to three digital-asset bills. The planned “Crypto Week” put stablecoin regulation, crypto-market structure and a proposed federal central-bank-digital-currency prohibition onto one coordinated legislative agenda.

The announcement came from House Financial Services Committee Chairman French Hill, House Agriculture Committee Chairman Glenn “GT” Thompson and House leadership. It named the Digital Asset Market Clarity Act of 2025, or CLARITY Act; the Anti-CBDC Surveillance State Act; and the Senate’s GENIUS Act.

That was consequential because the package reached beyond a single regulatory dispute. It joined rules for private payment stablecoins, a proposed division of digital-commodity oversight between the Securities and Exchange Commission and Commodity Futures Trading Commission, and restrictions on a Federal Reserve-issued CBDC. The plan signaled that House leaders intended to move several foundational questions together before the August recess.

Three measures, three different policy questions

The GENIUS Act, S. 1582, concerned the regulation of payment stablecoins. By July 3, it was the most advanced measure in the group: the Senate had passed the amended bill 68–30 on June 17. The official roll call recorded 68 yeas, 30 nays and two senators not voting. House consideration was still required; Senate passage had not made the proposal law.

The CLARITY Act, H.R. 3633, addressed a wider market-structure problem. Its official title described a system for regulating the offer and sale of digital commodities through the SEC and CFTC. The House Financial Services and Agriculture committees had each reported amended versions, and the reported bill was committed to the Committee of the Whole House on June 23. The July 3 announcement therefore moved the measure from committee work toward an anticipated floor test, without changing its legal status.

The Anti-CBDC Surveillance State Act, H.R. 1919, took a different approach to public digital money. The committee-reported text would prohibit Federal Reserve Banks from directly or indirectly issuing a CBDC to individuals and would restrict the Federal Reserve Board and Federal Open Market Committee from testing, developing or using one for monetary policy. The House report also included minority views, underscoring that the proposal was contested rather than settled policy.

A schedule was not a result

The verified development on July 3 was an agenda commitment. No floor vote occurred as part of the announcement, none of the three measures became law on July 3, and the statement did not guarantee passage or specify final vote margins. Floor procedure, amendments, intra-party disputes and negotiations with the other chamber could still alter the sequence or substance.

That distinction matters for interpreting the institutional signal. House leaders were not merely scheduling an industry hearing or issuing a general policy statement. They were publicly tying leadership attention to three named bills that had already completed significant committee or Senate steps. But the announcement itself created no stablecoin license, reassigned no agency jurisdiction and imposed no CBDC prohibition.

Why the package mattered on July 3

For crypto companies, banks, exchanges and protocol developers, the package gathered several long-running sources of uncertainty into a single prospective floor window. Payment-token issuers were watching reserve and supervisory rules; trading platforms were watching the proposed SEC-CFTC boundary; privacy advocates and central-bank researchers were watching the CBDC restrictions.

The grouping also clarified the House majority’s strategy: advance a Senate-passed stablecoin bill alongside two House-originated measures. That offered a possible route for one bill to move directly toward presidential consideration while the others, if passed, would still require Senate action.

The evidence supports calling July 3 a legislative scheduling milestone, not a regulatory breakthrough already in force. Any account of later votes or enactment belongs to later dates and should not be projected backward into what the announcement established.