SEC/CFTC Commodity Classification for 16 Cryptos—Interpretive Guidance Analysis

Big news dropped on March 17th—the SEC and CFTC finally published that joint 68-page release everyone’s been waiting for. They explicitly classified 16 major cryptocurrencies as digital commodities instead of securities.

The list includes all the heavy hitters: Bitcoin, Ethereum, Solana, XRP, plus Dogecoin, Cardano, Avalanche, Chainlink, Polkadot, Stellar, Hedera, Litecoin, Shiba Inu, Tezos, Bitcoin Cash, Aptos, and Algorand.

This is the first time we have coordinated guidance from both agencies actually naming specific assets and saying “these are commodities under CFTC jurisdiction, not securities under SEC jurisdiction.”

The Part Nobody Is Talking About

Here’s what caught my eye: This is an interpretive release, not a law.

The CLARITY Act still needs to pass through Congress to make this legally binding and permanent. And yeah, it passed the House back in July 2025 with a solid 294-134 vote, but it’s been sitting in the Senate ever since.

Even more interesting? Coinbase—literally the biggest US crypto exchange—pulled their support for the CLARITY Act in January 2026. Their CEO said it could “hamper innovation.” If the industry’s main player won’t back it, what are the chances it actually passes?

Why I’m Not Popping Champagne Yet

Look, I’m glad we have this guidance. It’s way better than the “regulate by lawsuit” approach we’ve been dealing with. But let’s be realistic about what this actually is:

Courts can ignore it. Federal judges aren’t bound by SEC/CFTC interpretations. They can rule however they want on securities law.

It doesn’t help existing cases. If you’re already in litigation, this guidance doesn’t retroactively save you.

Future administrations can reverse it. Remember when the SEC kept flip-flopping on whether ETH was a security? That could happen again with any of these 16 assets if we get a new SEC chair who disagrees.

The Bigger Picture

The March 11 MOU where the SEC and CFTC agreed to actually coordinate (via a “Joint Harmonization Initiative”) is probably more important long-term than the specific commodity list. At least they’re trying to work together instead of contradicting each other.

But the stablecoin yield fight shows how messy this still is. Banks don’t want stablecoins paying interest because it competes with deposits. Lawmakers say they reached “agreement in principle” but details are still being fought over.

My Take as a Developer

If you’re building right now, this guidance gives you something to work with. Document your compliance efforts. Engage with regulators proactively. Treat this as progress, not perfection.

But don’t bet your entire business model on interpretive guidance that could change. Build with flexibility. Have fallback plans.

The industry spent years screaming for regulatory clarity. We finally got explicit classifications for 16 major assets from both agencies. But it’s guidance dependent on Congress passing a bill that Coinbase won’t support, and it’s guidance that future administrations could reverse.

So did we get clarity, or did we just get another data point in ongoing uncertainty?

How are other builders thinking about this? Are you adjusting product roadmaps based on commodity status, or treating it as too uncertain to rely on?


Sources: SEC Official Release, CLARITY Act Status, Chapman Legal Analysis

As someone in the middle of fundraising right now, this announcement hit at exactly the right (or wrong?) time.

On one hand, I’m relieved. When we pitch investors, one of the first questions is always “regulatory risk.” Being able to point to explicit SEC/CFTC guidance saying the major tokens are commodities is huge. It’s way better than the “we think this probably isn’t a security based on the Howey test but who knows what the SEC will say” conversation we’ve been having for years.

But here’s what’s happening in actual investor meetings: They’re asking “What happens if this gets reversed in 2028?”

And honestly? I don’t have a great answer to that.

The fact that this is interpretive guidance and not law means investors see it as temporary. The CLARITY Act passing the House was encouraging, but it’s been stalled in the Senate for 8 months now. And when I mention that Coinbase—the biggest, most established US exchange—pulled support from the bill, investors get nervous.

One VC literally said to me: “If Coinbase won’t back the CLARITY Act because it might ‘hamper innovation,’ that tells me either the bill is bad or the industry can’t agree on what good regulation looks like. Either way, I’m not comfortable investing in something that depends on Congress passing a bill nobody seems to want.”

The Business Reality

From a practical standpoint, I’m treating this guidance as progress but not certainty:

  1. We’re documenting everything. Every compliance decision, every design choice, every legal opinion. If regulatory interpretation changes, we can show we acted in good faith based on current guidance.

  2. We’re building with flexibility. Not betting the entire business model on commodity status. Have fallback plans if classifications change.

  3. We’re engaging proactively. Meeting with regulatory consultants, participating in industry groups, submitting comments on proposed rules.

