Bitmart is winding Down: Spot Order Confirmation And Exit

The Wind-Down Replaced New Entries With Account Exit

The wind-down workflow is an account-exit sequence covering open-order cancellation, settled-balance review and withdrawal preparation for existing BitMart users.

Before the change, the first-position path began with an available quote balance, an eligible spot pair and a supported order mode. A trader selected BTC/USDT, chose buy or sell and entered quote notional or base size. Confirmation then moved through the order record into the spot asset ledger. During wind-down, the sequence starts later: cancel open orders, identify the final filled quantity, reconcile the balance and prepare the asset for its destination.

At 01:30 UTC on July 26, 2026, BitMart started gradually suspending deposits and new spot orders as its wind-down began.

Trading services were scheduled to end at 01:00 UTC on August 26, 2026, followed by platform cessation at 15:59 UTC on January 31, 2027. The recommended 05:00 UTC withdrawal cutoff on August 26 separated account review from blockchain processing. Those dates made position confirmation the first step of account exit.

An accepted order never proved an asset was ready to withdraw. A completed fill changed balances permanently; an unfilled order reserved funds until cancellation. The current sequence runs from open orders to history, then balances and withdrawal. It does not begin with a fresh trade ticket.

Pair Selection Set The Asset And Quote Direction

A spot pair was a 2-asset market whose base and quote currencies determined what each BitMart buy or sell instruction changed. In BTC/USDT, Bitcoin was the base asset and Tether’s USDT was the quote asset. A buy spent USDT to acquire BTC; a sell released BTC for USDT. That direction mattered because the selected exit asset had to be supported by the destination wallet and withdrawal network.

Order size and price precision came from symbol rules, not the coin’s smallest protocol unit alone. Bitcoin uses 8 decimal places and 1 BTC equals 100,000,000 satoshis, yet an exchange pair could impose a larger minimum or coarser step. The amount also had to sit in the available spot balance rather than an open order. Spot mode produced an asset ledger, whereas futures represented contract exposure requiring a different closeout path. That distinction prevented contract quantity from being mistaken for owned BTC.

Open Orders And Partial Fills Came Before Balance Confirmation

An open-order state was a reservation record showing whether BitMart had accepted, partly executed or completed a spot instruction. The former order model used 5 states: new, partially filled, filled, canceled and partially canceled. Only the filled quantity belonged in the position calculation.

New and partially filled were the 2 open states, so either could keep part of a balance unavailable. A partial fill split the instruction into an executed portion and a remainder. Cancelling the remainder stopped further matching but preserved the trade. A canceled state meant no remaining quantity would execute; a partially canceled state preserved what filled. During wind-down, those states prevented the original order size from being treated as final.

Balance confirmation followed cancellation because released funds and executed assets appeared as different ledger effects. The order record explained the difference. The next part of this is set out in Bitmart setup.

Market, Limit, Post-Only And IOC Entry Modes

BitMart’s spot order menu was an execution selector offering immediate matching, price control and maker-only or immediate-or-cancel behavior. It exposed 4 documented order types.

A market buy specified quote notional, while a market sell specified base size. Matching consumed the best order-book levels until the instruction finished or liquidity ran out. A limit order instead carried 2 required numeric inputs: size and price. It rested until compatible liquidity appeared, so its price defined the worst accepted price but not guaranteed execution. Several fills could contribute to one average price.

Post-only, documented as limit-maker, sought maker status. A buy at or above the lowest ask or a sell at or below the highest bid would cross the book, so the engine canceled or rejected it instead of taking liquidity. IOC meant immediate-or-cancel: the engine filled available quantity at once and canceled the remainder. Those mechanics made the order type part of position size, not merely an interface preference.

Fresh spot entry was no longer the active path during wind-down. These distinctions remain useful when interpreting historical orders and residual balances. A historical limit order may explain a partial position where a market ticket suggests a simpler all-at-once expectation.

How Did BitMart Confirm A Completed Spot Position?

