1. Deribit Support
  2. Exchange
  3. Releases
  4. 2026 Releases

27 February 2026

  • Updated

Note

This release has been rescheduled from 24 February 2026 to Friday, 27 February 2026, 9:00 AM UTC.

⚠️Expected downtime: 15 - 30 minutes

Client impact:Maintenance 9 AM UTC - The system will be down for around 15 - 30 minutes. Client systems will not be able to communicate with Deribit during this time.

Features

New HFT Nodes

To further improve performance and increase scalability, we are introducing additional High-Frequency Trading (HFT) nodes. Alongside this, we have implemented a new feature to manage connectivity and prevent a single subaccount from concurrently accessing multiple HFT nodes.

Key Changes

  • Two More HFT Nodes: New HFT nodes will be made available to enhance trading performance.

  • Single Subaccount Connection: To ensure fair resource distribution, a subaccount can now only be logged into and authenticate with a single HFT node at a time. This restriction applies to all connection types: WebSocket, REST, and FIX.

  • Disconnection Requirement: If a subaccount switches its connection to another HFT node, all existing active connections (made with any API key from that subaccount) on the previous node will be automatically terminated. Clients must implement robust reconnect logic to handle these necessary disconnections.

Client Routing

  • AWS-based clients will be routed exclusively to ld4-hft-01-prd.

  • Cross-connected and colocation clients may choose which HFT node to connect to, but the single-node-per-subaccount rule applies.

  • Retail users are unaffected. Retail users are allowed to authenticate to multiple retail nodes and are not affected by this new node.

Availability

The new nodes will be made available as of 27 February 2026, 9:00 AM UTC.

The existing connection IP 193.58.254.1 will stay the same but will no longer automatically fail over to a standby node in case of issues.

The additional nodes have IP addresses 193.58.254.2 and 193.58.254.3.

Block RFQ Extra Fee

We've improved our Block RFQ workflows to support an "Extra" fee mode, which gives brokers more flexibility.

  • Broker Service Fees: Brokers can now charge a separate, additional service fee to their clients for block trading activity.

  • How It Works: This extra fee can be applied to:

    • Block trades executed directly by a broker on behalf of a client.

    • Trades that result from Block RFQ allocations.

  • Setting the Fee: Brokers can specify the exact extra fee rate they want to charge, or they can choose to automatically apply the maximum allowed fee rate.

API Updates

Wallet

Withdrawal Email Notifications

We've implemented new email notifications to keep you informed about your withdrawal status:

  • Withdrawal admin verification notifications: You will now receive an automatic email notification when a withdrawal was sent to manual admin approval.

  • Withdrawal delay change notifications: You will now receive an email notification whenever your withdrawal delay settings are changed.

  • Withdrawal new address added: You will now receive an email notification when a new withdrawal address is added to your address book.

API

Warning

Action required: The deprecated method private/get_pending_block_trades will be removed. Please use private/get_block_trade_requests instead.

FIX

FIX ExecutionReport (8) messages now include tag 152 (CashOrderQty). This field indicates that the original order quantity is expressed as a USD value (specifically, BTC & ETH inverse futures and perpetuals), enabling clients to differentiate between value-based orders and quantity-based orders.

  • Value-based orders (where the client specified the desired order size as a USD amount): Both tag 38 (OrderQty) and tag 152 (CashOrderQty) are present and equal, reflecting the USD amount.

  • Quantity-based orders (where the client specified the desired order size in contracts): Only tag 38 (OrderQty) is present. Tag 152 (CashOrderQty) is absent.