SEC Opens Comment Period On Cboe 3x Bitcoin And Ethereum ETF Proposal

The SEC has opened a public comment period on Cboe BZX Exchange’s proposal to list six daily 3x leveraged Bitcoin and Ethereum futures ETFs.

The proposal, filed under SR-CboeBZX-2026-065, would cover commodity-pool products sponsored by Volatility Shares. The funds would seek three times the daily performance of front-month and next-month CME Bitcoin and Ethereum futures contracts, using daily reset mechanics.

That is a very different product from a spot ETF.

A 3x leveraged futures ETF is built for short-term tactical exposure. It is not a simple buy-and-hold wrapper for Bitcoin or Ethereum, and its daily reset structure can create performance drift over time.

The SEC’s move opens the proposal for public comments. It does not mean the products have been approved.

• The SEC opened comments on Cboe’s proposal for 3x leveraged BTC and ETH futures ETFs.
• The proposed products would be sponsored by Volatility Shares.
• The filing is under review and has not been approved.

Leveraged ETFs are popular because they give traders amplified exposure without directly using margin or futures accounts.

In crypto, that can be especially attractive because Bitcoin and Ethereum already move sharply. A 3x daily product would magnify those moves, creating potential for larger gains and larger losses in a traditional brokerage format.

That is exactly why regulators pay attention.

Leveraged products can be misunderstood by retail investors. They are designed to track daily performance, not long-term cumulative returns. Over multiple sessions, compounding and volatility can cause results to diverge from what investors might expect.

That risk becomes more important when the underlying asset is already volatile.

The proposal concerns futures-based products, not spot Bitcoin or spot Ethereum ETFs.

That distinction matters because the funds would use CME futures exposure rather than directly holding BTC or ETH. Futures-based exposure can behave differently from spot assets because of roll costs, margin, contract structure, and futures-market dynamics.

Investors may see “Bitcoin ETF” or “Ethereum ETF” and assume direct asset exposure.

That would be inaccurate.

These would be leveraged futures products tied to daily movements in futures contracts.

A public comment period gives market participants, investors, issuers, competitors, and other stakeholders a chance to respond to the SEC.

Comments may address investor protection, market manipulation, disclosure, suitability, volatility, liquidity, and exchange-listing standards.

The SEC can approve, reject, delay, or request changes.

So the current development is procedural but important. It shows the proposal is formally in the review pipeline, but it does not indicate the regulator has accepted the structure.

The proposal also shows how quickly the crypto ETF market is moving beyond plain spot products.

Bitcoin spot ETFs opened the door. Ethereum followed. Now issuers are testing leveraged, inverse, staked, altcoin, and multi-asset structures.

That expansion is natural in traditional ETF markets.

Once a base asset category becomes accepted, issuers compete by offering more specialized exposures. Crypto is now entering that phase, and regulators are being asked to decide how much complexity is appropriate.

If products like these eventually launch, they will not be suitable for every investor.

Daily 3x leveraged funds are typically tools for active traders. Holding them over longer periods can produce unexpected results because the fund resets exposure each day.

For Bitcoin and Ethereum, that risk may be magnified by extreme volatility.

The SEC’s review will likely center on whether disclosures, exchange rules, and product design are sufficient to protect investors.

For now, Cboe’s proposal is another sign that crypto ETF experimentation is accelerating. Approval, however, is still an open question.

This article is based on the SEC’s self-regulatory organization filing notice for Cboe BZX Exchange.

This article was written by the News Desk and edited by Samuel Rae.

This report is based on information released in disclosures at primary source documentation.