Exchange Updates
Dated notes on listings, fee changes, product launches and policy updates announced by crypto exchanges, each tied to the official notice.
Searches all 670 published articles by title, summary and platform.
Page 2 of 7
2026-10-09
3 stories- Exchange Updates
OKX Withdrawal Address Verification and Allowlist Controls
OKX withdrawal safety should be read as an address-book and verification workflow, not as a generic whitelist label.
- Exchange Updates
Kraken WebSocket v2 Add and Cancel Order Lifecycle Readiness Checklist
Kraken WebSocket v2 order controls should be treated as a lifecycle with command, acknowledgement, execution and reconciliation states.
- Exchange Updates
Bybit UTA Account Mode and Margin Mode Readiness Checklist
Bybit's Unified Trading Account documentation makes account mode and margin mode separate readiness controls.
2026-10-08
8 stories- Exchange Updates
Bybit SMP Trade Group and Order-Control Readiness Checklist
Bybit's self-match-prevention documentation turns SMP into an account and order-control question rather than a generic safety badge.
- Exchange Updates
Binance and OKX API Timestamp Signatures: Replay and Drift Risk Radar
Binance and OKX both require signed private API requests, but their replay-control evidence should be recorded as venue-specific authentication rules.
- Exchange Updates
OKX Chase Limit Trigger Orders: API Readiness Checklist
OKX's chase limit order update should be handled as an API-readiness change, not a trading signal. The OKX changelog says FUTURES and SWAP trigger orders can use chase as a post-trigger execution type, with advChaseParams in.
- Exchange Updates
Binance Order Amend Keep Priority: API Readiness Checklist
Binance's order-amend surface should be treated as a reconciliation feature, not a shortcut around normal order controls. The official trading endpoint, filters and user-data stream documents are the evidence boundary.
- Exchange Updates
Bybit Pre Check Order API: Risk-Limit Readiness Checklist
Bybit's V5 pre-check route is useful only when it is placed in a larger evidence chain. The source-backed chain is instrument metadata, local order construction, pre-check response, live place-order response and post-action.
- Exchange Updates
Kraken WebSocket Token and Dead Man's Switch Order-Control Radar
Kraken order automation should separate WebSocket session control from dead man's switch protection. Kraken support documentation says authenticated WebSocket trading uses a token retrieved through GetWebSocketsToken and that the.
- Exchange Updates
OKX and Bybit Subaccount API Permission and IP Binding Controls
OKX and Bybit both document API permissions, subaccount boundaries and IP binding, but their control surfaces are not interchangeable.
- Exchange Updates
Coinbase WebSocket Level2 Batch Channel Readiness Checklist
Coinbase WebSocket readiness should be handled as a channel-specific evidence plan. Coinbase documentation separates the Exchange WebSocket overview from channel documentation, and the channel page is the source for level2 and.
2026-10-07
5 stories- Exchange Updates
Coinbase Exchange WebSocket Sequence and Channel Readiness Checklist
Coinbase Exchange WebSocket readiness should be treated as a channel-by-channel evidence plan rather than a single connection test.
- Exchange Updates
Bybit Self Match Prevention: smpType and Order-History Readiness Checklist
Bybit Self Match Prevention should be treated as an order-lifecycle control, not a label that proves a strategy is safe.
- Exchange Updates
Deribit Heartbeat and Cancel-on-Disconnect Readiness Checklist
Deribit documentation makes connection liveness an order-risk control rather than a background networking detail.
- Exchange Updates
OKX expTime and Rate Limit Readiness Checklist
OKX API documentation turns order timeout handling into an explicit request-control decision. The current API guide describes an optional expTime request header for place-order and amend-order calls so a request can be discarded.
- Exchange Updates
Kraken Dead Man's Switch API Readiness Checklist
Kraken's dead man's switch should be treated as an outage-control mechanism, not as a generic safety label.
2026-10-06
8 stories- Exchange Updates
Kraken Earn Deallocate Status API Readiness Checklist
Kraken Earn API operations should be handled as asynchronous fund-control workflows, not as a single button result.
- Exchange Updates
Bybit WebSocket Order Entry Batch Timestamp Readiness Checklist
Bybit's V5 order-entry materials should be read as an implementation-readiness checklist rather than a guarantee that every bot can safely batch trade.
- Exchange Updates
Coinbase and Kraken FIX Sequence Reset and Cancel-on-Disconnect Controls
Coinbase and Kraken FIX controls solve different failure modes, so a venue runbook should not treat sequence reset, drop-copy recovery and cancel-on-disconnect as the same safety action.
- Exchange Updates
dYdX Indexer WebSocket and Subaccount Readiness Checklist
dYdX v4 indexer evidence should be treated as an application data-readiness question, not as proof that a wallet is approved or a trade is safe.
- Exchange Updates
Binance, Kraken and OKX Cancel-All-After Order Safety Controls
Binance, Kraken and OKX expose different order-cancellation safety controls, so an automation runbook should separate immediate cancel-all actions from timer-based cancel-on-disconnect controls.
- Exchange Updates
Binance Signed-Endpoint Percent-Encoding Migration Checklist
Binance developer documentation now makes percent-encoding part of the signed-payload control surface for affected REST examples, and the Spot Block Matching changelog warns that requests not following the order will be rejected.
- Exchange Updates
Binance User Data Stream Reconnect Gap and REST Backfill Checklist
A Binance User Data Stream reconnect plan should prove more than transport recovery. Binance documentation describes account and order updates through User Data Stream, REST request security requirements, WebSocket API.
- Exchange Updates
Coinbase, Kraken and OKX WebSocket Cancel-State Reconciliation Controls
Coinbase, Kraken and OKX expose different WebSocket surfaces for order lifecycle monitoring, so a cancel-state runbook should not normalize every message into one generic event.