❌

Reading view

DOA: CLARITY Act Torched By Senate Vote, Technocrats Are Livid But Not Deterred

Failure of the CLARITY Act does not stop the tokenization train, but it will slow it down. The SEC and CFTC will now write the rules by exemption, no-action letter, and enforcement discretion. The GENIUS Act provided the settlement layer in 2025, and the banks have already caved to tokenization. The stock markets are already being tokenized. Get ready for my new book, CRUCIBLE OF TOKENS, to figure out what this means to you, so you can take evasive action. ⁃ Patrick Wood, Editor.

The Senate on Tuesday failed to advance the Digital Asset Market Clarity Act, falling short of the 60 votes needed to invoke cloture on the motion to proceed to H.R. 3633. The vote, held at about 2:15 p.m. ET, was the first floor test of comprehensive crypto market-structure legislation in the chamber. It was not a vote on final passage. It was a vote on whether debate could even begin. The answer was no, with 50 no votes and 49 yes votes.

Every Democrat voted against the measure. Three Republicans – Sens. Susan Collins of Maine, Josh Hawley of Missouri and Jerry Moran of Kansas – also voted against the measure

The Clarity Act is the market-structure half of the crypto legal framework Congress began building last year, the companion to the GENIUS Act’s stablecoin rules. It draws the line between digital assets regulated as commodities under the CFTC and those regulated as securities under the SEC, puts spot trading platforms under a federal registration regime for the first time, and sets statutory terms for self-custody, noncustodial software and rewards on stablecoin balances. It cleared the House last July with 78 Democrats and then spent a year in Senate rewrites.

That result effectively freezes the bill in place with almost no calendar left before the midterms. Republicans control 53 seats. They needed at least seven Democrats, and more if GOP holdouts peeled off over bank or law-enforcement concerns. They did not get them.

The House passed its version 294-134 in July 2025. The Senate Banking Committee reported a version 15-9 in May 2026, with Democrats Ruben Gallego of Arizona and Angela Alsobrooks of Maryland joining Republicans. Tuesday was supposed to be the moment those committee crossovers turned into a floor coalition. Both Gallego and Alsobrooks voted no on cloture. Instead, the first hurdle became the last one of 2026.

BREAKING: 🇺🇸 The Crypto CLARITY Act has failed to pass the Senate cloture vote. pic.twitter.com/0VAw1H9Eyl

— Bull Theory (@BullTheoryio) September 15, 2026

Aaaaand, Bitcoin isn’t happy.

How the deal collapsed in 48 hours

Senate Republicans released what they called their “last, best and final” text Sunday night. Sens. Cynthia Lummis of Wyoming, Banking Chair Tim Scott of South Carolina, and Agriculture Chair John Boozman of Arkansas said the draft folded in 126 substantive changes requested by Democrats. The package included new ethics language modeled on a Tillis-Gallego proposal, edits to the Blockchain Regulatory Certainty Act for noncustodial developers, Agriculture Committee guardrails on affiliate trading and tribal gaming, and a Treasury “circuit breaker” meant to address bank fears that stablecoin yield would drain community-bank deposits.

Lummis’s line was blunt: Democrats got what they wanted; now take yes for an answer.

Democrats did not. Late Monday they sent a counteroffer. According to people familiar with it, they did not reopen the stablecoin-yield fight – sources had described that as a “Republican-only” problem – but they did demand more on ethics (large holdings, dependent children, paid crypto promotions), a narrower BRCA that expressly does not modify criminal law, and tighter Ag-title rules on exchanges and conflicts. Sens. Mark Warner of Virginia, Ruben Gallego of Arizona, and Raphael Warnock of Georgia said the White House-approved ethics language still needed work. Sen. Elizabeth Warren of Massachusetts went further, arguing the enforcement design left the Trump administration too much control and left loopholes around existing presidential crypto interests.

Republicans rejected the counteroffer Tuesday morning. “In response to a significant step in their direction, Democrats have chosen to move the goalposts again,” Senate Banking Committee spokesman Jeff Naft said. “Yet we are hearing the same unreasonable asks and the same refusal to take yes for an answer. The final text is public.” Lummis’s office said the Democratic paper “looks identical to their opening position at the start of recess.”

White House Crypto Council Executive Director Patrick Witt had already signaled there was little room left. “If there are any changes, we’re talking about punctuation at this point or technical changes,” he told Crypto In America on Monday. “I view that as definitely a best and final offer.”

Three fights that never closed