But the uncertainty still affects strategic decisions. Do we launch a token now or wait for CLARITY Act passage? Do we pursue US investors or focus on international markets? Do we allocate resources to compliance infrastructure that might change in 2 years?

@regulatory_rachel - From your experience, what’s your advice for startups trying to build compliant businesses when the regulatory foundation is interpretive guidance rather than law? Are there safe harbor provisions or practical steps that protect us even if interpretations change?

And has there been any signal from the Senate about when they might actually vote on the CLARITY Act?

I had such mixed feelings reading this announcement. Relief, frustration, cautious optimism, lingering worry—all at once.

The relief part: ETH and SOL explicitly classified as commodities. After years of “is Ethereum a security?” FUD, having both agencies say definitively “these are commodities” feels like we can finally breathe.

The frustration part: This could have happened years ago. The regulatory uncertainty genuinely slowed down development. I can think of specific features our team avoided building because lawyers said “this might trigger securities treatment.” We designed around regulatory fear instead of user needs.

How Uncertainty Shaped Development

Here’s a concrete example: We wanted to build a yield optimization feature that would automatically rebalance user positions across multiple protocols. Technical implementation? Easy. But legal said “if the protocol is actively managing user funds, that creates securities law risk.”

So we didn’t build it. Users missed out on potential value. Our protocol had less utility. All because of regulatory uncertainty about whether DeFi protocols offering managed strategies would be classified as securities.

Now that we have commodity classification, could we revisit features like that? Technically yes. But what if this guidance changes in 2 years? Do we build assuming commodity status, then have to unwind everything if a new SEC chair says “actually, these are securities after all”?

The Developer Dilemma

@startup_steve makes a great point about investor nervousness. As developers, we face the same dilemma:

  • Do we design protocols assuming commodity status and take full advantage of that flexibility?
  • Or do we continue designing conservatively because this is guidance, not law, and could be reversed?

The interpretive release is better than nothing. The March 11 MOU establishing the Joint Harmonization Initiative is actually really encouraging—at least the agencies are trying to coordinate instead of giving contradictory guidance.

But I keep thinking: what happens to all the protocols, DeFi apps, and composable systems we build assuming BTC/ETH/SOL are commodities… if that interpretation changes?

What I’m Watching

The fact that Coinbase withdrew support for the CLARITY Act worries me more than I want to admit. If the most established, most compliant US exchange thinks the legislation “hampers innovation,” what does that mean for the rest of us trying to build innovative protocols?

I guess my question for the more experienced folks here: How much should we trust and build on top of interpretive guidance versus waiting for actual legislation? Is it better to move fast and potentially need to adapt later, or be conservative and possibly miss market opportunities?

Also curious about DeFi-specific implications. The guidance mentions “digital tools” and “stablecoins” as separate categories. Does anyone know how that affects lending protocols, AMMs, or yield aggregators?

@ethereum_emma Your point about Coinbase pulling support really crystallizes the problem for me.

Here’s what bugs me: The crypto industry has been screaming for regulatory clarity for years. “Give us clear rules and we’ll comply!” Right?

Now we have the SEC and CFTC publishing 68 pages of coordinated guidance, explicitly classifying 16 major assets, establishing a taxonomy, trying to give us that clarity we demanded…

And the industry’s largest, most established company says “no thanks, this might hamper innovation.”

The Coordination Problem

This makes me wonder if the industry actually knows what it wants.

Coinbase’s specific objections were:

  • Restrictions on tokenized equities
  • DeFi provisions they didn’t like
  • Concerns about CFTC vs SEC authority balance
  • The stablecoin yield ban (which represented ~20% of their Q3 2025 revenue)

So they’re not saying “we want no regulation.” They’re saying “we want regulation, but not this regulation.”

But if the biggest player can’t get behind comprehensive legislation because specific provisions affect their business model, how does the industry ever reach consensus on what “good regulation” looks like?

Perfect Is the Enemy of Good?

The stablecoin yield fight is a perfect example. Banks don’t want competition for deposits. Stablecoin issuers and exchanges want to offer yields. Both sides have legitimate business interests. Lawmakers are trying to find middle ground.

But while they negotiate details, the CLARITY Act sits in the Senate. And builders like Emma and me are stuck wondering whether to design for commodity status or play it safe.

