What happened
On 27 August 2026 the Federal Register carried three notices, one for each of the MIAX options exchanges, of a rule change that was already in force. Release No. 34-106178 (File No. SR-MIAX-2026-36) was filed on 13 August 2026 and became operative the same day, after the Commission waived the delay such filings normally serve. It rewrites which securities may list short-dated options expiring on a Monday or a Wednesday, and it records, in a paragraph about housekeeping, that the iShares Bitcoin Trust ETF (IBIT) came off that list at the start of the third quarter of 2026.
What it changes
The Short Term Option Series Program lets an exchange list options expiring outside the standard monthly calendar. A subset of names, "Qualifying Securities", may carry two Monday and two Wednesday expirations beyond the current week. Qualifying is not a judgement. It is a quarterly arithmetic test on four things: for a fund, assets under management above $50 billion by net asset value on the last day of the prior quarter, monthly options volume above 10 million sides in the last month of that quarter as measured by the Options Clearing Corporation, a position limit of at least 250,000 contracts, and participation in the Penny Interval Program. The exchange publishes the new list by the close of the first trading day of each quarter.
IBIT was in the founding group when MIAX began listing Qualifying Securities on 26 January 2026, alongside Tesla, Nvidia, Apple, Amazon, Meta, Broadcom, Alphabet and Microsoft. On the required review it came off, and Advanced Micro Devices, Intel, Micron, the VanEck Semiconductor ETF and the Financial Select Sector SPDR Fund went on. The exchange's list for the third quarter, published on 1 July 2026, has thirteen names on it and IBIT is not one of them.
The test never looks at what a fund holds. It looks at how big the fund is and how much its options trade, and it is re-run from scratch every quarter. The new filing adds a second, lower rung: a Tier 2 Qualifying Security is an exchange-traded fund with assets above $25 billion and monthly options volume above 5 million sides, half of each of the current thresholds, and it gets the Monday and Wednesday expirations but not the Tuesday and Thursday ones the filing adds for the tier above it.
What it does not change
It does not put IBIT back. Eligibility for the fourth quarter is computed from the last trading day of September 2026 and published on the first trading day of October, on whichever data the fund and its options produce. The filings say the fund was removed; none of the three says which of the two thresholds it missed, and neither should anyone reading them.
Nothing about the fund itself moved. Same shares, same trust, same bitcoin. An option on IBIT is a claim on the shares, and the shares are a claim on the coins, so the expiry calendar sits two removes from anything in custody. A holder of the fund who never traded an option would not have noticed the change, and a holder of bitcoin certainly would not.
Nor is this a market-wide rule. It binds three exchanges in one group. MIAX asked for the immediate waiver so that it could, in its own words, "compete with at least one other exchange that has approval to list and trade the same option series", which means the expirations existed elsewhere while MIAX could not offer them. And immediately effective is not the same as approved: the Commission may summarily suspend a filing of this kind within 60 days of the date it was filed, and comments on this one are open until 17 September 2026.
Context
Since the spot ETF approvals the recurring pattern is that most of the news generated by these funds is about the wrapper rather than about bitcoin. The ARK 21Shares fund changing the index it prices itself by was one instance. This is another: a fund's presence on a list of names eligible for a particular expiry calendar, decided by two numbers that have nothing to do with what is in the trust.
That is worth keeping straight rather than dismissing. The wrapper is real infrastructure and its rules have consequences for the people who use it. It is simply a different object from the asset inside it, subject to a different rulebook, with its own quarterly tests, its own comment periods, and its own reasons for a change that have no counterpart in a block or a key.
