The SEC's Division of Corporation Finance on November 2 added three FAQs to its crypto asset classification framework, addressing when governance participants constitute a "central party" under the March 17 joint SEC-CFTC interpretive release. The additions — Questions 1.4, 1.5, and 1.6 — define ...
"Projects should not be forced to establish decentralized autonomous organizations and offshore foundations or decentralize too early if this is not their desired plan of action." — Paul Atkins, Chairman, U.S. Securities and Exchange Commission
The SEC's Division of Corporation Finance on November 2 added three FAQs to its crypto asset classification framework, addressing when governance participants constitute a "central party" under the March 17 joint SEC-CFTC interpretive release. The additions — Questions 1.4, 1.5, and 1.6 — define the boundary between decentralized governance and centralized control, with direct implications for how protocols structure their token economics and legal entities.
The guidance states that unaffiliated governance participants who have no agreements to act in concert "generally would not be viewed as" a centralized entity. It also confirms that decentralized governance can coexist with formal legal structures such as Wyoming's Decentralized Unincorporated Nonprofit Associations (DUNAs). The distinction between "functional" and "decentralized" — two terms conflated in industry discourse — is now codified in staff interpretation: a functional system can exist without being decentralized, and vice versa.
The timing matters. These FAQs arrive one day before U.S. midterm elections where prediction markets price Democrats at 92-94% for the House and 69% for the Senate. A Democratic majority could stall the CLARITY Act, which would codify many of these same principles in statute. The FAQs may represent the SEC staff's attempt to anchor interpretive ground before a potential legislative shift.
The Division of Corporation Finance published Questions 1.4, 1.5, and 1.6 on November 2, 2026, supplementing the nine FAQs issued on September 25. The total FAQ set now numbers twelve entries addressing the March 17 joint interpretive release.
FAQ 1.4 — Governance Through Legal Entities: Participants in a broad governance system of a functional crypto system who are "unaffiliated with one another" and have "no agreement, arrangement, or understanding to act in concert" generally do not constitute a centralized entity. This holds true even when governance operates "under the auspices of an organization, association, or foundation." The FAQ explicitly acknowledges structures such as DUNAs.
FAQ 1.5 — Supervisory Participation and Access Control: "Supervisory participation" by a centralized entity means authority to control access at the protocol, validator, or user level. This includes the ability to unilaterally grant or restrict access, or to determine or alter voting procedures for software upgrades. The FAQ draws a line between permissioned and permissionless systems.
FAQ 1.6 — Functional vs. Decentralized: The staff states that "functional" means a native crypto asset "can be used on the system in accordance with the system's programmatic utility," while "decentralized" means the system "operates autonomously without any person, entity, or group possessing operational, economic, or voting control." These are "distinct concepts" that "address different characteristics."
All three FAQs carry the standard disclaimer: they represent staff views only, have no legal force, and create no binding obligations.
The November 2 FAQs operate within the architecture established by the SEC-CFTC joint interpretive release of March 17, 2026 — a 68-page document that established a five-category taxonomy for crypto assets:
The release classified 16 specific crypto assets as digital commodities: BTC, ETH, SOL, XRP, DOGE, ADA, AVAX, LINK, DOT, HBAR, LTC, BCH, SHIB, XLM, XTZ, and APT. These 16 tokens represent the majority of market capitalization in the crypto asset class.
The interpretive release also confirmed that protocol mining, protocol staking (including liquid staking), token wrapping, and certain no-consideration airdrops do not constitute the offer and sale of securities.
Before the November 2 additions, the Division of Corporation Finance had published nine FAQs on September 25, addressing classification mechanics and the investment contract analysis:
The September FAQs established that functionality is the trigger point: once a system is functional, the issuer's ongoing work does not automatically create a securities relationship. The November additions now clarify the governance layer that sits on top of functional systems.
The operational significance of FAQ 1.4 lies in where it draws the boundary of "central party" status. Under the March 17 framework, a crypto system's classification depends on whether a central party exercises control. The November guidance defines two conditions that must both be met for governance participants to qualify as a central party:
Token holders who vote on governance proposals without coordination agreements do not meet either condition, according to the staff's interpretation. Even organized governance through a foundation or DUNA does not automatically create central party status.
The practical effect: protocols with governance token structures — which constitute the majority of DeFi protocols by TVL — now have staff-level guidance that their governance participants are not, by default, centralized entities. This is relevant to Uniswap (UNI), Aave (AAVE), Compound (COMP), MakerDAO (MKR), and hundreds of other governance-token protocols.
FAQ 1.4's explicit reference to DUNAs is the first SEC staff acknowledgment of Wyoming's 2024 Decentralized Unincorporated Nonprofit Association framework. Wyoming enacted the DUNA statute in March 2024, establishing a legal structure that grants DAOs formal legal status while preserving decentralized governance.
DUNAs require a minimum of 100 members joined by mutual consent for a common nonprofit purpose. They provide limited liability protections for members and administrators — a critical gap in DAO governance that left participants exposed to general partnership liability under prior case law.
The SEC staff's position that governance "under the auspices of" such an entity does not create central party status addresses a long-standing compliance question: whether wrapping a DAO in a legal entity transforms its governance participants into a centralized group.
According to a16z Chief Legal Officer Miles Jennings, the FAQ "clarifies how systems can maintain decentralized governance while using legal entities such as DUNAs." The framework effectively permits protocols to adopt legal wrappers for tax, liability, and regulatory purposes without sacrificing their non-security classification.
FAQ 1.6's separation of "functional" and "decentralized" resolves a persistent ambiguity. The March 17 release used both terms in defining when a crypto asset exits securities classification, but the relationship between them was unclear. The November FAQ establishes:
The distinction matters because it creates a staged compliance path. A project can achieve functionality — making its token a potential digital commodity — before achieving full decentralization. The two milestones are independent.
However, the guidance also implies that a functional-but-centralized system could still have tokens subject to the investment contract analysis if a central party's managerial efforts drive profit expectations. Functionality alone does not guarantee non-security status; it is a necessary but not sufficient condition.
The FAQs landed November 2, one day before U.S. midterm elections. As of October 30, prediction markets priced Democratic control of the House at 92-94% and the Senate at 69%, according to Kalshi and Polymarket data. More than $1.4 billion has been traded on midterm markets.
The CLARITY Act — which would codify the SEC-CFTC taxonomy in statute and establish formal definitions for "functional," "decentralized," and "central party" — failed a September Senate procedural vote. A Democratic-controlled Congress is expected to deprioritize the legislation or push for stricter oversight models.
As journalist Eleanor Terrett noted, the FAQ update "looks like an effort to clarify some of the decentralization questions the Clarity Act would address in law." Crypto attorney Avi Lev countered that "an FAQ is not law," questioning whether the update reduces or increases pressure on lawmakers to act.
The legal vulnerability is real. FAQs carry no legal force, represent only staff views, and can be rescinded or revised by a future administration. Under a different SEC chair, the same staff could issue contradictory guidance. By contrast, the CLARITY Act would require Congressional repeal to undo.
For protocols, this creates a regulatory gap: the interpretive framework provides clarity, but that clarity rests on non-binding staff opinions rather than statute or formal rulemaking.
The combined March, September, and November guidance creates a practical roadmap for token projects, with several implications:
Governance tokens gain clearer footing. Protocols with broadly distributed governance tokens — where no single entity controls more than a threshold share of votes and participants are unaffiliated — can structure their governance without triggering central party classification. This applies to the hundreds of DeFi protocols using governance token models.
Legal wrappers are permissible. Projects can adopt DUNAs, foundations, or similar legal entities for operational purposes without automatic reclassification. The liability protections of a legal wrapper no longer conflict with the decentralization requirement.
Buybacks and marketing are narrowly permitted. Post-functionality token buybacks and promotional activities do not constitute essential managerial efforts, provided no central party exists. This gives projects limited room for treasury operations.
The "functional" milestone is self-defined. The FAQ notes that "each issuer determines the thresholds that must be met to achieve functionality and/or decentralization for purposes of its own representations or promises." This grants flexibility but also creates enforcement ambiguity: the SEC could challenge an issuer's self-assessment.
Admin keys remain a risk factor. FAQ 1.5's definition of supervisory participation — unilateral access control, upgrade authority — means protocols retaining admin keys or multisig control over core contracts remain exposed to central party classification.
The November 2 FAQs represent incremental but consequential clarification of the SEC's eight-month-old token taxonomy. They answer specific questions that have constrained protocol governance design and legal structuring since the March interpretive release. The recognition of DUNAs, the separation of functionality from decentralization, and the definition of central party boundaries each remove a practical obstacle for token projects.
The constraint is durability. Staff FAQs are the lowest tier of regulatory guidance — below formal rules, interpretive releases, and no-action letters in terms of binding authority. With the CLARITY Act unlikely to advance under a potentially Democratic Congress, the industry operates under a framework that is comprehensive in scope but fragile in legal standing.
For protocols, the immediate path is clear: distribute governance broadly, avoid concentrating access control, and consider DUNA or equivalent legal structures. The longer-term question — whether this framework survives a change in SEC leadership — remains unanswered.