By The Bitcoin Reserve Bill Got Weaker to Survive Committee. It Still Passed on Party Lines
H.R. 8957 was introduced in May by a Republican and a Democrat together, Nick Begich and Jared Golden, with 23 mostly Republican cosponsors and language about protecting Bitcoin from the whims of future Congresses. Four months later, the version that actually cleared committee had dropped its original funding mechanism, weakened its reporting requirements from quarterly to annual, and still passed 28 to 21 with every single vote falling exactly along party lines. The bill got weaker to build support and got none anyway. That's worth sitting with longer than the vote count itself.
What actually changed to get this bill through
The substitute amendment Bryan Steil introduced right before the final vote made two specific concessions from the bill Begich originally filed. The proof-of-reserve audit requirement went from quarterly to annual, a real loosening of the oversight the bill promised at introduction. And the original bill's stated purpose, offsetting costs using certain Federal Reserve System resources, simply isn't in the text that passed, meaning a concrete funding mechanism got quietly dropped somewhere in four months of negotiation. Both changes point the same direction: less transparency, a vaguer funding path, presumably in service of building broader support. Whatever that support was supposed to look like, it didn't show up in the room. Every Republican present voted yes. Every Democrat voted no. There's no evidence in the actual vote count that either concession moved a single vote.
The Senate's own experience the day before makes the same point with a bigger number. The CLARITY Act's authors didn't offer a couple of quiet concessions, they released a weekend revision incorporating more than 120 separate changes Democrats had specifically requested, by far the larger compromise of the two bills. It failed anyway, 49 to 50, with zero Democratic votes, the same outcome H.R. 8957 produced with a fraction of the concessions. Scale the compromise up by an order of magnitude and the result doesn't change. That's a strong signal that the size of the concession was never the variable that mattered.
The private key for every Bitcoin wallet on Earth is on this website, even Satoshi's. But even if you try for a million years, you'll never find a funded one.
Try the key collider nowThe same fight, one day apart, in a different chamber
What actually sank the compromise wasn't the funding language or the reporting schedule. Maxine Waters offered a competing amendment that would have barred elected officials and their immediate families from holding digital assets or taking crypto-related compensation. It failed 21 to 28, the identical split as the bill's final passage. That's the same specific objection, an ethics rule aimed at the financial interests of officials and their families in the crypto industry, that killed the Senate's CLARITY Act on a failed cloture vote the day before. Two different bills, two different chambers, two different sets of specific provisions, and the exact same fault line running through both: not what a federal Bitcoin framework should technically look like, but whether officials with a personal financial stake in the outcome should be writing rules for the industry they're invested in. When the identical objection kills two separate bills in two separate chambers inside 24 hours, that's not a coincidence of scheduling. That's the actual fight, and everything else attached to both bills is negotiating around it.
What actually happened at the state level tells a different story
It's worth noting that the federal gridlock isn't universal. Individual states have already moved further and faster on the same basic idea than either chamber of Congress managed this week. New Hampshire authorized a state-level Bitcoin reserve in May 2025. Texas went further, actually purchasing Bitcoin with public funds through a spot ETF the following month, becoming the first state to do so. Neither required the kind of ethics compromise that's stalled the federal versions, because neither state legislature was simultaneously debating rules for a sitting president's own family business. That's not a coincidence. It's evidence that the technical questions, custody structure, holding periods, reporting schedules, are actually solvable when the personal financial conflict isn't sitting in the middle of the negotiation. Congress has the harder version of this problem specifically because Congress is the body that would have to write rules governing the president whose family stands to benefit from how permissive those rules turn out to be.
The counter-argument worth taking seriously
It's fair to push back on reading too much into one committee vote. Committee votes are structurally more partisan than floor votes almost everywhere in Congress, since committee assignments themselves are made by party leadership specifically to produce reliable majorities, and a member who might eventually vote for a bill on the floor, once amendments are settled and leadership has counted votes, often votes with their party at the committee stage regardless of their private view. It's also true that policy substance isn't nothing: the 20-year lock, the state custody provision, and the federal accounting requirement all represent real, specific choices that could plausibly attract individual votes once the bill reaches the floor and members aren't simply signaling loyalty to their party's committee position. A single 28-21 vote in September doesn't necessarily predict what a floor vote looks like in a different political environment after the midterms, particularly if Republicans hold or expand their majority and no longer need Democratic votes to pass anything at all.
What that counter-argument doesn't explain is why the concessions happened at all if nobody expected them to matter. Steil's substitute wasn't cosmetic, it changed a specific, substantive commitment (quarterly audits) into a weaker one (annual audits), and it appears to have dropped the bill's own stated Federal Reserve funding mechanism entirely. Those are the kinds of changes a bill's own authors make when they're trying to win over skeptical votes, not changes made for no reason. If the goal was Democratic support and the result was zero Democratic votes, the rational conclusion isn't that the concessions failed to reach far enough. It's that no concession on reporting frequency or funding mechanics was ever going to touch the actual objection, which was never about those provisions in the first place.
What would actually break the pattern
There's a real, specific path out of this, and it's the one Waters herself proposed: rules that reach the actual conflict directly rather than working around it. Her failed amendment would have barred officials and their immediate families from holding digital assets or taking crypto-related compensation, the same shape of proposal Senate Democrats pushed during the CLARITY Act negotiations when they asked for mandatory divestment rather than a blind trust. Neither version has attracted a single Republican vote in either chamber, which suggests the actual sticking point isn't the specific mechanism, disclosure versus divestment versus a holding period, but the principle that any such rule would apply to the sitting president's own family regardless of how it's written. A bill that resolved that question on terms both parties could accept would likely pass comfortably; the technical provisions around custody and reporting were never where the real disagreement lived. Until that happens, expect more of what happened this week: bills that get more restrictive on transparency and funding while getting no more bipartisan, because those two things were never actually connected to begin with.
What this means for whatever comes next
If the pattern holds, the substantive content of a Bitcoin reserve bill may matter less to its actual odds than whichever party holds the votes when it comes up. A bill can lose its funding mechanism, lose three-quarters of its reporting frequency, and gain nothing in exchange, and a bill can gain 126 bipartisan text changes in the Senate's case and still fail by 11 votes. Both outcomes are consistent with a simpler explanation than the specific policy merits of either bill: the ethics question is the actual veto point, and until it's resolved on terms both parties can live with, the market structure and custody details are largely beside the point. Begich introduced this bill ahead of the November midterms specifically because control of the House is what decides whether any version of this survives past this Congress. That's a more honest way to read where this actually stands than treating the 28-21 committee vote as momentum. It's a bill that got weaker and still couldn't buy a single vote from the other side, which is the opposite of momentum, dressed up as if it were the same thing. Whichever party controls the House after November will decide whether that pattern gets a chance to change or simply repeats itself with a different bill number attached.
For the full mechanics of what H.R. 8957 actually contains, see the complete guide to the Bitcoin Reserve bill. For the Senate vote that failed on the identical objection a day earlier, see why the CLARITY Act just failed, and for the executive order both bills are ultimately trying to convert into permanent law, see what the US Strategic Bitcoin Reserve actually is.