⚠️ 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.
Warning
This release will cancel all open hidden and partially hidden orders. Users are advised to place new Iceberg orders instead.
Warning
Rate limiting for public/get_instruments on websocket API has been updated: 1 request per 10 seconds, with a burst of 5. To avoid rate limits, we recommend using either the REST requests or the WebSocket subscription to instrument_state.{kind}.{currency} for real-time updates.
Iceberg Orders
We are introducing Iceberg orders as a replacement for fully hidden orders, which are no longer supported. Iceberg orders allow traders to show only a portion (display amount) of the total order in the order book, while keeping the remaining amount hidden. As the visible portion is filled, the next portion is automatically revealed, maintaining the original refresh amount until the order is nearly or fully executed.
To enforce proper usage and maintain order book integrity:
-
The initial display amount must be at least 100 times the instrument’s minimum order amount.
-
The ratio of the displayed portion to the total order amount must be at least 1% (i.e., the display amount must be at least 1/100 of the total amount).
Learn more about Iceberg orders in our Order attributes article.
Warning
Iceberg orders are not supported on future spreads
VASP website
As part of Deribit’s continued efforts to comply with the Travel Rule and global regulatory standards, users are now required to provide the website of the VASP (Virtual Asset Service Provider) when adding or editing a withdrawal address, if the VASP is not included in Deribit’s list of known providers.
-
For unlisted VASPs, both the VASP name and website URL must be provided by the user.
-
For known VASPs, the website will be displayed automatically based on internal configuration.
Please refer to our Withdrawals article for more details.
The following API updates will be included in this release:
Breaking Changes
-
Deprecated the
max_showparameter and introduceddisplay_amountto define the visible portion of an iceberg order. -
The private/buy, private/sell, and private/edit API methods now support the optional
display_amountparameter. -
Order responses and events for iceberg orders now include
display_amount(current visible portion) andrefresh_amount(initially requested display amount).
Note
refresh_amount remains constant throughout the order’s lifecycle. It represents the intended size of each iceberg “tip” as it gets replenished. The actual display_amount can be lower than refresh_amount when the order is partially or nearly fully filled.
For example, if the total order amount is 10,000, refresh_amount is 1,000, and 9,500 has already been filled, the current display_amount would be 500 — the remaining visible portion.
-
Fee discounts are now returned per currency pair in the responses of private/get_account_summary and private/get_account_summaries.
-
Rate limiting for public/get_instruments on websocket API has been updated: 1 request per 10 seconds, with a burst of 5.
Important
To avoid rate limits, we recommend using either the REST requests or the WebSocket subscription to instrument_state.{kind}.{currency} for real-time updates.
-
Added a new field
beneficiary_vasp_websiteto private/add_to_address_book, private/update_in_address_book, and private/get_address_book. This field is mandatory if the address belongs to a VASP not listed among known VASPs.
Non-Breaking Changes
-
Added a new
extra_currenciesparameter to the private/add_to_address_book method, allowing a list of valid ERC20 currencies. Theextra_currenciesparameter can only be used when currency is set to an ERC20 and type is set to withdrawal. -
Introduced a new event channel: block_trade_confirmations.{currency}, which functions like block_trade_confirmations but supports filtering by currency for more efficient data handling.
FIX
Breaking changes
As part of the iceberg order feature rollout, the FIX API now uses DisplayQty(1138) tag instead of MaxShow(210). Additionally the RefreshQty(1088) tag has been added as a non-mandatory field in Execution Reports (8). This optional tag defines the quantity used to refresh DisplayQty.