SEC's 5-Category Crypto Framework: Still Need a Lawyer to Figure Out Which Category Our Token Is

I’ve been building in crypto since 2017, survived one failed startup and one modest exit, and I’m currently co-founding a Web3 startup in Austin. When the SEC announced their crypto classification framework on March 17th, I was cautiously optimistic. Finally—regulatory clarity!

Two weeks later, after three calls with securities lawyers and $15K in legal fees, I can confidently say: We have a framework, but we still don’t have clarity.

The Five Categories Sound Simple… Until You Try to Use Them

The SEC created five categories:

  1. Digital Commodities (BTC, ETH, SOL + 13 others)
  2. Digital Collectibles (NFTs, memecoins)
  3. Digital Tools (membership tokens, tickets, credentials)
  4. Stablecoins (payment-focused stable value tokens)
  5. Digital Securities (everything with profit expectations)

On paper, this looks great. In practice? Every category has a footnote that says “depends on facts and circumstances.”

Our Startup’s Classification Nightmare

We’re building a protocol with a governance token. Sounds straightforward—governance = digital tool, right?

Not so fast. Our lawyers spent six hours analyzing these questions:

:american_football: Question 1: Does the token control protocol revenue? (If yes, might be a security)

:american_football: Question 2: Did we make any forward-looking statements about value in our marketing? (If yes, might be a security)

:american_football: Question 3: Is the protocol fully decentralized, or does our team still make key decisions? (If centralized, more likely a security)

:american_football: Question 4: Can token holders vote to change revenue distribution? (If yes, might be a security)

Every answer required legal interpretation. The framework doesn’t provide bright-line tests—it provides factors to analyze.

The Real-World Impact on Startups

For well-funded projects: This framework is manageable. Spend $50-100K on legal, get classification opinion, proceed with caution.

For bootstrapped teams: This is a disaster. We’re pre-seed. That $15K legal bill is 10% of our runway. And the advice we got was basically “here are the risks, proceed carefully, maybe.”

For international competitors: They’re laughing. A similar protocol incorporating in Singapore or Switzerland doesn’t deal with this complexity. They can ship faster, cheaper, and iterate without classification anxiety.

What About Algorithmic Stablecoins?

The framework mentions stablecoins but doesn’t clearly address algorithmic models. Is UST-style algorithmic stablecoin a “stablecoin” or a “digital security”? The guidance says “stablecoin arrangements outside those described may be securities, depending on facts.”

So… we still don’t know. Another legal bill to figure it out.

The Frustrating Part

We WANT to comply. I’m not anti-regulation. Legitimate frameworks unlock institutional capital and protect users. But this framework doesn’t make compliance easier—it just creates five categories of ambiguity instead of one.

The old question was: “Is it a security?”

The new question is: “Which category, and under what interpretive analysis, considering facts and circumstances, with ongoing monitoring for changes?”

That’s not simpler. It’s lawyer employment insurance.

Should We Incorporate Elsewhere?

Here’s the real question our team is debating: Do we move the company offshore?

I don’t want to. I’m from Austin, I love the US startup ecosystem, and I believe in building here. But when a competitor in the Cayman Islands can launch the same product without classification analysis, we’re playing with one hand tied behind our back.

Is regulatory clarity worth losing competitive speed and burning runway on legal fees?

Question for the Community

Am I overreacting? Are other founders feeling this same frustration?

For the developers and protocol founders here: How are you handling classification? Are you getting legal opinions? Incorporating offshore? Just shipping and hoping for the best?

And for anyone with regulatory expertise: Does this framework actually help small teams, or just formalize the advantage of well-funded players?

I’m genuinely asking—maybe I’m missing something. But right now, this feels like clarity in name only.


Not legal advice. Just one founder’s frustrated perspective after two weeks of trying to use this “clear” framework.

Steve, I feel your frustration. I’m building a DeFi interface and was planning to launch a governance token this summer. After reading the SEC guidance, I spent three days trying to figure out which category we’d fall into—and I’m still not 100% sure.

The Staking Clarity Was Huge (for me at least)

The one thing I’m genuinely relieved about is that Ethereum is officially a digital commodity and staking is classified as an “administrative activity” rather than a securities offering. That’s massive for anyone building on proof-of-stake chains.

For years, there was this anxiety that staking ETH might be offering an unregistered security. Now we know: participating in network consensus ≠ securities transaction. That removes a huge legal overhang for PoS ecosystems.

But Governance Tokens? Still Confused

Here’s my situation: we’re building a protocol where users vote on which yield strategies to deploy. The token is purely for governance—no revenue sharing, no profit distributions, just voting rights.

Based on the guidance, that should be a “digital tool” (practical function = governance, value from functionality not passive yield). But then I read this footnote: “A digital tool can become a security if issuers make representations about value appreciation or profit expectations.”

