On August 9, 2021, two objections in the U.S. Senate blocked unanimous consent for a bipartisan amendment intended to narrow cryptocurrency tax-reporting language in H.R. 3684, the infrastructure bill. The amendment was not defeated by a recorded vote. It failed to be adopted because the Senate could proceed at that stage only if no senator objected.

The immediate result was that the broader digital-asset provision in the Senate substitute remained intact as the chamber approached final passage. That mattered because the bill would extend broker information-reporting rules to digital assets, while participants in mining, staking, wallet software and protocol development argued that the wording could reach actors that did not possess the customer information a broker would normally report.

How the compromise was blocked

Amendment No. 2656 was sponsored by Senators Pat Toomey, Mark Warner, Cynthia Lummis, Kyrsten Sinema and Rob Portman. Its text would have defined the relevant broker category as a person who, for consideration, regularly effectuates digital-asset transfers on behalf of another person. It also included rules of construction stating that people solely validating distributed-ledger transactions, or solely selling hardware or software used to control private keys, were not included merely because of those activities.

Toomey first asked that Amendment No. 2656 be agreed to by unanimous consent. Senator Richard Shelby requested that the proposal be combined with his Amendment No. 2535 on defense infrastructure, and Toomey accepted that modification. Senator Bernie Sanders then objected to the combined request, specifically criticizing the proposed addition of roughly $50 billion in military spending.

Senator Tom Carper next sought unanimous consent for the crypto amendment by itself. Shelby again asked to attach his defense amendment; Carper declined, and Shelby objected to the original request. The official record therefore shows two distinct procedural barriers: Sanders stopped the combined package, and Shelby stopped the standalone crypto amendment. Describing the episode simply as one senator voting down the crypto compromise would omit that sequence.

What remained in dispute

The underlying bill defined a broker broadly enough to include a person who, for consideration, was responsible for regularly providing a service effectuating transfers of digital assets on behalf of another person. It also treated digital assets as specified securities for reporting purposes and contemplated returns and statements required after December 31, 2023.

Critics said the wording could be read to cover validators, software developers and wallet providers unable to collect names, taxpayer identification numbers and transaction details. Supporters of the underlying provision disputed that interpretation. In an August 9 floor colloquy, Warner and Portman stated that miners, stakers and sellers of private-key hardware or software would not be brokers when they performed only those functions. Their exchange documented legislative intent, but it was not the same as inserting explicit exclusions into the bill text.

The compromise also did not eliminate digital-asset reporting. Its sponsors said centralized exchanges acting as brokers should report customer transactions in the same manner as conventional brokers. The contested question was which intermediaries actually fit that role, not whether cryptocurrency gains were taxable.

Why August 9 mattered

The episode placed protocol architecture inside a major tax and infrastructure debate. A statutory term designed around financial intermediaries was being applied to networks in which validators and software publishers may facilitate activity without maintaining conventional customer relationships. The amendment’s failure left Treasury interpretation and later legislative action as unresolved safeguards rather than enacted text.

As of August 9, H.R. 3684 had not passed the Senate, cleared the House in its Senate-amended form or become law. Any later enactment, implementation or regulatory interpretation belongs to subsequent chronology and should not be projected backward into this date. The verified development is narrower: senators reached a bipartisan clarification, but Senate procedure prevented its adoption.

Primary sourceCongressional Record — Senate proceedings for August 9, 2021

The complete source packet and revision history are retained with the newsroom record.

Automated desk disclosure

Automated systems may have assisted with source organization and drafting. Coinburn is accountable for the published text and maintains a revision record.

Financial-risk note

This article provides news and analysis, not investment, legal or tax advice. Digital assets are volatile and may result in total loss.