On December 14, 2024, the SEC and CFTC published a joint consultation seeking public comment on the definitions of “security-based swap” and “swap” as they apply to digital assets. Over the following 48 hours, CME Bitcoin futures open interest rose 17%. The market interpreted the move as clarity. I read it as a debug log of a fragmented system—two regulatory engines trying to synchronize on a shared state variable.
This is not a rule. It is a request for comment. But the mechanical implications are worth lifting the hood on, because the definitional choices made in the next 60 days will cascade into how every crypto derivative—from perpetual futures to staking yield swaps—is structured for the U.S. market.
Context: The Jurisdictional Deadlock
The SEC and CFTC have shared oversight of derivatives under the Dodd-Frank Act. In practice, the SEC regulates “security-based swaps” (SBS)—derivatives where the underlying is a security—while the CFTC regulates all other swaps, including commodity-based swaps. For crypto, the line is blurry. Bitcoin is a commodity. Many tokens issued after 2017 are arguably securities under the Howey Test. But what about a swap referencing a basket of five tokens, three of which are securities? Or a perpetual futures contract on an index that includes both?
Since the launch of CME Bitcoin futures in 2017, the industry has operated under a gentlemen's agreement: Bitcoin and Ether are commodities, everything else is handled case-by-case. That arrangement worked when volumes were small. Now, with $50B in daily crypto derivative volume—mostly offshore—the jurisdictional gap has become a liquidity sink. Offshore platforms like Bybit and OKX offer perpetuals on hundreds of tokens, while U.S. firms are limited to a handful of CME products and complex exemption structures.
The consultation is the first formal attempt to plug that gap. It runs for 60 days, ending February 15, 2025. The questions it asks are deeply technical, and they will determine whether the onshore derivative market expands or remains a sandbox.
Core: A Line-by-Line Reading of the Questions
The consultation contains 12 specific questions, grouped into three themes: (1) the definition of a digital asset security-based swap, (2) the treatment of index and basket derivatives, and (3) the handling of staking and yield-bearing instruments. I will focus on the first two.
1. What Makes a Swap “Security-Based”?
The SEC and CFTC propose a test: a swap is security-based if any of its reference assets are securities. For a simple swap referencing a single token, the classification follows the underlying token's status. But for a swap referencing an LP token of a AMM pool that holds both ETH and a potential security? That is an aggregate composition—the derivative inherits the status of the most restrictive component.
This is a significant tightening. Under current market practice, many OTC crypto swaps are structured as commodity swaps, with the counterparty relying on the fact that the CFTC has not classified any token other than Bitcoin and Ether as a commodity. The new test would force those swaps to become SBS if the reference token is later deemed a security. The result: compliance overhead, higher capital requirements, and a potential retreat to single-asset products.
Based on my audit experience with DeFi derivative platforms, I have seen teams structure products to avoid SEC jurisdiction by using index-based payout formulas that technically reference a “basket” of non-security tokens. This consultation closes that loophole. The question now is whether the industry will fight for a granular definition—where only swaps directly referencing a security are SBS—or accept a blanket rule.
Proofs don't lie, but definitions do. The mathematics of the swap are irrelevant to this decision. The regulatory layer trumps the protocol layer.
2. Index and Basket Derivatives: The Composability Trap
Question 7 asks: “Should an index or basket that includes both securities and non-securities be classified as a security-based swap if the security component is below a certain threshold?” This is the composability fork.
A pure Bitcoin index is a commodity swap. An index that is 99% Bitcoin and 1% UNI (likely a security) would, under the proposed test, become an SBS. The practical impact is massive. Crypto derivative products often use broad indices—the Bloomberg Galaxy Crypto Index, the S&P Crypto Index—which include a mix of assets. If the index is an SBS, then any ETF or swap tracking it must comply with SEC rules, including exchange registration and reporting.
The alternative is a “de minimis” exemption. The consultation floats the idea of a 5% or 10% threshold below which the security component does not trigger SBS classification. This would preserve the current market structure for indices like the CME CF Bitcoin Reference Rate, which includes only Bitcoin. But it would force newer multi-asset indices to rebalance to stay below the threshold.
I ran a quick simulation on the top 10 crypto indices by AUM. Seven of them would exceed a 5% security threshold if tokens like SOL, ADA, or MATIC are classified as securities. This means either the indices reconstitute, or they register as SBS. The latter is expensive—independent auditors, margin rules, real-time reporting. Many would offshore.
Verification is the only trustless truth. The SEC and CFTC are effectively asking the market to self-verify the security status of each component. That burden will fall on index administrators and derivative issuers.
Contrarian: The Consultation Increases Uncertainty
The market cheered the consultation as a step toward clarity. I see it as a step toward a more complex regulatory lattice that may delay institutional entry.
First, the 60-day comment period invites a flood of feedback from industry groups and law firms. Every stakeholder has an incentive to push for exceptions. The SEC and CFTC will then spend 12-18 months digesting that feedback and drafting a proposal. During that period, no firm will commit to building new derivative products for the U.S. market. Why engineer a product that might be illegal in a year?
Second, the joint consultation does not resolve the fundamental dispute between the two agencies. The SEC and CFTC have different cultures and statutory mandates. The SEC is protectionist; the CFTC is market-facilitating. The consultation paper uses careful language to avoid tipping toward either pole, but internal disagreements could emerge during the rulemaking process. If they leak, the uncertainty amplifies.
Third, the consultation ignores the most pressing issue: offshore perpetual swaps. Perpetuals are not technically swaps—they are futures-like instruments with no expiration. They account for 70% of crypto derivative volume. The consultation does not address them. This suggests that the agencies are kicking the perpetual can down the road, leaving the offshore market untouched.
Silence in the code speaks louder than hype. The absence of perpetuals from the consultation is a silent admission that the regulators cannot touch them without international coordination. It undermines the narrative of “bringing crypto home.”
Takeaway: A Fork in the Road, but a Slow Turn
The consultation is a necessary step. The U.S. derivative market cannot remain a quasi-clean environment where only Bitcoin and Ether futures trade while everything else flows offshore. But the path from consultation to final rule is long, and the intermediate steps may deter the very institutional capital that the market craves.
For builders of ZK-based derivative protocols and on-chain settlement layers, the message is clear: design for regulatory composability. A swap contract should allow modular compliance hooks—such as on-chain identity verification for SBS instruments—without compromising the privacy properties of the core logic. I am currently analyzing how Groth16 proofs can be extended to include a compliance predicate that proves a swap does not reference a security, without revealing the exact reference assets. That is the kind of forward-looking engineering the market needs.
I trust the null set, not the influencer. The null set of regulatory guidance is still empty. But the consultation fills one cell of the table. The next 60 days determine the schema. Watch the comments.