BitMEX Shutting Down: Close-Only Mode Explained

The mechanics are simple but easy to misread. Since 04:00 UTC today, BitMEX's risk limits only let you trade in the direction of reducing exposure, closing longs, closing shorts, or shrinking size. New positions are blocked outright, and existing ones can only get smaller from here. That's the close-only phase, and it runs for 28 days, until the exchange's full closure at 04:00 UTC on September 23. During that window, BitMEX has explicitly reserved the right to force-close existing positions at its own discretion, not just at the final deadline, so there is no guarantee your position survives untouched even before September 23 arrives. Platform open interest has already been drifting down for weeks — BitMEX's XBTUSD perpetual notional was around $39.45 million as of August 10, per Cryptoslate — and it's continued shrinking as traders comply rather than wait it out.

At 04:00 UTC on September 23, anything still open gets force-closed automatically, settled against BitMEX's own index or settlement price. There's no negotiation and, per BitMEX's terms, no liability on the exchange's part for losses that result from that settlement. That matters because a forced settlement during what could be a volatile final 24 to 48 hours, with a shrinking pool of liquidity behind it, is not the same as choosing your own exit price on a normal trading day with normal depth. The practical takeaway is blunt: if you have an open position, closing it yourself now, on your own terms and at a price you can see, is strictly better than letting BitMEX's wind-down engine do it for you later. Waiting doesn't preserve optionality here — it just hands execution control to the exchange at the exact moment liquidity is thinnest.

Closing a position is only half the job. Even after you're flat, leaving funds sitting in a BitMEX wallet past closure carries its own cost. KYC-verified users who still have a balance after September 23 start accruing a custody fee — the greater of $50 or 1% of the balance annually, charged monthly — with no stated cap other than the balance eventually hitting zero over time. It's easy to close a trade, feel done, and forget the money is still parked on an exchange that's actively shutting down around it. The fee only kicks in post-closure, so there's no cost to withdrawing early, and every day spent deciding is a day the fee clock could be running once the deadline passes. Treat closing positions and withdrawing funds as two separate checklist items, not one, because clearing the first without the second still leaves money exposed.

There's a narrow edge case where "just close it yourself" doesn't cleanly apply: a handful of dated futures contracts — XBTU26, XBTZ26, XBTH27, and ETHUSDU26 — have expiry dates that fall after BitMEX's own closure date. Combined, these represent roughly 66 BTC of exposure, about 0.06% of the platform's total open value, so this affects a genuinely small slice of traders. BitMEX has said it will early-settle these contracts on notice rather than let them run past the exchange's own shutdown date. If you're holding one of these specific instruments, expect an early settlement notice rather than a normal expiry, and don't assume the standard close-and-withdraw advice fully covers your position without checking the contract-specific terms BitMEX has published.

There's no bull case in the usual sense here — no scenario where waiting pays off. The best outcome available is simply avoiding unnecessary friction: close remaining positions at a price you choose rather than one BitMEX chooses for you, then withdraw the resulting balance before September 23 rather than after. The failure mode is equally straightforward: a position that rides into the forced-closure window and gets settled at an unfavorable moment, stacked on top of a balance that sits untouched afterward and starts losing value to a monthly fee with no clear ceiling. Both risks are entirely avoidable with the same two actions: close, then withdraw, and do both well before the clock runs out rather than scrambling after.