Spare a thought for the US Senate this week. Lawmakers are weighing an uncertain economy, the situation in the Middle East, and the opening stretch of an AI race moving faster than the policy meant to govern it. Given everything else on their plate, the CLARITY Act should be the easy one. 

It hasn't been so far. Senate Majority Leader John Thune said this week the chamber will probably hold a procedural vote on the bill before they leave for recess on Aug. 7, adding "we'll see if the Democrats will give us the votes to get on that." Prediction markets have cut its odds of becoming law this year to below 30%, down from a coin flip a month ago.

We're not going to guess whether it clears the floor in September, in a lame-duck session, or not this Congress. What we can say is what the bill asks of anyone touching digital asset markets, because that part holds regardless of the Senate's calendar.

The Real-Time Requirement

Start with Section 308.* For the first time, a US bill names blockchain analysis as a compliance tool in statute. Before an intermediary routes an order through a DeFi trading protocol, Section 308 asks it to detect money laundering, sanctions evasion, fraud, cyber intrusions, and market manipulation as they happen, then to execute, reject, or suspend the transaction based on that risk. Compliance is verified by examination, and an examiner will ask to see the control working on a live transaction.

That asks for something most compliance stacks were never built to do. Tracing a transfer after it settles tells you what happened and who to report. It does not stop the transfer, freeze the funds, or block a withdrawal while the money is still moving. Section 308 wants the decision while the transaction is in flight: detect, decide, act, inside the same block.

The rest of the illicit finance framework points the same way:

• Section 201 brings brokers, dealers, and customer-facing exchanges under the Bank Secrecy Act and expects suspicious activity monitoring that explicitly includes onchain analytics.
• Section 302 asks front-end messaging systems to screen for sanctioned addresses and stop transactions carrying ransomware or other illicit patterns.
• Section 305 creates a safe harbor to place a temporary hold on funds tied to suspected illicit activity, which only helps if you can flag those funds fast enough to act on them.
• Section 205 puts fraud detection duties on crypto kiosks.

Taken together, these sections make continuous monitoring, screening, and fast interdiction the floor rather than a stretch goal.

The sharpest attack on the bill comes from the Bank Policy Institute, which argues it does not go far enough. Offshore custodians, unhosted wallets, and mixers can still sit outside the perimeter, and the bill only orders a study of mixers rather than granting real authority over them. Agree with that critique or not, it pushes in one direction: wider monitoring and tighter coverage. Nobody serious is asking for less.

Why the Vote Doesn't Change the Work

Which is why the vote, for a security or compliance team, matters less than the headlines suggest. If CLARITY passes, real-time detection and an execute, reject, or suspend decision become an examined obligation, and the operators already running those controls are ready while everyone else scrambles. If it stalls, regulation-by-enforcement stays the default and classification stays contested, but the exploits, sanctions exposure, and fraud these controls address carry on without waiting for a statute. 

In April alone, more than $645M was lost across more than 60 separate incidents, one of the worst months in the history of this industry. That did not pause for a Senate calendar, and the next incident will not either.

So the honest planning posture is the same under either outcome. Build the capability to see risk onchain in real-time, decide on it at the transaction layer, and prove both to whoever asks, whether that is an examiner or your own board. 

This is the ground Hypernative works on: continuous monitoring across 75+ chains, a pre-execution decision on every transaction, fraud and address screening that flags risk the moment a block finalizes instead of days later, and automated response that can pause, block, or revoke before losses land.

Reach out for a demo of Hypernative’s solutions, tune into Hypernative’s blog and our social channels to keep up with the latest on cybersecurity in Web3.

Proactive security for onchain finance.

Website | X (Twitter) | LinkedIn

*Section numbers follow the House-passed bill. The July 22, 2026, Senate substitute renumbered them (e.g., Section 308 is now §10308); the numbering may change again if the bill moves further this fall.