Copy page

Changelog

Update Preview

ANTHROPICUSDT Renamed to ANTUSDT

Effective date: TBD, subject to further announcement

Starting from the effective date, the following USDT-M Futures trading pair under both the V2 Classic Account and the V3 Unified Account will be renamed:

Before	After
ANTHROPICUSDT	ANTUSDT

What stays the same:

The following remain unchanged after the rename. There is no need to cancel orders, close positions or place orders again:

• Existing positions remain valid
• Existing open orders, TP/SL orders and strategy orders remain valid
• Trades, fills, positions and history records are not affected

What changes:

1. After the rename, API request parameters will accept both ANTHROPICUSDT and ANTUSDT, so you can keep using the old name or switch to the new one. However, the symbol field in all REST responses and WebSocket pushes will be returned as ANTUSDT.

Scenario	Request symbol	Response symbol
Before the rename	ANTHROPICUSDT	ANTHROPICUSDT
After the rename, using the old name	ANTHROPICUSDT	ANTUSDT
After the rename, using the new name	ANTUSDT	ANTUSDT

2. Public WebSocket connections subscribed with ANTHROPICUSDT will receive a push message notifying you of the rename. Please re-subscribe to this trading pair after receiving the message.

Candlestick and Public Trades Channels: Snapshot Push Removed

Effective date: demo trading on November 4, 2026; live trading expected on November 17, 2026

Interface:

• WebSocket candlestick channel (kline)
• WebSocket public trades channel (publicTrade)

Changes:

• After a successful subscription, these channels will no longer push snapshot data (action=snapshot); only real-time incremental data (action=update) will be pushed.
• To obtain historical candlestick or trade data, please use the corresponding REST API.

books50 Depth Channel: Incremental Push

Live date: December 1, 2026

Interface:

• WebSocket books50 depth channel (JSON)
• WebSocket SBE Depth50 channel (books50, templateId=1001)

Changes:

• The books50 channel will change from full snapshot on every push to incremental push: the first push after subscription is a full snapshot, and all subsequent pushes are incremental updates. This applies to both the JSON text-frame channel and the SBE binary channel.
• The pseq push parameter will also have a value for the books50 channel (previously only for the books channel), and can be used to determine whether there has been packet loss.
• On the SBE side, the schema version will be raised to 5, and the Depth50 message (templateId=1001) will carry two additional fields: depthAction (0 = snapshot, 1 = update) to distinguish the two frame types explicitly, and pseq for packet-loss detection.
• Currently effective in demo trading.