Policy · November 2026

The midterms did not kill US market-structure law. They raised the price of getting it, and they moved that price onto the product.

Democrats won both chambers of Congress and take the gavels in January 2027. The stalled CLARITY Act is still the federal rulebook fight for venues, brokers, dealers, and custody. The next draft is likely to ask for stronger consumer protections, a larger SEC role, and ethics rules that actually bind senior officials. Crypto PACs spent $233 million this cycle, per Public Citizen. In Ohio, Sherrod Brown still beat a crypto-backed challenge that spent $64 million to stop him.

That is the political story. The builder story is narrower.

If you ship a wallet, a venue, a payments rail, or a tokenized product that touches US users or US bank partners, the next year is about proving consumer protection in the app. Statements. Custody labels. Hot-wallet policy. Address screening. An incident owner. The next draft of market structure will ask for those things. Bank diligence already does.

The short version

CLARITY (H.R. 3633) is the federal rulebook for digital-asset venues, brokers, dealers, and custody. It is not the GENIUS Act. GENIUS already covers payment-stablecoin issuers. CLARITY is the missing layer around everything else.

The Senate failed to advance it in September 2026, largely over ethics. Democrats now write the next version, and they still need Republican votes to clear a 60-vote Senate. So the path is a harder bargain, not a partisan rewrite that sails through.

Some lobbyists have already called the bill dead. Rep. Shri Thanedar, a Democrat who voted for the House version, still says it can pass if anti-corruption rules apply to the President, not only Congress. For a shipping team, those two forecasts collapse into one job: build as if the next statute looks more like a bank exam than like the summer draft.

Keep production on Tatum’s RPC Gateway, Data API, and Notifications so the evidence is already in the stack when the questionnaire lands.

What actually changed in Washington

Senator Elizabeth Warren is expected to chair Senate Banking. House Democrats are discussing a broader market-structure bill that expands ideas from Rep. Maxine Waters: more consumer protection, more SEC, new limits on officials holding or issuing digital assets. Incoming House Oversight Chair Robert Garcia has already flagged corporate-corruption inquiries, including Trump family crypto ventures.

That last item is not your roadmap. It is the political tax on the bill. Hadley Stern, head of institutions at Silence Laboratories and founder of Fidelity Digital Assets, says the industry should want Democrats to separate official self-dealing from market-structure law, because that mix is what poisoned the bipartisan deal.

" A sitting president’s family launching memecoins and a stablecoin is a real governance problem. If I’d done that at Fidelity, I’d have been walked out the same afternoon. "

- Hadley Stern, Silence Laboratories / Fidelity Digital Assets

Stern’s other point is the one builders should tape to a monitor. 2026 is not 2022. The stack is no longer “FTX and a bunch of tokens.” There is a federal stablecoin law, Treasuries and credit funds onchain, and tokenized equities on the way.

" You don’t regulate that by pretending it doesn’t exist. "

- Hadley Stern

A Democratic Congress can slow a crypto-friendly draft. It cannot un-invent the market. The pressure moves to how you custody, disclose, and recover when something breaks.

The new bargain: consumer protection as product work

Lindsay Fraser, chief policy officer at the Blockchain Association, argues consumer protection and innovation are not competing objectives. The law has to match how the technology works, and it has to earn public trust if builders are going to keep a future in the United States.

Paul Brody, founder of Nightfall Networks and former global blockchain lead at EY, expects banks to come out ahead. They will push crypto companies toward the same customer-protection and security bar they already live under. He called accepting those conditions a wise strategy, because blockchain-native systems are still more programmable and efficient once the compliance layer is real.

Translate that out of op-ed and into a backlog.

Four workstreams

01
Consumer protection in the UI

Show self-custody versus firm-custodied balances. Make history exportable. Name who gets paged when a withdrawal fails.

02
SEC gravity

Map which flows are software, which take orders, and which hold customer assets. Keep those paths from collapsing into one screen.

03
Bank-grade security

Key policy, authenticated RPC, failover, webhook signatures, SOC 2 paperwork. See security best practices for 2026.

04
Custody after Binance

Hot-wallet caps, insurer or loss-payee language, and a split between matching engine and custodian stop being theoretical.

What enterprises will ask for next

Enterprise buyers were already moving this way. The midterms accelerate the questionnaire, they do not invent it.

A bank, a payments firm, or a tokenized-fund issuer will ask who holds the key, who can move customer assets, what happens when an RPC endpoint stalls, and whether you can reconstruct a wallet as of last Tuesday. Public agencies ask a version of the same thing. We covered that stack in how governments use blockchain APIs.

You do not need a signed CLARITY PDF to answer those questions. You need:

  • Normalized balances and history from the Data API, not a one-off indexer that only the original engineer can query
  • Counterparty checks through the Security API before a send, a receive, or a new admin
  • Transfer and failed-transaction Notifications on treasury and hot wallets, with HMAC verification on the webhook
  • An RPC path with priority failover, not a single URL in an env file
  • Vendor paperwork that survives procurement: Tatum’s SOC 2 Type II and ISO/IEC 27001:2022 coverage is the kind of evidence those reviews actually open

If you already sell to institutions, this is a sales advantage. Brody’s “banks win” line only hurts teams that treated consumer protection as a lobbying problem. Teams that treated it as UX and ops get to keep the programmable rails and pick up bank partners that sat out waiting for a federal rulebook.

