Binance announced changes to order quantity increments across several spot trading pairs on November 12, setting a November 19 implementation deadline that may require adjustments to automated order calculations.
The exchange’s official notice says the changes will be completed by 07:00 UTC, or noon Pakistan time. The update concerns step size, the interval by which an order’s asset quantity can change.
ETH and several Bitcoin pairs face larger increments
For ETH market price and chart/BTC market price and chart, the announced step size moves from 0.0001 ETH to 0.001 ETH. ADA market price and chart/BTC moves from 0.1 ADA to 1 ADA, while LINK market price and chart/BTC rises from 0.01 LINK to 0.1 LINK.
Other examples include DOT/BTC and FIL/BTC, each moving from 0.01 to 1 unit of the base asset. LUNC/USDT changes from 0.01 LUNC to 1 LUNC. These are order quantity increments, rather than price forecasts or a change in the assets’ circulating supplies.
A larger increment means less granular sizing for the affected order quantity. The financial importance depends on the unit price and the size of the intended trade; a tenfold increase in step size is not a tenfold increase in the amount a customer must invest.
Quantity filters and price filters impose separate constraints
Binance’s spot API filter documentation distinguishes the LOT_SIZE rules governing quantity from PRICE_FILTER rules governing price. Step size belongs to the former, while price tick size belongs to the latter.
The documentation also defines minimum notional rules, which concern the value of an order. A quantity meeting the permitted increment can still fail a separate minimum-value requirement. Checking decimal precision alone is therefore insufficient when validating an automated order.
Consider an illustrative order for 0.0015 ETH. That quantity fits an increment of 0.0001 ETH, but it is not a whole multiple of 0.001 ETH. An application calculating that quantity would need to validate the result against the rules in effect when the order is submitted.
Automated trading systems need current symbol rule checks
The operational question is whether a trading system obtains current filters or relies on quantities hard-coded under older settings. A rejected order can leave a strategy without the exposure its software expected, even though no trade has taken place.
Changing a quantity to satisfy an increment also changes the intended position size. The software must account for that adjustment rather than assume that formatting an extra decimal place solves a quantity-rule mismatch.
BlockBriefing’s guide to exchange API key security addresses account permissions and credentials, a separate concern from order validation. Its explanation of futures open interest also distinguishes derivatives positioning from activity in the spot market covered by this notice.
AVAX/BTC’s quantity increment rises from 0.01 AVAX to 0.1 AVAX. BCH/BTC moves from 0.001 BCH to 0.01 BCH, while ARB/BTC rises from 0.1 ARB to 1 ARB. Each pair therefore requires its own rule check.
Today’s announcement sets a future trading-parameter change. It does not establish that spreads have already narrowed or that market liquidity has improved. Those outcomes would require evidence from trading after implementation, rather than being inferred from the exchange’s stated objective.
