Upcoming mainnet release

​

API changes

• Entry stop orders: a STOP_LOSS order on POST /v1/placeOrder can set reduceOnly: false to open a position in the trigger direction when it fires. TAKE_PROFIT orders and TP/SL legs in a batch still require reduceOnly: true. Available on testnet now (testnet changelog).
• USDG withdrawal cap: POST /v1/withdraw rejects a single USDG withdrawal above $1,000,000 with HTTP `400`. Exactly $1,000,000 is accepted. Spot-asset withdrawals are not affected. Available on testnet now (testnet changelog).
• Account aggregates can trail by up to about 15 seconds: net deposits and cumulative funding on GET /v1/account, GET /v1/positions and WebSocket account snapshots are served from a short-lived cache. Net deposits update on every transfer; cumulative funding can lag by one payment for about 15 seconds after each hourly funding payment. Available on testnet now (testnet changelog).
• liquidationFeePpm matches the fee charged: GET /v1/markets and the markets channel report the liquidation fee the engine actually charges. Values do not change. Available on testnet now (testnet changelog).

​

Fixes

• Cancelled orders no longer reappear as open: on October 30, some already-cancelled orders showed up again in GET /v1/openOrders and the orders snapshot after a deploy, and cancelling them returned ORDER_NOT_FOUND. They were never live on the book. Deploys and restarts can no longer bring cancelled orders back. Available on testnet now (testnet changelog).

​

Stability and performance

• Lower WebSocket order-ack tail latency: rate-limit checks on WebSocket orders and cancels have a firm timeout and a local cache, so a slow check no longer delays acks for other clients. Available on testnet now (testnet changelog).
• Faster order book fan-out: order book views are built with less CPU, lowering WebSocket fan-out latency. Message contents and order are unchanged. Available on testnet now (testnet changelog).