HomeAtlasDashboardChartsReal valueResearchPersonsCatalogsBlockchainBubble MapGlobeQuantumAILeadershipLensesMethodologyGlossarySource ↗
Independent research & opinion. Gradings are automated / LLM-assisted and may contain errors or hallucinations; nothing here is a statement of fact, financial advice, or an accusation of wrongdoing by any party. Claims about identifiable people or organizations reflect public records + good-faith interpretation; intent is not inferred from association. Methodology & disclaimer.

CLARITY Act (H.R. 3633) — delay chronology and the shifting arguments

House passage was fast and bipartisan; the Senate is where it stalled. This dates the sequence and tests one hypothesis: that large banks moved the goalposts to run out the clock.

Timeline

The developer-rights fight (your "proven false")

Section 604 (the Blockchain Regulatory Certainty Act — Emmer H.R. 1747; Lummis + Wyden S. 3611) gives non-custodial developers a safe harbor: they aren't money transmitters (excluded from 31 U.S.C. §5330 / 18 U.S.C. §1960) where they lack "unilateral and independent control" of user funds — plus a self-custody shield (Keep Your Coins, §10605). It responds to the Tornado Cash prosecution (Roman Storm convicted on one charge, Aug 2025); the principle is "writing code shouldn't be criminalized."

Law-enforcement groups (and some Catholic leaders) objected that it's a "compliance-free lane for illicit finance." The DeFi side rebutted — code ≠ control, and anti-fraud/anti-manipulation (CFTC) rules still apply to everyone; the DeFi Education Fund called it "appropriate tools without overregulating." The objection did not prevail — the safe harbor survived intact. So the "proven false" reading holds in the sense that the illicit-finance-loophole claim didn't carry — but note the objector was law enforcement, not the bank/yield coalition.

Verdict (graded): partially supported, not the whole story

Sources: Latham & Paul Hastings US crypto-policy trackers; The Block (Jul 22 2026); crypto.news; Coinpedia timeline; Polymarket/Galaxy odds; DeFi Education Fund. Cross-refs: spec-stablecoin-yield-fight, spec-bank-digitalmoney-consortia, spec-us-regulator-jurisdiction-map, spec-crypto-sec-epstein (Trump/WLFI conflict).

Cloture-vote outcome (15 Sep 2026): failed, but kept revivable

The Senate cloture vote on the motion to proceed to CLARITY failed on 15 Sep 2026, short of the 60 needed (live tally ~49-49/49-50; Sen. Susan Collins among the notable no votes; possible GOP defections flagged on community-bank grounds, e.g. Cornyn). Sponsors' "last, best and final" substitute (14 Sep) reportedly folded in ~126 Democratic-requested changes over a year; Democrats sent a counterproposal Monday night; overnight talks collapsed before the 2:15pm ET vote.

But it was not killed. Majority Leader John Thune entered a motion to reconsider - the standard maneuver (a prevailing-side member, typically the leader switching to "no" for standing) that preserves a route to bring CLARITY back. So the widely-quoted "it's over" (Sen. Lummis) is an overstatement: the vehicle stalled but was deliberately kept revivable.

The three disputes that sank it map exactly onto threads already documented here: (1) ethics rules targeting President Trump's ~$1.4B crypto income (World Liberty Financial); (2) DeFi developer liability (Section 604); (3) the stablecoin-yield provision (threatening ~$1.35B/yr in Coinbase USDC-rewards revenue - the same yield fight in spec-stablecoin-yield-fight). Prediction markets had already collapsed (Polymarket ~82% Feb -> ~16% early Sep; Galaxy ~10%). Cloture success would not have enacted the law anyway - it only opens amendments -> passage -> House concurrence.

Sources: CoinGape, Coinpedia, TechTimes, CryptoTimes (2026-09-15 live coverage). Cross-refs: spec-stablecoin-yield-fight, spec-community-bank-stablecoin-response, spec-crypto-sec-epstein.

← Research index · structured data: spec-clarity-act-chronology.json · spec-clarity-act-chronology.md