Ethics. This was the political core. Democrats wanted restrictions on large crypto holdings by the president, vice president, members of Congress, judges, and family, plus limits on paid promotions. Republicans added language they said tracked the Tillis-Gallego framework and gave state attorneys general a role in enforcement. Critics said it still left gaps around existing ventures tied to the Trump family and put too much enforcement discretion in the Justice Department. Warren and others treated that as disqualifying. The Democrats who had spent months negotiating the bill, Kirsten Gillibrand, Mark Warner, Cory Booker, Raphael Warnock, Ruben Gallego, Angela Alsobrooks and Catherine Cortez Masto, all voted no, according to Crypto In America’s Eleanor Terrett.

Developer protections and DeFi. The BRCA language was meant to shield noncustodial software developers from money-transmitter registration. Sen. Catherine Cortez Masto of Nevada has been the Democratic face of that fight. Republicans already stripped explicit criminal safe harbors to satisfy her. Her camp still wanted the provision narrowed and a sentence stating that nothing in it changes criminal law. Industry and GOP negotiators called that a second move of the goalposts.

Banks and stablecoin yield. Eight banking trade groups, including the American Bankers Association and the Independent Community Bankers of America, attacked the new circuit breaker as “not a safeguard at all” because it would fire only after deposits had already left. They wanted tighter bans on interest-like payments on stablecoin balances. The White House Council of Economic Advisers published a tool arguing there is “no meaningful relationship between stablecoin growth and community bank deposit flight.” Witt accused the banks of acting in bad faith: “If you oppose the Clarity Act because you just hate crypto, that’s fine. Just say that.”

That bank fight mattered inside the GOP. Sen. John Curtis of Utah said he would vote to proceed but was a no on final passage. Sens. John Cornyn of Texas and Susan Collins of Maine – Collins called the bill a “moving target” and flagged community-bank deposits – were publicly undecided going into the vote. Sens. Rand Paul of Kentucky and Josh Hawley of Missouri were widely expected to oppose the bill on substance. Mitch McConnell of Kentucky returned to the floor Monday after a three-month absence and said he would “do my best to be present for tough votes.” Presence was not the same as 60 votes.

What the bill would have done

Clarity is market-structure legislation, the sequel to last year’s GENIUS Act on stablecoins. It would split digital-asset oversight between the SEC and the CFTC, keep securities law from being skirted by labeling tokens as something else, set rules for trading platforms, and try to write a statutory floor under self-custody and noncustodial development. Supporters at BlackRock, Fidelity, Schwab, Goldman, and Coinbase argued the alternative is agency-by-agency enforcement with no durable statute. Opponents argued the draft under-regulated conflicts, illicit finance, and bank-deposit competition.

Majority Leader John Thune framed Tuesday as the “next logical step” after GENIUS. Scott called it the day “everyone [had] to put their cards on the table.” They did. The table did not have 60 cards on it.

Cloture on a motion to proceed is not a funeral by Senate rules. Leadership can file again. Amendments can be rewritten. A lame-duck session still exists on paper.

The calendar does not. The House has already canceled late-September weeks. The Senate has a short September window, then October campaign recess, then a post-election lame duck that will be defined by midterm results. Prediction markets had already repriced the bill before the roll call: passage-this-year contracts on Polymarket and Kalshi ran between the high teens and the mid-30s in the hours before the vote, depending on the platform and the hour. Analysts at TD Cowen and Capital Alpha had the full-year odds in the same neighborhood.

If the 119th Congress does not pass Clarity, the next Congress writes a new bill. Agencies keep making policy by enforcement and rulemaking. The industry stays in the gap between a House-passed statute and a Senate that could not open debate.

Witt said Monday that whether the bill got 60 votes would be “a political calculation, not a policy calculation.” Tuesday proved him right. The policy text was 600-plus pages and a year of talks. The politics were ethics, banks, and a midterm clock. The politics won.

Read full story here…

  •  

Amazon Says Cloud Infrastructure In Bahrain, UAE ‘Beyond Saving’

Amazon Web Services (AWS) is on the ropes in the Middle East with a collection of wreckage from bombed-out data centers in the UAE and Bahrain. AWS reported, “The damage to our infrastructure spanned multiple Availability Zones and exceeded what our regional and multi-AZ services are designed to withstand.” Phrases like “damaged beyond hope of recovery,” “the region went dark,” and “exhausted every option for recovering whatever was left behind” highlight the angst felt by AWS, ⁃ Patrick Wood, Editor.

Amazon Web Services (AWS) says it cannot restore access to its cloud-computing facility in Bahrain or one of three data-hosting zones in the UAE due to the extensive damage caused by Iranian retaliatory strikes, Reuters reported on 15 September.

“The damage to our infrastructure spanned multiple Availability Zones and exceeded what our regional and multi-AZ services are designed to withstand,” AWS reported in its status update seen by Reuters.