Maybe the question isn’t “did we get clarity or uncertainty” but rather: Is the industry capable of agreeing on regulatory framework, or will perfect be the enemy of good?

Because from where I’m sitting, interpretive guidance that can be reversed is better than nothing. But if Coinbase won’t support legislation to lock it in… what’s the path forward?

@regulatory_rachel - Do you see a scenario where the industry reaches consensus on CLARITY Act provisions? Or are we stuck with interpretive guidance indefinitely because stakeholders can’t agree on details?

Great questions from both of you. Let me address the concerns directly with some legal and practical perspective.

Why Interpretive Guidance Still Matters

@startup_steve asks about building on guidance that could change. Here’s my take: Document everything, comply proactively, and understand that regulatory certainty is always iterative—not a single announcement.

Even if interpretive guidance could theoretically be reversed, there’s significant value in compliance efforts made in good faith:

  1. Safe harbor doctrine. Courts and regulators generally give credit for good-faith compliance with existing guidance, even if that guidance later changes.

  2. Enforcement discretion. The SEC and CFTC are far less likely to pursue enforcement against companies that demonstrably tried to comply with published guidance.

  3. Investor protection. Showing documented compliance processes protects you legally even if rules change.

The CLARITY Act Reality Check

Yes, Coinbase withdrew support. But let’s be precise about what that means:

Brian Armstrong’s objections were specific provisions, not the concept of regulatory framework. They opposed:

  • Tokenized equities restrictions
  • Certain DeFi definitions
  • SEC/CFTC authority balance
  • Stablecoin yield provisions (affecting ~20% of their revenue)

This isn’t “Coinbase opposes regulation.” It’s “Coinbase opposes specific regulations affecting their business model.”

Honestly? That’s normal legislative negotiation. Banking regulations, securities laws, commodity futures regulations—all of them went through years of stakeholder negotiation before passage.

What the March 11 MOU Actually Means

@ethereum_emma, the Joint Harmonization Initiative is more important than the commodity list.

The March 11 Memorandum of Understanding commits the SEC and CFTC to:

  • Coordinated policymaking
  • Harmonized examination procedures
  • Joint enforcement coordination
  • Regular communication and consultation

This is structural coordination. Even if specific guidance changes, having agencies work together rather than contradict each other is foundational improvement.

Practical Advice for Builders

For @startup_steve’s fundraising:

Tell investors: “We’re complying with current SEC/CFTC guidance, documenting all compliance decisions, and engaging with regulatory counsel proactively. If guidance changes, we have flexibility built into our architecture and a track record of good-faith compliance.”

That’s a better pitch than “we’re ignoring regulations” or “we’re waiting for perfect clarity.”

For @ethereum_emma’s development:

Build features assuming commodity status, but with modularity. Design systems where you can switch compliance modes if classifications change. Document why each design decision complies with current guidance.

The yield optimization feature you mentioned? Build it. Document that you designed it based on commodity classification guidance. If guidance changes, you have architecture to adapt and documentation showing good faith.

The Senate Timeline Question

Realistically? The CLARITY Act faces several hurdles:

  1. Stablecoin yield compromise (lawmakers claim “agreement in principle” but details aren’t finalized)
  2. DeFi definitions (still contentious)
  3. SEC/CFTC jurisdiction boundaries (both agencies want authority)

Could it pass in 2026? Yes. Will it? Depends on whether stakeholders accept “good enough” rather than holding out for perfect.

Steve’s Question About Industry Consensus

You asked whether the industry can agree on regulatory framework. Honest answer: Probably not on every detail.

But here’s the thing—that’s okay. Banking regulations didn’t achieve perfect industry consensus either. Securities laws took decades to evolve. Commodity futures regulations went through multiple revisions.

Regulatory frameworks are iterative. The fact that we have SEC-CFTC interpretive guidance establishing commodity classifications is step forward, even if it’s not final legislation.

My Professional Recommendation

Don’t let perfect be the enemy of good.

Comply with current guidance. Document your decisions. Engage with regulators proactively. Build flexible architectures.

And yes, have contingency plans for if interpretations change. But don’t freeze development waiting for Congress to pass perfect legislation. That could take years—and even then, it will get amended.

The interpretive release is better than the “regulation by enforcement” approach we endured. The Joint Harmonization Initiative creates structural coordination. These are real improvements, even if imperfect.

Build. Comply. Document. Adapt as needed. That’s how you survive regulatory evolution.


Disclosure: This is general analysis, not legal advice for specific situations. Consult qualified regulatory counsel for your particular circumstances.