A completed spot position was an asset-ledger change BitMart confirmed through the filled order record and the corresponding available balance. Three fields did the main reconciliation work: filled size, filled notional and average execution price. Filled size stated the acquired or sold base quantity. Filled notional showed the matched quote amount. Average price summarized multiple executions without replacing either total.

Order history supplied the order ID, side, symbol, state and update time; trade history split the order into executions. The spot balance showed the asset available after fills and cancellations. For BTC/USDT, BTC filled size matched the BTC balance movement and USDT filled notional matched the quote movement. Another open order could reserve either asset, so order state had to be reconciled before withdrawal capacity. Both records described the same event from different angles.

The chart price was only market context. Position confirmation came from account-specific execution records, which carried more authority than the ticket’s original requested amount.

Worked Balance Reconciliation From A Partial Fill

A partial-fill reconciliation was an arithmetic check separating executed quantity from the original requested size before cancellation or withdrawal. In this hypothetical example, every changing input is illustrative: limit size 0.020 BTC, limit price 30,000 USDT, filled size 0.012 BTC and filled notional 360 USDT. The remainder was 0.008 BTC. After cancellation, the confirmed position increase was 0.012 BTC and the recorded quote execution was 360 USDT, not the original 0.020 BTC and 600 USDT.

Order Identifiers, States And Query Windows

The spot order interface was a signed instruction system returning identifiers, execution fields and time-bounded query results for reconciliation.

A client-defined spot order ID accepted up to 32 case-sensitive alphanumeric characters in the documented submission interface. The engine returned its own order ID after successful submission. Besides the default none setting, self-transaction protection offered 3 cancel responses: cancel maker, cancel taker and cancel both. Those identifiers linked a user instruction to later state, fill and cancellation records.

Order queries used a default receive window of 5,000 milliseconds and allowed 60,000 milliseconds. A canceled, unfinished API transaction remained queryable within 20 minutes. Open-order requests returned at most 200 records and defaulted to 200; without a range, they covered the last 7 days. These windows mattered because a missing response could reflect query scope rather than a missing ledger event. A local record preserved context after the interface changed.

The account interface presented the same core relationship in simpler form: order ID, state, filled quantity and balance movement. Those fields were more reliable than recalling the button pressed.

The Current Exit And Withdrawal Sequence

The current BitMart exit is a withdrawal workflow built around settled spot balances, an exact network choice and destination confirmation. It starts only after all remaining spot orders are canceled and the final available asset amount appears in the main account.

From there, BitMart described 2 withdrawal routes: on-chain transfer to an external address and internal transfer to another BitMart account. The web flow used 4 main steps - choose the asset, select the crypto-network route, enter network and address and complete Google Authenticator plus email verification. The app guide used 6 screens. During wind-down, on-chain withdrawal created the durable exit; an internal transfer left the asset inside the closing platform.

Network selection bound the withdrawal to one ledger. USDT on Ethereum follows ERC-20, while USDT on TRON follows TRC-20; the token ticker did not make those routes interchangeable. EVM addresses also look similar across networks, yet Ethereum uses chain ID 1, BNB Smart Chain 56, Polygon PoS 137, Arbitrum One 42161, Optimism 10 and Base 8453. The destination wallet had to support the same chain chosen in the BitMart form, including any required memo or tag. Each network records a separate transaction and balance.

Address management recognized 3 categories: standard, universal and EVM. A verification flag used 2 states, unverified and verified, while bulk management accepted up to 20 addresses. API withdrawals required a verified address; the ordinary interface could pre-verify an address to avoid repeating that step. The withdrawal request then returned one withdrawal ID, which proved submission rather than blockchain settlement.

At a protocol level, BitMart recommended withdrawal before 05:00 UTC on August 26, 2026. A request could pass through account review, asset checks and a queue before broadcast. Withdrawal history supplied status; a blockchain transaction ID marked the on-chain stage. Bitcoin targeted one block about every 10 minutes and Ethereum used 12-second slots, but receiving wallets chose their confirmation threshold. Etherscan or another matching explorer provided a clearer settlement view than an exchange request marked pending.