# November 2026

## [November 11, 2026] Preview: ANTHROPICUSDT Renamed to ANTUSDT

- Effective date: November 17, 2026, 17:30 (UTC+8)

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.

:::warning{title="Note"}
We strongly recommend switching the relevant parameters to `ANTUSDT` as soon as possible after the rename takes effect.
:::

## [November 3, 2026] Preview: V2 Classic Account and V3 Unified Account Candlestick and Trade Channels: Snapshot Push Removed

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

Interface:
- WebSocket Spot / Futures candlestick channels (`candle1m`, `candle5m`, `candle1H`, etc.)
- WebSocket Spot / Futures trade channels (`trade`)

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.

## [November 2, 2026] FastAPI Signature Algorithm Upgrade

- Release date: November 3, 2026

The FastAPI request signature algorithm is being upgraded from MD5withRSA to SHA256withRSA. You only need to change the hash algorithm from MD5 to SHA-256 in both your request-signing code and your callback signature verification code. For example, in Java, replace Signature.getInstance("MD5withRSA") with Signature.getInstance("SHA256withRSA"); the same applies to other languages. The estimated effort is under one hour, plus sandbox testing.<br/>
For code examples of signing and RSA encryption/decryption, please refer to the [FastAPI Integration Guide](https://www.bitget.com/docs/classic/fastapi-integration-guide#code-examples-java)<br/>
For the detailed migration timeline, please refer to [Bitget FastAPI Signature Algorithm Upgrade Notice](https://www.bitget.com/support/articles/12560603899220)
