What changed Binance order execution today?

TLDR

Binance changed order execution today by updating tick-size rules on selected spot pairs (affecting the minimum price increments and order validation) and running a Spot system test for UTF?8 support. The tick-size update was announced with examples and API notes in a Binance post; existing orders keep their original ticks, while new orders must use the updated increments, and bots should be adjusted per the API exchangeInfo endpoint tick size update.

1. Tick sizes on pairs such as CGPT/USDT and INJ/BNB are being tightened, changing allowed price steps.
2. A Spot platform test of UTF?8 implementation is scheduled today, which may affect order messaging and encoding system test note.
3. Impact: orders using old increments may be rejected; update bots to new tick sizes and watch rounding/display differences.

Deep Dive

1. Tick-Size Update

Binance is tightening the minimum price increments (tick sizes) on select spot pairs, which directly affects how limit and stop orders are validated and matched.

• The notice lists examples (e.g., CGPT/USDT ticks changing from 0.0001 to 0.00001 and INJ/BNB from 0.00001 to 0.000001). Existing orders placed before the change continue matching at their original ticks; new orders must use the updated increments. API users should refresh exchangeInfo to avoid rejections per the notice above.
• Practical effects: narrower ticks increase the number of price levels, potentially altering order book depth, queue priority, and backtest assumptions. Wider ticks compress steps and can change fills if your strategies assume older increments.

2. Spot System UTF?8 Test

Binance scheduled a Spot system test today related to UTF?8 implementation, which can influence how order text, symbols, and messages are encoded and displayed on the platform and via API clients system test note.

• While not a matching?engine change, encoding updates can affect downstream systems (order acknowledgements, logs, parsers, and UI) and may surface as formatting changes in endpoints or client libraries.
• If you rely on strict text parsing or symbol handling, verify your integrations against todays test window to prevent silent parsing failures.

3. Operational Impact and Next Steps

The tick-size changes become effective by 18 Dec (UTC), but the operational impact on order execution is immediate once live.

1. Refresh API exchangeInfo, validate order builders against new tick sizes, and ensure rounding matches the venues rules (buy rounding down, sell rounding up where applicable per the notice above).
2. Re-run stop/limit parameter checks; smaller ticks may allow tighter stops or more granular profit steps, but they can also change queueing and fill behavior.
3. Watch for order rejections and update bot error handling to catch invalid tick responses cleanly.

Conclusion

Todays changes center on price?increment rules (tick sizes) and a Spot system UTF?8 test. Together, they affect how orders are validated, encoded, and displayed. Update trading bots and OMS settings to the new tick sizes, verify UTF?8 compatibility, and run small test orders to ensure clean execution once the changes are fully live.