CLARITY Act rewrite targets non-decentralized DeFi

TLDR

A revised CLARITY Act in the US would put compliance duties on people controlling non-decentralized DeFi protocols, not on neutral code itself.

1. The new draft creates a category of non-decentralized finance trading protocols and directs SEC, CFTC and Treasury to impose registration and AML-style obligations on their controllers.
2. A protocol falls in scope if an identifiable person or group can materially change its functions or restrict users, while genuinely autonomous systems and pure software infrastructure are explicitly carved out.
3. The text is still only a draft ahead of a September 15 Senate cloture vote, and even if it advances, detailed agency rulemaking will decide how DeFi platforms and front ends are treated in practice.

Deep Dive

1. What The Rewrite Actually Does

The revised CLARITY Act would require controllers of non-decentralized finance trading protocols to comply with securities, commodities and anti-money laundering requirements, including registration, conduct and recordkeeping rules, as laid out in the new draft posted by Senator Cynthia Lummis. The bill says the SEC and CFTC must write activity-based rulebooks, while Treasury decides how Bank Secrecy Act duties apply to those controllers, focusing on people rather than code or networks themselves.

DeFi rules are narrowed to spot and cash digital commodity transactions, which is meant to avoid unintentionally sweeping prediction markets and other event contracts into the same framework. Credit unions also get clearer authority to custody and offer crypto services under the same package.

2. How Non-Decentralized DeFi Is Defined

The draft defines a non-decentralized protocol as one whose functionality, operation or rules can be materially altered by a person or coordinated group, or where controllers can restrict users or bypass transparent, pre-set code logic. That captures platforms with admin keys, upgrade multisigs or pause switches that can change how the system works, even if the marketing calls it DeFi.

At the same time, the text specifies that software and distributed ledger systems are not required to register in their own capacity, and participation in incident response or security councils does not, by itself, count as control. The intent is to shield genuinely decentralized infrastructure and emergency mechanisms from being treated as financial intermediaries.

3. Status And What To Watch Next

The updated CLARITY Act is still draft legislation, not law. It is circulating just before a September 15 Senate cloture vote that needs 60 votes to open full debate, and key ethics and stablecoin yield disputes remain unresolved. Democratic support is uncertain despite the bill including over 100 Democrat-requested changes, so the entire package could stall.

Even if cloture passes, multiple rounds of amendments plus later SEC, CFTC and Treasury rulemaking will determine the practical impact. DeFi builders and users should watch:

1. Whether the cloture vote succeeds.
2. How agencies interpret control in guidance and enforcement.
3. Whether future drafts tighten or relax the definition of non-decentralized DeFi.

Conclusion

The CLARITY Act rewrite does not ban DeFi, but it draws a regulatory line between truly decentralized systems and decentralized in name only platforms where humans still hold levers of control. If the bill advances and agencies follow through, controllers of those protocols could face CFTC, SEC and AML-style obligations, while neutral infrastructure remains largely out of scope. For crypto users and builders, the key edge now is understanding where their projects sit on that control spectrum, and tracking how Washington turns these definitions into enforceable rules.