What is self‑certification? Crypto’s permission model, turned inside out
———————————————————————
For years, a token’s legal fate in the United States depended on what the SEC *might* do someday. Status was whatever a later lawsuit, settlement, or speech implied it had been all along. The CLARITY framework inverts that posture. Instead of projects waiting indefinitely for the regulator’s blessing or enforcement, networks declare their own legal “coming of age” and the government is put on a clock to disagree.
At the heart of this shift is self‑certification: a structured process where a project states that its network has reached “maturity,” files that conclusion with supporting analysis, and moves forward unless the SEC formally objects within 60 days. If the agency stays silent, the project’s assertion hardens into law: the asset is treated as a digital commodity, regulated primarily by the CFTC, not as a security.
This is not a minor procedural tweak. It changes the baseline from *prohibition by ambiguity* to *permission unless rebutted*, and that flips who carries the burden of action, and when.
—
What does “maturity” actually mean?
CLARITY uses “maturity” as the key threshold that marks a token’s exit from securities law. To understand it, you have to start with the problem the framework is trying to solve.
A typical token begins life inside a classic securities setup:
– The initial sale looks like an investment contract: money goes in, a team promises to build.
– The token itself, often described in the bill as an “ancillary asset,” is closely tied to the ongoing efforts of a specific organization or founding group.
– As long as buyers reasonably rely on that identifiable team to drive value, securities law has a hook: investors are depending on the work of managers, so they’re entitled to structured disclosure about those managers.
But blockchains are intentionally designed *not* to be forever run by a small group. Over time:
– Validation spreads to independent participants.
– Development becomes open, with many contributors.
– Governance shifts from a founding company to token holders, community mechanisms, or other decentralized arrangements.
Once a network truly functions without any one person or coordinated group being in charge, the original securities logic fades. There is no longer a central “manager” whose special efforts are powering the token’s value. At that point, CLARITY says the network has reached maturity-and that maturity is what gets certified.
—
The two‑part test: functionality and decentralization
The CLARITY framework gives maturity a working test with two main pillars:
1. Functionality
The network needs to be real and operational:
– It processes transactions.
– It performs the functions it promised (payments, smart contracts, data storage, or whatever its whitepaper described).
– It is more than a pitch deck or a testnet posing as the finished product.
This requirement aims to keep teams from certifying empty shells or barely functional prototypes as mature digital commodities.
2. Decentralization, anchored by the 20% rule
The bill introduces a sharp line that the industry has been talking about for years without ever having in law: no single person, or group under common control, can hold 20% or more of the tokens or of the voting power if the network is to be treated as not controlled.
That numeric threshold turns vague decentralization talk into something measurable. It forces concrete decisions on:
– Treasury size and how fast it is distributed.
– Founder and early team allocations.
– Validator or node concentration.
– Voting rights in governance mechanisms.
These are no longer just optics or investor relations topics; they become regulatory design choices that need to be defensible on paper.
If both prongs are met-real functionality and lack of concentrated control under the 20% line-the network can be certified as mature.
—
What does certification actually buy a project?
Self‑certification is not a press release; it is a legal switch.
Once a network is certified as mature and that certification is allowed to stand:
– The token is treated as a digital commodity, not a security.
– The asset migrates out of core SEC jurisdiction and into a CFTC‑style regime.
– Originator‑specific securities disclosure requirements fall away.
– Registered digital commodity exchanges can list the asset under commodity rules.
– Brokers, custodians, and other intermediaries handle it under a commodity framework instead of securities rules.
– The SEC’s enforcement toolkit for securities violations is sidelined with respect to that token’s trading as a commodity.
This is the first time U.S. law sketches a clear, forward‑looking path from token launch, through a securities phase, to commodity status-without requiring a bespoke no‑action letter, years of silence, or a lawsuit.
Self‑certification is the door that opens that path.
—
How the self‑certification process actually works
The procedure is structured, and each step is designed to allocate power and responsibility:
1. Who can file
A certification can be submitted by:
– The original issuer.
– An affiliate of the issuer.
– Or-most notably-a decentralized governance system (for example, a DAO) that controls the network.
That last category is quietly radical. It acknowledges that a network may outlive or outgrow its founding company. If the original entity has dissolved, relocated, or stepped back, the on‑chain governance system itself is not left stranded; it can assert maturity and seek commodity treatment for its token.
2. What gets filed
The filing is not just a checkbox form. It must:
– State that the network meets the maturity criteria.
– Provide a detailed explanation of how the functionality and decentralization tests are satisfied.
– Document token distributions, voting power, governance design, and any relevant control relationships.
– Address foreseeable edge cases, like large but non‑voting holdings or delegated control.
3. The 60‑day clock
Once the certification is filed, the SEC gets a fixed period-60 days-to push back. During that window, the agency can:
– Accept the filing by taking no action, allowing the certification to stand.
– Object, arguing that the network has not actually reached maturity.
– Request more information or clarification, which may itself influence timelines and strategy.
If the SEC does nothing within the deadline, the certification effectively locks in: the token’s status as a digital commodity becomes the new legal default.
4. Shifting the burden
Historically, projects needed to knock on the SEC’s door, hoping for guidance the agency rarely issued. Under self‑certification:
– Projects initiate the process.
– The presumption is that they are correct unless the SEC can make a timely, reasoned case otherwise.
– The burden of initiative and explanation moves from the builder to the regulator.
This is the core inversion: permission is assumed after a structured filing unless the government actively rebuts it.
—
Can a DAO really certify its own network?
Under the CLARITY model, yes-if it truly functions as the network’s governing body.
A decentralized governance system can submit a certification when:
– The original corporate sponsor no longer controls the network, or may not even exist in its original form.
– Decisions about upgrades, parameters, or treasury spend are made according to on‑chain or protocol‑defined rules.
– No single participant or coordinated group breaches the 20% control threshold over tokens or votes.
Practically, that means a DAO must:
– Have governance processes transparent enough to describe in regulatory filings.
– Be able to demonstrate how proposals are made, voted on, and executed.
– Document that no one actor (or affiliated group) effectively dominates the system, even through soft power or vote delegation.
This is one of the more forward‑looking features of CLARITY: it treats on‑chain institutions as legitimate counterparts in the regulatory arena, not as legal ghosts.
—
Where did this self‑certification model come from?
The crypto world did not invent the idea of regulated entities declaring compliance and proceeding unless stopped. Similar “certify‑and‑go” structures exist or have existed in other areas of law and regulation:
– Certain types of financial products can be launched under frameworks where disclosure and internal checks are structured by rule, and regulators intervene by exception.
– In some sectors, businesses file certifications or notices of compliance with technical standards or safety regulations, operating on the understanding that regulators will audit, inspect, or challenge only if they see warning signs.
– Telecoms, environmental regulations, and even aspects of banking law have used variants of self‑attestation with oversight, rather than pre‑approval, as the baseline.
CLARITY borrows that logic and applies it to the token lifecycle. Instead of an opaque, one‑off approach where every network lives in limbo, the framework attempts to standardize how a project can announce, “We are now beyond investment‑contract dependence; treat this as a commodity unless you have specific grounds not to.”
In that sense, self‑certification is less a radical invention and more a transplantation of familiar regulatory machinery into crypto.
—
The 20% line: why that number matters so much
The 20% threshold is the most talked‑about number in the framework because it finally pins decentralization to a concrete metric.
Key implications:
– Founder and team allocations: Large pre‑mines or concentrated holdings by a company and its insiders now have clear legal consequences. If a founder group keeps 30-40% of supply indefinitely, it will be extremely difficult to argue that no one controls the network.
– Treasuries and foundations: Many networks have big protocol treasuries or foundation holdings. Under CLARITY, the questions become:
– Who actually controls those wallets?
– Are there robust checks and balances?
– Does the governance around those funds effectively put more than 20% of voting or economic power in one set of hands?
– Validator and node concentration: If block production or validation is heavily dominated by a small number of operators, that concentration may undermine claims of decentralization, especially when combined with token or governance control.
– Token distribution strategies: Airdrops, community distributions, vesting schedules, and secondary sales all take on a compliance dimension. The way tokens leave insider hands-and the way voting power is delegated-will be central evidence in any dispute over maturity.
The 20% line is not a magic guarantee of decentralization, but it is a bright line: cross it, and your filing must explain why control is still meaningfully diffused despite that concentration, or you should expect a challenge.
—
How can the process be gamed-and what stops that?
Any rule with numeric thresholds invites attempts to game it. Likely tactics include:
– Splitting holdings across related entities to appear under 20% while still coordinating.
– Using nominees or custodial structures so that a single controller sits behind many ostensibly independent wallets.
– Engineering governance rules where one actor has outsize agenda‑setting power despite only moderate token ownership.
– Creating informal influence networks (e.g., a dominant developer team) that effectively dictate outcomes, even with dispersed token holdings.
CLARITY anticipates some of this by focusing not only on raw token counts, but on “persons or groups under common control” and on voting power, not just ownership. That means:
– Corporate structures, contracts, and actual decision‑making patterns matter.
– A cluster of entities, all controlled by the same individuals, is treated as one for the 20% calculation.
– Delegated voting arrangements and veto rights must be disclosed and analyzed, not hidden behind technicalities.
Still, enforcement will always lag ingenuity. The true guardrail here is the combination of:
– The risk of SEC challenge, including the possibility of enforcement if the certification is found misleading or fraudulent.
– The paper trail a filing creates, which can be used later in litigation if the facts diverge from what was represented.
False or overly aggressive certifications may buy time in the short run but can become powerful evidence against a project if regulators or courts later decide the maturity claim was not credible.
—
What happens if the SEC challenges a certification?
If the SEC believes a network has not actually reached maturity, it can formally object within the 60‑day window. That triggers a more adversarial process:
– The SEC will articulate why it thinks the functionality or decentralization criteria are not met.
– The project (or DAO) will need to defend its analysis, supply additional evidence, or, in some cases, reconsider and withdraw or delay the certification.
– The dispute can escalate into formal proceedings, negotiations, or eventual litigation.
Consequences for a failed certification can include:
– The token remaining squarely under securities law, with continued or expanded disclosure obligations.
– Potential enforcement action if the agency concludes that the filing was materially misleading.
– Market and reputational damage from the failed attempt.
Because of these stakes, self‑certification is not a casual marketing milestone; it’s a high‑stakes legal assertion that should be treated with the same seriousness as a major securities filing.
—
How should projects prepare in practice?
Any project considering self‑certification under CLARITY should treat the process as a multi‑year design and documentation effort, not a last‑minute checkbox. Practical steps include:
1. Architecting decentralization from the start
– Plan token allocations, vesting, and treasury structures with the 20% line in mind.
– Avoid architectures that require a permanent central operator to keep the chain alive.
– Build real paths for power to diffuse-both economically and in governance.
2. Documenting the network’s evolution
– Keep rigorous records of token distributions, governance votes, validator sets, and major upgrades.
– Track how decision‑making authority has shifted away from the founding group over time.
3. Designing resilient governance
– Ensure that voting systems, proposal rules, and on‑chain mechanisms make capture by one actor difficult.
– Address how conflicts of interest are managed, and how core contributors can be replaced or overridden.
4. Strengthening functionality
– Ship real, robust features that match the network’s stated purpose.
– Demonstrate usage, reliability, and independence from any one company’s infrastructure.
5. Preparing a defensible analysis
– Treat the certification memo like a comprehensive legal brief.
– Anticipate SEC questions on gray areas: large partners, strategic investors, or infrastructure dependencies.
– Be candid about risks and ongoing centralization pressures; regulators are more likely to trust filings that acknowledge reality.
Projects that plan for maturity from day one will be in a far stronger position when they finally choose to certify.
—
Honest failure modes: where self‑certification can break down
Even with good faith on all sides, the model has real vulnerabilities:
– Over‑optimistic projects
Teams may sincerely believe they are decentralized and functional when, in practice, they are still the key coordinators. Overconfidence, not malice, can still produce flawed certifications.
– Captured or ineffective DAOs
A DAO on paper may be controlled by a small clique in practice. Low voter turnout, dominance by a few large wallets, or complex governance mechanics can undermine the appearance of decentralization.
– Regulatory over‑reaction
The SEC could decide to challenge a large share of certifications, slowing the process and re‑creating uncertainty. If every filing is treated as suspect, the practical benefits of the new default may erode.
– Ambiguity around technical dependencies
Even if token and voting distributions are decentralized, heavy reliance on one company’s infrastructure (such as hosted nodes or proprietary code) may raise questions about real‑world control.
– Legal lag behind technical innovation
New token models, cross‑chain systems, or novel governance structures might not fit neatly into the 20% or two‑prong framework, creating fresh gray zones.
These failure modes do not invalidate self‑certification, but they define where the next wave of legal and policy debates will likely concentrate.
—
Why reversing the default matters so much
The deepest innovation in CLARITY is not the specific percentages or the wording of the tests; it is the change in who must act to shape a token’s status.
Under the old environment:
– Silence and uncertainty were the norm.
– Builders often chose not to engage with U.S. regulators at all, or they architected around them.
– The absence of a clear path pushed some activity abroad and kept compliant actors on the sidelines.
Under a self‑certification regime:
– Projects willing to meet clear standards can affirmatively claim their place.
– The SEC must either articulate its objections on a timeline or let the certification stand.
– Markets, exchanges, and intermediaries gain a more predictable way to evaluate which assets belong under a commodity rule set.
That doesn’t make the system simple or risk‑free. It does, however, replace endless waiting and guesswork with a structured process that can be tested, refined, and argued over in the open.
In effect, CLARITY tries to move crypto from a world where permission is granted by silence and fear to one where permission exists by rule-and where government objections, when they come, are at least forced into the light.