Binance Demo Trading launch log, 27–29 September 2026
First three days on Binance Demo Trading: stop placement, order acknowledgements, restart warnings, suspended assets and exit execution, with the change made for each.
Between 27 and 29 September the book moved from simulation to Binance Demo Trading, which uses the production matching engine, order API and error codes with simulated capital. Five exchange behaviours that the backtest does not model appeared in that period; each is listed below with the change made.
1. Stop orders require an open position
The self-test placed a stop order on a flat account, and Binance rejected it with -4509: Time in Force (TIF) GTE can only be used with open positions. Trading was unaffected, since stops are only placed against open positions; the fault was in the test. The self-test now opens a minimum-size position, attaches the stop, confirms it is resting on the exchange and closes the position.
2. Market orders acknowledged as unfilled
Binance's default acknowledgement for a market order reports zero quantity filled even when the order has filled in full, so trade reports understated fills. All orders now request the full result response.
3. False warnings on restart
On start-up the bot re-sent cross-margin and 5× leverage settings that were already in place. Binance rejects settings changes while stop orders are open, so each restart logged three false warnings. The bot now reads the current settings first and changes, or flags, only those that differ.
4. Suspended assets misread as closed positions
Reconciliation, which detects positions closed on the exchange by a stop, skipped assets that the exchange had suspended. A position in a suspended asset would therefore have been reported as closed while still open. Found in testing and fixed before it occurred on the account.
5. Maker-first exits
Maker-first execution performed as intended on entries. On exits it cost 9–22 bps each, against a fee saving of about 2 bps. Exits now cross the spread; the measurement is in Note 07.
Status
No capital was at risk; the account trades simulated capital. The self-test now exercises every exchange call the bot depends on, and every fill is logged with its slippage, so a further execution discrepancy should show up in the weekly report before it reaches a copier.