In the UAE, resources and data held exclusively within one zone, labeled mec1-az2, have been damaged beyond hope of recovery, the company said, as engineers are still salvaging what they can from the two other battered zones and across the wider Emirati region.

An availability zone refers to a cluster of one or more data centers sitting inside the same geographic region, the structure AWS relies on to keep services running when a single site goes down.

The outages trace back to March, when the US and Israel attacked Iran, and Tehran responded with missile and drone salvos against Israel and Gulf states hosting US military bases.

AWS confirmed at the time that two of its UAE facilities took direct hits, while a drone strike near one of its Bahraini sites left the infrastructure there destroyed.

Most Bahrain-based customers shifted their workloads elsewhere on AWS advice before the region went dark in April, but the company says it has now exhausted every option for recovering whatever was left behind.

The losses have called into question the resilience of the Gulf’s fast-expanding cloud and AI infrastructure.

The UAE is already redrawing plans to war-proof a major AI data center project, weighing decentralized site building alongside underground and blast-resistant construction, and even equipping the data center itself with anti-air defenses.

Israel and the US have long ago transformed AI infrastructure into a weapon of war deployed extensively across West Asian theaters.

Cloud platforms, data centers, and high-capacity computing systems now help store intelligence, process intercepted communications, analyze surveillance, and support military operations across West Asia, extensively so in Gaza and Iran.

Iran maintains that data centers operated by US technology companies are not simply civilian facilities, but strategic assets supporting US and Israeli aggression, thereby making them legitimate targets for retaliation.

AI has become a central instrument of US and Israeli warfare across West Asia, embedded in how targets are chosen, tracked, and struck.

Israel has weaponized AI platforms including automated targeting systems like The Gospel, Lavender, and Where’s Daddy? to harvest mass data, autonomously generate kill lists, and orchestrate systematic airstrikes and assassinations against Palestinians.

Backed by corporate infrastructure like Microsoft Azure, which stored massive caches of intercepted Palestinian communications, the Israeli military has deployed AI-driven drone surveillance to track and assassinate Palestinians.

The US has run algorithmic warfare systems such as Palantir’s Maven to process satellite, drone, and radar intelligence, using machine learning to speed the production of targeting recommendations against Iranian forces.

More than 1,000 targets were designated within the first 24 hours of the war on Iran, one of which resulted in the massacre of at least 150 people, including at least 120 schoolchildren at the Shajareh Tayyebeh elementary school in Minab.

Read full story here…

  •  

UAE Moves To ‘War-Proof’ Its AI Data Centers

“War is hell” when all of a sudden it dawns on you that your AI data center might be bombed into oblivion. UAE is perilously close to Iran, so its data centers are getting hit. The UAE is a leader in AI and FinTech (Financial Technology) in the Middle East, and wants to be the hinge pin of the global trade routes passing through the region. No AI data centers = no global trade. ⁃ Patrick Wood Editor.

The UAE is redrawing its plans for a five-gigawatt artificial intelligence (AI) data center project, one of the largest anywhere outside the US, after Iranian retaliatory strikes on infrastructure across the Gulf forced the Emirates to rethink how and where critical facilities are built, Reuters reported on 11 September.

Speaking in anonymity, six people familiar with the matter told Reuters that Emirati authorities began reassessing where and how sensitive facilities should be built once the war reached the Gulf.

Four of those sources said the campus, first designed as a single 26-square-kilometer site in Abu Dhabi, is now expected to take shape as several data centers distributed across the country.

Authorities are weighing ways to shield the facilities from drone and missile strikes, the sources said, including installing air defenses and putting some of the centers underground.

Sources also said interceptors and electronic jamming equipment are being written into the redesign, with blast-resistant concrete and additional backup power and cooling systems also under consideration, and with the most sensitive material, including military data, possibly housed inside mountains.

Iran began striking Gulf states hosting US forces with missiles and drones in response to US and Israeli airstrikes on Iranian territory. Two Amazon Web Services data centers in the UAE and one in Bahrain were damaged in March, and the company’s regional cloud services remain disrupted.

In April, the Iranian armed forces released a video naming Stargate UAE, the $30 billion, one-gigawatt first phase of the campus, as a potential target for retaliatory strikes, showing a map of the site alongside the caption “Nothing stays hidden from our sight.”

Daniel Benaim, a former US deputy assistant secretary of state for Arabian Peninsula affairs, called the war an “economic earthquake” for Gulf states that had spent years selling themselves as safe havens, adding that hardening critical infrastructure was now vitally necessary.

Data centers have moved from commercial facilities into the category of critical infrastructure, processing financial flows, sustaining public services, and feeding into military communications and intelligence work.

Read full story here…

  •  
❌