So if we say anything in our marketing about how governance could lead to better protocol outcomes, which could increase token value… did we just turn a digital tool into a security?

The guidance doesn’t give clear examples of governance tokens. It just says “depends on facts.”

Question for Anyone with Regulatory Expertise

If a token:

  • Grants voting rights on protocol parameters
  • Does NOT distribute revenue to token holders
  • Does NOT promise profits
  • Controls technical decisions (which yield strategies, which integrations)

Is that a digital tool or a digital security?

Or does it depend on whether the protocol itself generates revenue, even if token holders don’t receive it directly?

I genuinely don’t know. And like Steve said, getting a legal opinion costs $15-30K. For a bootstrapped project, that’s a non-starter.

The International Competition Problem

I agree with Steve’s point about offshore competitors. I have a friend building something similar in Portugal—they’re launching next month with zero classification analysis. No legal fees, no multi-month delays, just ship and iterate.

Meanwhile, I’m here reading 68 pages of SEC guidance trying to figure out if my governance-only token is a “tool” or a “security.”

I don’t want to move offshore. I believe in building legitimate, compliant products. But the framework makes compliance so expensive and uncertain that it’s pushing projects away from the US.

Still Better Than Before?

I guess the one silver lining is that we’re no longer debating first principles. The SEC laid out categories. That’s progress.

But “progress” that still requires $30K in legal fees to interpret isn’t accessible to most builders. And that worries me.

Anyone else in a similar position? How are you thinking about governance token classification?

As someone building a yield optimization protocol with a stablecoin component, the stablecoin category is an absolute mess. And Steve, I share your frustration about international competition—we’ve seriously considered moving to Switzerland.

The Stablecoin Classification Gap

The SEC framework defines stablecoins as crypto assets “designed to maintain a stable value relative to a reference asset.” Sounds simple.

But then it adds: “stablecoin arrangements outside those described by the Interpretation may be securities, depending on facts.”

What does that even mean?

Here are real-world stablecoin models that the guidance doesn’t clearly address:

1. Algorithmic Stablecoins

UST-style algorithmic stables that maintain peg through mint/burn mechanisms—are these “stablecoins” or “digital securities”? The framework doesn’t say. After Terra/Luna, you’d think they’d clarify this explicitly.

2. Yield-Bearing Stablecoins

Tokens like sUSDe or Ethena’s USDe that maintain dollar peg BUT also generate yield from underlying assets. Is that a stablecoin + digital security hybrid? Do we need dual registration?

3. Over-Collateralized Stables

DAI and similar tokens backed by crypto collateral—they’re decentralized, but does the MakerDAO governance token make the stablecoin itself a security offering?

4. Rehypothecated Stables

If our protocol takes USDC, lends it on Aave, wraps the aToken, and issues a yield-bearing derivative—did we just create a security? A stablecoin? Both?

Our Specific Problem

We’re building a cross-chain yield aggregator. Here’s the product flow:

  1. User deposits USDC
  2. Protocol deploys to highest-yield strategy (voted by governance token holders)
  3. User receives yUSDC (yield-bearing receipt token)
  4. yUSDC maintains ~$1.00 value but accrues yield over time

Based on the guidance, I think this means:

  • USDC = stablecoin (clear)
  • Governance token = digital tool or digital security (depends on “facts”)
  • yUSDC = ??? (stablecoin because it tracks $1? Or digital security because it generates yield?)

We’ve asked two different law firms. We got two different opinions.

One firm said yUSDC is a digital security (yield = profit expectation from our managerial efforts).

The other firm said it’s a stablecoin with yield characteristics, similar to a bank savings account (not a security).

The Economics Don’t Work

Here’s the brutal math:

  • Legal opinion #1: $35K
  • Legal opinion #2: $28K
  • Total spent: $63K for contradictory advice
  • Our current TVL: $1.2M
  • Our current revenue: $18K/month

We spent 3.5 months of revenue trying to classify our token, and we’re still not certain.

Meanwhile, our competitor based in the Cayman Islands launched their yieldUSD product three months ago, hit $50M TVL, and spent exactly $0 on SEC classification analysis.

Should Yield-Bearing Stables Be Securities?

Let me be transparent: I actually think yield-bearing stablecoins should face regulatory scrutiny. If we’re promising yield from our management of assets, that’s fundamentally different from a pure stablecoin.

But the framework should explicitly say that. Give us a bright-line rule:

:white_check_mark: Stablecoin: Maintains $1 peg, no yield, no profit promise = not a security

:white_check_mark: Yield-Bearing Stable: Maintains $1 peg + generates yield = digital security, register accordingly

Instead, we got “may be securities, depending on facts.”

Question for the Community

