Result update · September 15
The Senate Daily Press has now reported that cloture on the motion to proceed failed 49–50. Our separate results article covers the completed vote, the possibility of reconsideration and an early market snapshot. The original preview below is preserved as pre-vote analysis. 6
The question on the floor
The Senate’s September 15 schedule sets a 2:15 p.m. Eastern vote on cloture on the motion to proceed to H.R.3633, the Digital Asset Market Clarity Act. That is 18:15 UTC. At our 17:45 UTC check, the official roll-call list contained no result for this CLARITY vote. The scheduled time can change. 1, 2
The practical question is whether senators will clear a procedural obstacle to taking up the bill. A successful vote would advance that process. It would not, by itself, approve the bill’s full text or make it law. That distinction matters when a fast-moving headline reaches a trading screen.
The number to watch is the official threshold
The Senate explains that cloture generally requires three-fifths of senators duly chosen and sworn, conventionally 60 in a 100-member Senate. Readers should check the threshold and outcome recorded for this specific roll call, alongside the yes, no and not-voting totals. A running television tally is not the completed official result. 3
If cloture succeeds, the next useful question is which text the Senate takes up and what subsequent action is scheduled. If it fails, the immediate route has hit an obstacle. The result alone would not establish that every future route for crypto legislation has closed. I would look for the leadership’s stated next step before drawing that larger conclusion.
The proposed text still matters
In their September 14 release, Senators Cynthia Lummis, John Boozman and Tim Scott said the final draft would be offered as a substitute amendment if cloture on the motion to proceed is invoked. Their release describes revised ethics enforcement, Treasury authority relating to stablecoin-driven deposit flight, and protections for software developers. These are the sponsors’ descriptions of a proposed text, not rules already in force. 4
For a crypto business, a vote count cannot answer which activities the eventual framework covers or what obligations would apply. The amendment actually offered, later amendments and the final agreed text remain important. A broad market reaction to legislative progress can therefore coexist with unresolved questions for particular business models.
How I would read the market reaction
A price move around the vote would show that traders are adjusting positions. On its own, it would not prove which provision caused the move or that the reaction will last. A useful comparison needs the same instrument, a defined observation window and timestamps on both sides of the event.
Our earlier Fed-and-CLARITY article preserved a morning prediction-market snapshot and explained why Polymarket’s named-bill contract and Kalshi’s broader legislation contract should not be averaged. Those morning quotes are not live odds for this vote. This preview introduces no new probability estimate. 5
What the results article must establish
The follow-up will begin with the exact motion, the final official tally and the recorded result. It will then separate completed action from the next scheduled step. Any new market prices will need fresh, timestamped source data; if that evidence is unavailable, the article will say so rather than fill the gap.
This is a pre-vote analysis, not a result announcement. We will publish the results article after the central facts are verified, then send the Spectre Intelligence Telegram notification with a choice of app or website links.
Sources
- U.S. Senate Daily Press: September 15 floor schedule
- U.S. Senate: official 2026 roll-call results
- U.S. Senate: cloture and the three-fifths threshold
- Lummis, Boozman and Scott: September 14 draft and conditional substitute amendment
- Earlier Spectre analysis: dated Fed and crypto-legislation contracts
- Results: CLARITY stalls at 49–50; what remains open
See a discrepancy? Send the article URL and supporting evidence to spectre@spectreai.io.
Explore Spectre
