Twenty working days, one named provision on the trading block, and — as of today — no cloture motion filed. The abstract fight is now a countdown. If you're just joining, the CLARITY Act is Congress's attempt to draw a federal market-structure map for digital assets — which tokens and platforms sit under the SEC, which under the CFTC, and what protections apply to the people building. Coming into this, CFTC Chairman Michael Selig was pushing the line that New York-style state enforcement makes federal rules more urgent, while senators stayed split over developer protections and illicit-finance safeguards. This is Crypto Clarity Watch. Today — one section, Section 604, and whether it survives the vote count. Cassidy, walk us in. Here's TFTC:
The Senate returned from its July recess with the CLARITY Act sitting on the Legislative Calendar at General Orders No. 423 and three weeks to act before August. No cloture motion has been filed. The merged text from the Senate Banking and Senate Agriculture Committees, expected the week of July 13, has not been published as of today, meaning the exact language of Section 604 in the Senate version remains unconfirmed.
Here's the concrete fact of the week: the CLARITY Act is sitting on the Legislative Calendar at General Orders 423, and as of today no cloture motion has been filed. The pressure campaign is down to procedure now. No cloture filed with roughly twenty working days on the clock — that's a failure you can put on a calendar, not a vibe. I've been saying floor time is the binding constraint. This is what it looks like when the calendar starts winning. And the chip on the table has a number now — Section 604, the carve-out that bars classifying non-custodial Bitcoin developers as money transmitters. It's one of three unresolved disputes standing between the bill and the seven to nine Democrats needed to clear 60. One vote-count dispute away from being traded away. Read Section 604 next to what Wyden was demanding on July 10 — statutory language exempting non-custodial developers. Same fight, and that's where the bill is bleeding. Careful, though — the merged Banking-Agriculture text expected this week hasn't been published. So the exact Senate wording of 604 is still unconfirmed. We're arguing about a provision whose final language nobody's seen. Right, and Lummis is out there warning that if it slips past August, meaningful crypto legislation waits until 2030. Big number, convenient timing. But you don't move cloture with a warning — you move it with a filed motion, and there isn't one. Odds on Senate passage: Galaxy Research at roughly 50 percent, Polymarket 41 to 48. Basically a coin flip dressed up as analysis. The House cleared this 294-134 last July — that number tells you nothing about a filibuster threshold. This one's from United States Senate:
This new disclosure is particularly troubling as the President urges Congress to pass cryptocurrency deregulation legislation that will almost certainly boost the value of his crypto holdings. The disclosure also demonstrates the extent to which President Trump’s family is profiting off of their crypto businesses.
July 13 — same day senators walk back in — a letter lands on Thune and Schumer's desks citing the OGE disclosure: $1.4 billion in crypto income for the President in 2025. That's a primary-source number, dated and on file. And look at what they attach it to — DT Marks Defi LLC, over $590 million on its own, and a 38.25% stake in the entity that owns World Liberty Financial. So the conflict story comes with line items and dollar figures. And here's the part that matters for scheduling — the letter says the President is urging Congress to pass legislation that will 'almost certainly boost the value of his crypto holdings.' That context now sits on top of every floor vote we talked about in the Section 604 piece. $1.4 billion — more than any publicly traded U.S. crypto company earned last year, per the disclosure. When the person pushing the bill out-earns the entire regulated industry off the asset class, disclosure stops being a footnote. I've argued conflict disclosure should be a standing segment, not a gotcha. Well — this is the disclosure. It's public, it's from the Office of Government Ethics, and it's addressed to the two men who control the floor calendar. Here's Mattie Duppler at Washington Examiner:
Congress faces a choice: drain the savings of millions of Americans out of local banks and credit unions to meet the demands of well-funded crypto players, or create fair rules for the entire financial system. Those are the stakes of a new digital assets bill being debated in Congress.
Here's the framing in the Examiner op-ed: Congress can either drain savings out of local banks and credit unions for, quote, 'well-funded crypto players,' or write fair rules. It's an op-ed with a clear thesis, and it lands on the stablecoin yield question. Right, and let's keep the category straight. It's an opinion page giving the banking and credit-union coalition a voice for its economic-harm argument — deposit flight — which lines up with the blocking coalition we've been watching on Title II AML. And it's saying the quiet part: the CLARITY push serves the well-funded players, not the credit union in your town. When outside validation for 'clarity for whom' shows up on the Examiner op-ed page, I notice. I'd separate the two, though. Deposit flight from stablecoin yield is a stablecoin-bill argument. Section 604, the developer shield we just hit, is market structure. This op-ed uses 'hasty' to blur them, even though no cloture motion's been filed and there are roughly twenty working days left. Here's Ana Bustos García at CoinsPaid Media:
Developers of the Phantom crypto wallet and researchers at the Hyperliquid Policy Center (HPC) urged the U.S. Commodity Futures Trading Commission (CFTC) to revise the regulatory framework for on-chain infrastructure by exempting software developers from requirements intended for financial intermediaries.
So this lands the same day we're watching Section 604 wobble in the Senate. Phantom and HPC filed a joint response to the CFTC's request for information, asking the agency to exempt software developers from rules built for intermediaries. And I want to be precise here: this is a comment letter responding to a CFTC request for information. That's a rulemaking track. It isn't statutory language. Which is the whole tension. They're asking the CFTC to narrow a mandate the agency doesn't even have yet — the map CLARITY would hand it hasn't passed the Senate. No cloture motion filed as of today. Right, and here's why the distinction bites: if 604 — the Bitcoin developer money-transmitter carve-out — gets traded away on the floor, a friendly CFTC comment letter doesn't backfill that. You can't rulemake your way around a statute that stripped the protection. And nobody in this picture seems to be talking to each other. The outside pressure on the CFTC and the inside horse-trading in the Senate are running in parallel, and neither track knows what the other is conceding. The Phantom angle is at least honest about the premise — it's a non-custodial wallet, users hold their own keys, so the intermediary framework genuinely doesn't map onto it. That's a real argument, not a costume. Got a question, correction, or story idea we should be watching in crypto? Send it our way at cryptoclaritywatch at lantern podcasts dot com. We’d love to hear what you’re tracking.
Next, we're watching for publication of the merged Senate Banking and Senate Agriculture CLARITY text, expected this week, and any cloture motion on H.R. 3633. That would be the next formal signal of movement toward Senate floor debate.
You’ll find links to every story from today’s briefing in the show notes, so take a look at anything you want to read in full. That’s Crypto Clarity Watch for today. This is a Lantern Podcast.