DAO Token Voting Does Not Equal Control: What the SEC Guidance Says

KTX
KTX
  • Updated

SEC staff clarified on November 2, 2026 that participating in broad-based token governance does not automatically make voters a controlling group. The update matters because a DAO can have many voters while decision-making power remains concentrated elsewhere. The question is who can actually direct the system. The new answers are nonbinding staff guidance, and their scope is narrower than a general exemption for DAOs or governance tokens.

KTX News illustration separating DAO token voting from execution keys and system permissions

A governance vote reveals one part of a system’s decision process. Actual authority requires a closer look.

What the new SEC answers establish

The Division of Corporation Finance added Questions 1.4–1.6 to its crypto-asset FAQs. Question 1.4 says participants generally will not be treated as a group for this purpose when they are unaffiliated and have no separate formal or informal agreement, arrangement or understanding to act together, including through delegation, outside governance participation itself. The assessment remains fact-specific.

Broad-based is a substantive qualification: proposals, deliberations, voting mechanisms, outcomes and implementation must be publicly recorded and accessible to stakeholders on a timely basis. Decisions must follow pre-established, objective procedures that a single stakeholder or coordinated group cannot unilaterally change except through those procedures, while participation and decision authority must not be concentrated with one stakeholder or an affiliated or coordinated group, including through delegation. It is not simply a label for any token poll.

Two questions therefore remain distinct: whether participants form a group, and whether that group has operational, economic or voting control. Any of those forms of control can matter; all three are not required. Merely adding up everyone who voted does not answer either question.

The qualification is important. Footnote 3 confines this view to digital-commodity classification in Section III of the March interpretation. It does not change other statutory group definitions, expressly including the Exchange Act definition of an exchange. It supplies no blanket conclusion about participant liability, exchange registration or any named token. The Commission has neither approved nor disapproved the staff FAQ’s contents.

Follow the authority after the vote closes

Consider a hypothetical DAO with thousands of token-holding addresses. One arrangement lets independent stakeholders propose changes, debate them publicly and implement successful votes through established procedures. Another collects an advisory poll while a small team retains discretion to ignore the result. Both display voting activity, but the practical authority differs. These examples illustrate questions to investigate, not legal findings about a particular project.

Visible governance feature Further evidence to examine Why it matters
Many token-holding addresses Affiliations and delegated voting power Addresses do not establish independent decision-makers.
A proposal passes Execution transactions, vetoes and permissions Approval and implementation may be separate steps.
A published voting process Who can change its rules Procedures may constrain or preserve discretion.
The network works Authority over code, access and validators Utility and autonomous operation address different issues.

Conceptual DAO decision path from token holders through delegation, proposals and voting to execution permissions

Participation, the distribution of voting power and implementation authority should be examined separately.

Question 1.5 focuses on unilateral powers over access, upgrade or distribution voting procedures, validator participation, code changes and transaction reversal. It also describes conditional cases where all material ongoing operations run automatically without individual discretion, or discretion rests solely with qualifying broad-based governance whose participants are not a central party. The presence of software alone does not resolve who can intervene.

A functioning token is not a complete decentralization test

The underlying Commission interpretive release was issued on March 17 and became effective on March 23, 2026. Its classification framework and the November staff clarification distinguish a token’s programmed usefulness from a system’s autonomy. A working application demonstrates something different from the absence of a person or group with controlling powers.

That distinction is useful when reading a project’s roadmap. Shipping a feature, reaching a user milestone or opening a voting portal provides operational information. It does not, by itself, explain whether privileged permissions were removed, retained or transferred. A governance transition should be understood through the permissions and procedures that actually changed.

Asset classification also differs from evaluating an offer or transaction involving the asset. The March release addresses how a non-security crypto asset can be involved in an investment contract. A governance label cannot replace analysis of the associated rights, representations and promised managerial efforts.

Why the 2017 DAO report still provides a useful comparison

In its July 2017 report on The DAO, the SEC concluded that the tokens in that particular offering were securities. Voting rights did not give holders meaningful control over the enterprise in the circumstances described. Curators screened proposals, and dispersed holders faced practical limits on collective action. The report examined the offering’s economic reality rather than accepting its governance label.

This answers a different question from the November 2026 clarification. The older report considered whether investors depended on others’ managerial efforts. The new FAQ addresses when governance participants are grouped as a central party within a particular classification framework. It should not be read as a universal reversal of the earlier findings.

The practical connection is straightforward: a voting right alone does not settle the relevant control question in either direction. Neither “everyone has a vote” nor “somebody voted” provides a complete account of how a system operates.

What token holders can check in practice

A useful review follows the decision from proposal to execution:

  1. Identify the decision and the system. Establish whether a vote concerns the base network, an application, a treasury or an advisory position. Authority over one component should not automatically be attributed to every connected component.
  2. Map effective voting power. Examine delegation, affiliations, participation and procedural thresholds. A distribution chart can show token balances while missing delegated influence or relationships between participants.
  3. Trace implementation. Compare the approved proposal with the actions actually executed. Read the mandates of multisig signers, upgrade administrators and emergency roles. Determine which actions are automatic, which require approval and which permit discretion.
  4. Check whether the arrangement persists. Review subsequent changes to roles, rules and delegation. A governance document describes an arrangement; later executed changes show whether that description still fits.

Comparison of visible DAO voting features with evidence about delegation, execution rights, code access and decision authority

Evidence about permissions and execution adds context to a vote count; the diagram supplies no legal verdict or numerical threshold.

KTX’s explanation of Lido’s governance and execution process provides a concrete way to distinguish voting rights from protocol implementation. Its coverage of Pyth’s DAO authorization and operational execution illustrates another decision chain. These are governance examples, not SEC classifications of those projects.

For market participants, governance evidence helps explain exposure to upgrades, treasury decisions and operational disruption. It does not establish a token’s fair value or predict its price. The next useful evidence is an actual change in authority, rather than the popularity of a decentralization claim.

Frequently asked questions

Does a multisig automatically establish centralized control?

No. Its mandate, permissions, discretion and relationship to governance matter. A signer executing an approved instruction presents a different question from someone able to change the rules unilaterally.

Do different wallet addresses necessarily represent independent voters?

No. One actor can use multiple addresses, and delegation can concentrate voting power. Wallet counts alone cannot establish independence or a coordinated group.

Does a governance token automatically represent company shares?

No. Examine the actual legal and economic rights. A protocol vote does not by itself establish equity ownership, a dividend entitlement or the token’s securities status.

Can a foundation still control an application on another network?

Yes. Footnote 4 says an organization or foundation could itself be a central party over another system, including by setting an application’s operating parameters. The analysis must identify the relevant system.

This article is for information only and is not legal or investment advice. Governance arrangements and applicable requirements must be assessed on their specific facts.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request