CLARITY Act Section-by-Section Breakdown
This page walks through the substantive provisions of the Digital Asset Market CLARITY Act (H.R. 3633, 119th Congress), section by section, based on the bill text and the House Financial Services Committee's own section-by-section summary. It is written for builders, exchanges, compliance teams, and investors who want more than a headline explanation. For the plain-English overview, see what the CLARITY Act is and why it matters; for live status updates, see the Timeline & Updates page.
What does the CLARITY Act actually do?
The CLARITY Act creates the first comprehensive federal market-structure framework for digital assets by splitting regulatory jurisdiction between two agencies: the SEC oversees digital-asset securities offerings and permitted payment stablecoins on registered platforms, while the CFTC gets exclusive jurisdiction over digital commodity spot markets. It also excludes "digital commodities" and "permitted payment stablecoins" from the legal definition of a security, sets registration and disclosure rules for exchanges and issuers, and exempts pure software activity like running a node or building a wallet from registration.
In practice, the bill tries to answer the question that has driven years of enforcement disputes: is a given token a security regulated by the SEC, or a commodity regulated by the CFTC? Rather than leaving that to case-by-case litigation, the bill defines "digital commodity" and "permitted payment stablecoin" as categories that fall outside the legal definition of a "security" (Sec. 301), then builds separate registration, disclosure, and custody regimes around each regulator's turf. Readers who want a quick self-check on which bucket a specific token might fall into can try the token classification quiz, which walks through the decentralization factors described below — though only the SEC or a court can make that determination for real.
The SEC/CFTC jurisdictional split
The core structural idea of the bill is dividing authority by market type rather than by asset type alone. The SEC keeps its traditional role over investment contracts and capital-raising activity involving digital commodities, plus general anti-fraud authority across the space. The CFTC, which previously had only limited authority over crypto derivatives, gains exclusive jurisdiction over the spot (cash) market for digital commodities traded through registered digital commodity exchanges, brokers, and dealers (Sec. 401), along with new anti-fraud powers specific to that market.
| Under SEC jurisdiction | Under CFTC jurisdiction |
|---|---|
| Investment contracts involving digital commodities (primary-market offers and sales) | Spot-market trading of digital commodities on registered digital commodity exchanges (Sec. 401) |
| Permitted payment stablecoins when traded on SEC-registered platforms | Digital commodity brokers and dealers operating in the spot market |
| General anti-fraud and anti-manipulation authority across digital asset markets | Anti-fraud authority specific to registered digital commodity trading venues |
| Disclosure regime for issuers before a blockchain system is certified "mature" (Sec. 202) | Cannot regulate the internal operations of a permitted payment stablecoin issuer |
The practical effect is that a single token can touch both regulators at different points in its life cycle: SEC oversight while it is closely tied to a founding team's capital-raising efforts, and a shift toward CFTC-regulated spot trading once the underlying network is decentralized enough to be treated as a mature blockchain system. The glossary defines each of these terms — "digital commodity," "permitted payment stablecoin," "digital commodity exchange" — in plain language if any of this terminology is unfamiliar.
How are digital commodities defined, and what is a "mature blockchain system"?
Section 301 excludes digital commodities and permitted payment stablecoins from the statutory definition of "security." Section 202 introduces a "mature blockchain system" test: a network is more likely to qualify as decentralized, and its token to shed SEC disclosure obligations, the less control any single person or affiliated group has over its development, governance, and token issuance.
This decentralization test is arguably the single most consequential mechanism in the bill, because it determines when reduced SEC disclosure applies to a token's issuer. Rather than a bright-line rule, the bill sets out qualitative factors — concentration of token holdings, control over protocol upgrades, and dependence on a central developer or company for the network to function — that regulators and courts would use to assess maturity. A network dominated by a single founding company looks very different, under this framework, from one governed by a broad, decentralized validator and developer community. Because this is a facts-and-circumstances test rather than a fixed checklist, specific outcomes for any individual project are not something this page — or anyone outside the SEC or a court — can predict.
Registration, capital, custody, and AML requirements
Firms operating digital commodity exchanges, brokers, or dealers must register with the CFTC (and, where applicable, the SEC) under a new expedited framework. Section 106 directs the agencies to stand up that registration process within 180 days of enactment; firms then have 90 days after the process exists to actually register. Once registered, entities face a set of prudential obligations that mirror traditional securities and derivatives regulation.
| Requirement | What it covers | Source section |
|---|---|---|
| Registration process | SEC/CFTC must build an expedited registration process within 180 days; firms register within 90 days after that | Sec. 106 |
| Capital requirements | Registered exchanges, brokers, and dealers must meet minimum capital standards | Sec. 110 |
| Customer asset custody | Customer funds and digital assets must be segregated and held with qualified digital-asset custodians | Sec. 404 |
| AML / Bank Secrecy Act compliance | Registered entities and associated persons must run anti-money-laundering programs consistent with the BSA | Sec. 406 |
These obligations apply to exchanges, brokers, dealers, and their associated persons rather than to individual users — a distinction that matters for the exemptions described below.
Disclosure obligations for issuers
Primary-market issuers of digital commodities are required to file ongoing disclosures with the SEC until their blockchain system is certified "mature" under the Section 202 test described above — at which point reduced disclosure obligations apply. Section 311 layers on custody and insolvency disclosures, requiring registered platforms to tell customers clearly how their assets are held and what happens to those assets if the platform becomes insolvent. Section 314 goes further and requires registered entities to provide "clear and accessible educational materials" covering how the underlying technology works and how to recognize common fraud red flags — an explicit nod to retail investor protection alongside the market-structure rules.
Together, these disclosure sections are meant to give investors more information earlier in a token's life, while easing the burden once a network has genuinely decentralized. Readers evaluating a specific project's disclosures against these standards should treat this page as background only; the FAQ page addresses common investor questions about what disclosure changes would mean in practice.
Exemptions for developers, validators, and wallet makers
Sections 309 and 409 generally exempt validators, software developers, wallet developers, and blockchain-system creators from SEC/CFTC registration requirements for those specific technical activities — such as running validator infrastructure, writing open-source protocol code, or building non-custodial wallet software. This is not a blanket exemption: anti-fraud liability still applies to everyone under the bill, regardless of registration status.
This carve-out responds directly to a long-running industry concern that broad securities and commodities registration requirements could sweep in people who never take custody of customer funds or control a trading venue — engineers maintaining open-source code, individuals or entities running validator nodes, or companies building self-custody wallet software. The bill tries to draw a line between that kind of purely technical activity and the operation of a registered exchange, broker, or dealer. It is worth repeating that this exemption is narrow: it removes a registration obligation for specific activities, not a shield against fraud claims, and it is also one of the three disputed issues currently holding up a Senate floor vote (see below), since the Senate Banking and Senate Agriculture committees produced different draft language on how far DeFi-related exemptions should extend.
Effective-date ladder: the compliance timeline once enacted
If the CLARITY Act is enacted, its provisions do not all take effect at once. Section 112, together with Sections 403 and 305, lays out a staged rollout so regulators and industry have time to build the required infrastructure before the toughest rules apply.
- 80 days after enactment — The CFTC's review window opens for digital commodity trading certifications (Sec. 403).
- 180 days after enactment — The SEC's blockchain recordkeeping rulemaking is due (Sec. 305); this is also the deadline for the agencies to stand up the expedited exchange/broker/dealer registration process referenced in Section 106.
- 270 days after enactment — Title IV, covering the CFTC's digital commodity market provisions, takes effect.
- 360 days after enactment — All implementing rules must be finalized, and Titles II and III, covering the SEC's provisions, take effect (Sec. 112).
Every one of these dates is measured from enactment — meaning the date a final bill is signed into law — not from today. Since the bill has not been enacted, none of this ladder has started running yet.
Where this stands right now
Nothing in this section-by-section breakdown should be read as a prediction of whether or when the bill will pass. The provisions described above reflect the bill text as introduced and reported out of committee; the Senate could still amend specific sections, including the numbering and substance of the disputed provisions, before any final vote.
Why this matters, by audience
Builders and developers: The Section 309/409 exemptions are the provisions to watch most closely — they determine whether writing protocol code, running a validator, or shipping wallet software triggers federal registration. Because the DeFi-related language is still unsettled between the Senate committees, teams building in this space should track the timeline page rather than assume the House-passed text is final.
Exchanges and brokers: The registration timeline (Sec. 106) and the capital, custody, and AML requirements (Secs. 110, 404, 406) represent the core operational build-out. The 180-day and 270-day markers in the effective-date ladder are the practical planning horizons once — and if — the bill is signed.
Investors: The SEC/CFTC jurisdictional split and the "mature blockchain system" test in Section 202 shape what disclosures you can expect to see, and from which regulator, for a given token. These are legal classifications, not investment recommendations; consult the official resources page for links directly to SEC, CFTC, and congressional materials rather than relying on any single summary, including this one.
Primary sources: H.R. 3633 bill page, congress.gov · full bill text, congress.gov · House Financial Services Committee section-by-section summary (PDF).