SEC Staff Clarifies How Governance and Control Shape Crypto Classification

Three New Answers on Crypto Governance

The SEC’s Division of Corporation Finance added three answers to its crypto-asset FAQs on November 2, 2026. Questions 1.4 through 1.6 address governance participation, control over network access, and the relationship between functionality and decentralization.

The new entries expand on the Commission’s March 17 interpretation. They are nonbinding staff views, not a new law or binding SEC rule.

That makes this a fresh clarification within an existing framework. Its significance is in explaining how staff approaches the questions, rather than declaring a final classification for every governance token.

---

When Governance Participants Form a Central Party

The staff says unaffiliated participants in broad-based governance generally are not treated as a group under this central-party analysis when they have no separate formal or informal agreement to act together. The assessment remains dependent on the circumstances.

The update also addresses unilateral powers over access, voting procedures, validator participation, code, and transactions. Functionality concerns whether an asset can perform its programmed use; decentralization concerns the absence of operational, economic, or voting control by a central party.

Taken together, those points put attention on how a system works and who can exercise authority within it. The presence of a governance mechanism is only the beginning of that examination.

---

The Questions I Would Ask About a Network

My takeaway is that the most useful project research starts with specific powers. Who can approve a change? Who can stop one? What process must be followed, and who has the practical ability to complete it?

Consider two hypothetical networks with public voting pages. In one, a single administrator can disregard the result. In the other, changes depend on a procedure that no participant can bypass alone. Their interfaces might look similar, but a researcher would want to understand the difference in authority.

That example illustrates a due-diligence approach, rather than supplying a legal verdict on either network. Reaching a conclusion would require the actual facts, including how permissions and decision-making operate in practice.

I would also compare project descriptions with the documents and mechanisms that govern changes. A claim of community involvement is more useful when a reader can trace how a proposal becomes an implemented decision.

---

A Working Product Answers Only Part of the Question

Separating functionality from decentralization helps avoid an overly simple shortcut. Showing that a product works gives a researcher evidence about utility. Understanding who controls that product requires an additional investigation.

A hypothetical application might deliver a valuable service while allowing a small operator group to make major changes. Another might distribute decision-making more widely while struggling to attract users. Those are different business and governance characteristics.

For investors evaluating projects, that suggests keeping separate notes on utility, adoption, governance, and control. Combining them into a single label can hide weaknesses that would otherwise be visible.

An impressive user count, for example, cannot explain who holds an administrative permission. A well-documented voting process cannot establish whether customers find a service useful. Each claim needs evidence suited to the question.

---

Clarity Has Value Without Settling Every Case

The practical value of the update is that it gives readers more precise questions to investigate. It does not supply a blanket approval for decentralized finance, foundations, or projects with governance tokens.

I would be cautious about market commentary that jumps straight from this clarification to a list of supposed regulatory winners. A broad statement about how staff evaluates control still has to be applied to an individual system.

The next useful step is to look at how projects explain their own authority structures in light of these questions. Clearer documentation could help users understand what they are participating in and where important decisions sit.

For tomorrow’s discussion, the central development is straightforward: SEC staff has added detail to its treatment of governance and network control. That is meaningful regulatory context, while the underlying assessment remains specific to the facts of each system.