How the Binance hack shows up in the next draft

The midterms landed while lawmakers were still staring at the October 29 Binance hack: more than $6.3 billion stolen from a centralized exchange hot wallet after a signing failure, the largest on record.

Thanedar says market-structure law would not have solved every failure, but it would have put security guardrails on paper, and the hack is a clean example of what happens without them.

Maylea Ma, deputy general counsel at 1inch, was blunter about the current text. The incident was a CEX hot wallet and signing failure. The draft, she said, has no insurer, no loss payee, and no hot-wallet cap that would have limited the loss or forced a security standard that might have prevented it. Amanda Fischer at Better Markets used the same episode to argue that crypto exchanges should not also act as custodians, because that design is a honeypot.

Whether you agree with Fischer’s conclusion or not, the architecture question is now in the room:

  • Is the matching engine also the custodian?
  • What share of customer assets sits in a hot wallet, and who can sign?
  • Who is on the hook if that wallet drains: the venue, an insurer, a named loss payee, or the customer?
  • How fast do you detect an anomalous outflow, and who gets the page?

Ma also warned that the hack could make lawmakers less willing to pass an industry-favored draft unless consumer protection is stronger. That is the concession. The work it implies is ordinary production hygiene: segregated wallets, a written hot-wallet policy, filtered notifications on large transfers, and an incident note that names who pauses withdrawals. We laid out the control set in the 2026 security guide. The midterms just made that guide look like prep for a hearing.

Listen: Binance Hacked, The $6.4B Heist. Mantas and Hannah on The Tatum Podcast, about 7 minutes.

Follow the funds

We are mapping where the $6.3 billion sits, chain by chain, and how to alert when a still-movable wallet moves.

Open the live map

What to ship by team before January

January 2027 is when the gavels change. It is also a useful internal deadline. The cards below are not legal advice. They are the artifacts we would want in a diligence folder if a bank, a venue partner, or a future examiner asked “show me.”

01
Wallets and custody

Label self-custody vs firm-custodied balances. Export history from the Data API. Screen destinations with the Malicious Address API.

02
Exchanges and brokers

Prove customer-fund segregation. Write a hot-wallet cap. Alert on failed withdrawals and large outflows with Notifications.

03
DeFi and apps

Keep info-only front ends separate from order flow. Make supply, reserves, pegs, and positions reconcilable. Prefer GENIUS rails.

04
Payments and infra

Stay on licensed issuer rails under GENIUS. Use SLA-backed RPC with routing, and event-driven alerts instead of polling.

If you want the longer CLARITY primer, including the SEC/CFTC split and how we were tracking passage odds in September, it is still here: The CLARITY Act for builders. This piece is the midterm overlay on that map.

What to concede. What not to pause.

Brody also flagged a presidential veto, and he said crypto is likely a low priority next to corruption investigations, budget fights, and war. CNBC’s post-election read was similar: Democrats may spend more energy on Trump-linked crypto businesses than on an industry-favored market-structure bill. That can delay a statute. It does not delay a bank’s security review.

Worth conceding

  • Consumer protection as a product requirement, not a talking point
  • Bank-like custody, security, and incident-response standards
  • Ethics walls that separate official self-dealing from the industry bill
  • A larger SEC role on securities-class flows, with a written map of what you actually operate

Do not pause

  • GENIUS-covered stablecoin payments and the rails those issuers already use
  • Tokenized Treasuries, funds, and equities that institutions are already shipping
  • Production RPC, data, and monitoring. Diligence will not wait on cloture.
  • Multi-chain products on networks those buyers already use: Ethereum, Polygon, BNB
Filibuster math still applies. Democrats can set the agenda. Most market-structure text still needs 60 Senate votes. The realistic bill is a compromise with more consumer protection, not a 51-vote rewrite. Build for the compromise.

A week-one checklist

1
Write the flow map

One page: software, brokerage, custody. Put it where legal, product, and eng can all find it.

2
Turn on exportable history

Portfolio and transfers via the Data API. Diligence questionnaires love a CSV more than a slide.

3
Watch the hot wallets

Subscribe to transfer and failed-tx Notifications on treasury addresses. Verify the webhook HMAC. Name the human who gets the page.

4
Screen counterparties

Run the malicious-address check before send, receive, or a new admin. Do it in the product, not in a spreadsheet after the fact.

5
Prove RPC failover

Disable the primary in staging. Confirm you still read a fresh block on the chain you expect. Custom RPC Gateways exist for this test.

6
Keep a live read on the bill

Pipe related prediction markets through the Prediction API if policy risk sits on your dashboard. Do not let that chart become the reason you skip items 1 through 5.

Crypto spent years convincing Washington it deserves a seat at the table. The midterms are the reminder that the seat comes with obligations, and that those obligations look a lot like production software: custody you can explain, security you can test, and records you can export.

FAQ

Democrats won both chambers and take control in January 2027. Crypto market-structure law can still pass, but the next draft is likely to demand stronger consumer protections, a larger SEC role, ethics rules that bind senior officials, and tighter custody and security standards. Builders should treat that as product work: custody labels, exportable history, address screening, hot-wallet policy, and monitored production infrastructure. Checked November 9, 2026.