A 1946 Supreme Court case about Florida orange groves is still the test that decides whether your governance token gets you sued by the SEC.
The Real Risk: Retroactive Classification
The most damaging pattern in US crypto enforcement isn't a project being told upfront that its token is a security — it's a project launching, building a community, and only later being sued by the SEC on the theory that the token was a security all along. By the time that happens, the liquidity is already gone and the founders are already facing potentially significant civil penalties, regardless of what the project intended at launch.
The test the SEC uses to make this determination comes from SEC v. W.J. Howey Co. (1946) — a case that had nothing to do with technology and everything to do with orange groves sold to investors with a management contract attached.
The Four Elements of the Howey Test
An arrangement is an "investment contract" — and therefore a security — if it involves:
- An investment of money (or something of exchangeable value, which the SEC has treated crypto and even non-monetary contributions as satisfying).
- In a common enterprise — investors' fortunes are tied together, typically through pooled funds or shared dependence on the promoter's efforts.
- With a reasonable expectation of profits — did buyers expect the token's value to increase, and was that expectation part of how it was marketed?
- Derived from the efforts of others — this is usually the decisive element for crypto specifically. If profits depend substantially on a core team's ongoing development, marketing, or management efforts, this element is satisfied even if the token itself has some technical utility.
Why "Efforts of Others" Is Where Most Projects Actually Fail
A token with genuine, working utility at launch can still fail Howey if buyers were realistically expecting the founding team to keep building and marketing in ways that would drive the token's value up. The SEC and courts look past marketing language calling something a "utility token" and examine the actual economic reality: were early buyers functioning as investors betting on the team, or as users acquiring something they'd use regardless of price appreciation?
Progressive Decentralization as a Risk-Reduction Strategy
The concept of "progressive decentralization" — reducing a project's dependence on a central founding team's efforts over time — has become the dominant strategy for managing this risk, though it's a strategy, not a guarantee. The reasoning: if a token starts out heavily dependent on a core team (satisfying "efforts of others" strongly) but genuine control, development, and value-driving activity progressively shifts to a decentralized community or DAO, the "efforts of others" element weakens over time.
This doesn't create a bright-line safe harbor — there's no fixed timeline or percentage of decentralization that the SEC has officially blessed as sufficient. It does, however, meaningfully change the fact pattern a court or regulator would actually be evaluating if the project is challenged years after launch, rather than at the moment of the token generation event.
What This Means for You
If you're building or evaluating a token project, the marketing label ("utility token," "governance token") carries little legal weight on its own — what matters is the actual economic substance: how it's marketed, whether profit expectations are part of the pitch, and how dependent its value is on a specific team's continued effort. This is a genuinely fact-specific, high-stakes legal determination, and this article is not a substitute for securities counsel before a token launch.
Related Kibbo Tools
Sources
- SEC v. W.J. Howey Co., 328 U.S. 293 (1946).
- U.S. Securities and Exchange Commission — Division of Corporation Finance, Crypto Assets guidance. sec.gov