Coinbase opened hybrid Mag7 and crypto-ETF futures market

Coinbase Derivatives opened its Mag7 + Crypto Equity Index futures market at 5:00 p.m. Central Time on September 21, 2025, the start of the exchange’s Monday session. The contract carried a September 22 trade date, an important calendar distinction: the market opened on Sunday evening in the United States even though Coinbase promoted the product as a September 22 launch.

The new contract, code MC, put seven large technology companies, Coinbase shares and two BlackRock spot-crypto exchange-traded funds into one regulated futures benchmark. Coinbase described it as the first U.S.-listed derivative combining traditional equities and cryptocurrency ETFs. The available contemporaneous records support the product’s structure and listing; they do not establish how much traded in its opening session or whether investors adopted it at scale.

A futures wrapper around ten securities

The MarketVector Mag7 Plus Crypto Index contained Apple, Microsoft, Alphabet, Amazon, Nvidia, Meta Platforms, Tesla and Coinbase, plus the iShares Bitcoin Trust and iShares Ethereum Trust. Each of the ten securities began with a 10% weight, with quarterly rebalancing. That meant the contract delivered indirect bitcoin and ether exposure through U.S.-listed ETF shares, not through spot cryptocurrency or direct token custody.

The contract was cash-settled in dollars. Its size was $1 multiplied by the index level, and the minimum increment was 0.25 index point, worth $0.25 per contract. Coinbase’s regulatory submission used an illustrative index level of 3,000.25 and an approximate $3,000 notional value; those were specification examples, not a verified September 21 transaction price.

Three nearest quarterly expirations were to be listed. Final settlement was tied to MarketVector’s index value at 3:00 p.m. Central Time on the third Thursday of the contract month. Nodal Clear was designated to clear the contracts. No shares of Apple, Coinbase, IBIT or any other component would be delivered at expiration.

Why the hybrid mattered

The listing compressed two themes that public markets had generally packaged separately: large-cap technology exposure and regulated proxies for bitcoin and ether. A single future could therefore express or hedge a combined view without assembling ten positions. That was a meaningful product-design step for a crypto-linked exchange moving beyond single-asset contracts.

The label “crypto equity index” also required care. Eight components were company shares, while IBIT and ETHA were exchange-traded trusts holding bitcoin and ether. The index did not include BTC or ETH themselves. At each quarterly reset, the two crypto ETFs together represented 20% of the benchmark, Coinbase stock another 10%, and the seven technology shares the remaining 70%. Those weights could drift between resets as component prices changed.

Coinbase’s filing argued that the ten-security, equal-weighted basket qualified as a broad-based security index under U.S. law and therefore fell under sole CFTC jurisdiction. On September 5, 2025, the CFTC’s public product database recorded the future as certified. Certification reflected Coinbase’s self-certification under CFTC Regulation 40.2(a); it was not a Commission finding that the contract would be liquid, profitable or suitable for any particular market participant.

What the event-day record cannot show

The launch expanded the set of regulated instruments connecting crypto exposure with conventional portfolios, but its immediate market impact remains unmeasured in the reviewed record. Coinburn found no authoritative event-day volume, open-interest, bid-ask or participant data for MC. The article therefore makes no claim about launch demand, price discovery or institutional uptake.

The defensible conclusion for September 21 is narrower: a CFTC-certified U.S. futures venue opened a hybrid equity-and-crypto-ETF contract during its Sunday evening session. Whether that structure became a durable market would require trading data and evidence from later dates, neither of which should be projected backward into the launch-day record.