For DeFi builders here: How are you thinking about yield-bearing stablecoin classification? Are you treating them as securities? Avoiding yield models entirely? Moving offshore?

For anyone with regulatory expertise: Is there existing securities law precedent for bank savings accounts or money market funds that could guide stablecoin classification? Or is this genuinely novel and we’re all guessing?

Steve is right—this framework creates clarity for well-funded players who can afford multiple legal opinions. For bootstrapped protocols trying to innovate, it’s a competitive disadvantage disguised as regulatory progress.

Coming at this from a trading and market structure perspective—this framework is going to create some fascinating (and frustrating) market dynamics.

The “16 Named Commodities” List Is Gold

Steve, Emma, Diana—I get your frustration about governance tokens and yield-bearing stablecoins. But can we appreciate for a moment that 16 major crypto assets are officially commodities?

Bitcoin, Ethereum, Solana, XRP, Cardano, Chainlink, Litecoin, Polygon, Avalanche, Cosmos, Algorand, Stellar, Tezos, Filecoin, and Polkadot.

This is massive for:

  • Institutional capital allocation - Pension funds can now invest without “is it a security?” paralysis
  • Derivatives markets - CME and other exchanges can list futures/options with regulatory clarity
  • Lending protocols - Borrowing/lending these assets isn’t offering unregistered securities

But the List Creates Weird Market Incentives

Tokens ON the list get institutional inflows. Tokens NOT on the list get treated as “probably securities, consult expensive lawyers.”

This creates a two-tier market:

  • Tier 1: 16 commodities - institutional grade, liquid, regulated
  • Tier 2: Everything else - retail playground, uncertain legal status, offshore exchanges

Guess which tier gets better liquidity, tighter spreads, and institutional capital? Guess which tier bleeds talent to Singapore?

The Arbitrage Opportunity (and Problem)

Here’s what’s already happening in markets:

US-based protocols:

  • Expensive legal compliance
  • Slow to ship new features
  • Conservative marketing (can’t say anything about value appreciation)
  • Higher costs passed to users

Offshore competitors:

  • Zero classification costs
  • Ship fast, break things, iterate
  • Aggressive marketing (promise the moon)
  • Lower fees, better UX

From a trader perspective, I can access both. But US users? They’re pushed toward offshore protocols via VPNs and non-KYC exchanges.

The framework didn’t eliminate regulatory arbitrage—it formalized it.

Diana’s Yield-Bearing Stablecoin Problem Is Real

Diana, your yUSDC example is interesting because there’s actual TradFi precedent here: money market funds.

Money market funds:

  • Maintain $1.00 NAV
  • Generate yield from underlying assets
  • ARE regulated as securities (Investment Company Act of 1940)

Based on that precedent, yield-bearing stablecoins probably ARE securities. The SEC guidance just didn’t explicitly say it.

But here’s the kicker: if yUSDC is a security, you need to register as an investment company. That’s not just filing paperwork—that’s ongoing compliance, audits, custody requirements, qualified custodians, the whole nine yards.

For a $1.2M TVL protocol? That’s economically impossible.

So what happens? You move offshore. And the US market loses another innovative DeFi protocol.

What I’m Watching

Short-term (3-6 months):

  • Capital flows to the 16 named commodities
  • Governance token projects either avoid US users or incorporate offshore
  • Yield-bearing stablecoin protocols migrate to Cayman/Switzerland
  • Traditional stablecoin dominance (USDC, USDT) increases

Medium-term (1-2 years):

  • Case law develops around edge cases (algorithmic stables, governance tokens)
  • Either the framework gets refined with clearer guidance, or offshore dominance becomes permanent
  • US crypto markets become commodities-only, everything else happens offshore

Wildcard:

  • If a major protocol gets enforcement action for misclassifying (thought they were “digital tool”, SEC says “digital security”), the entire market reprices uncertainty. Legal fees spike, offshore migration accelerates.

Steve’s Question: Should You Incorporate Offshore?

From a pure market perspective? Yes, if you’re building anything other than infrastructure for the 16 commodities.

The compliance cost differential is too large. Singapore offers:

  • Payment Services Act (clear framework for digital payment tokens)
  • 3-6 month approval timeline
  • $100K-250K total legal/compliance (vs $500K+ in US for anything complex)
  • Access to Asian market (bigger crypto adoption than US)

Austin is great for talent and culture. Singapore is better for shipping a token-based product in 2026.

I hate that this is the answer, but market structure doesn’t care about feelings.

Bottom Line

This framework solved the BTC/ETH/SOL debate. For everything else, it increased complexity without reducing cost.

If you’re building on the 16 named commodities (infrastructure, tooling, analytics), stay in the US.

If you’re issuing any token (governance, utility, yield-bearing), seriously consider offshore.

The regulatory clarity we got is real—but it’s clarity that small teams can’t afford to use.