Bitcoin traders using Deribit’s public positioning data will face an eight-hour lag under a release scheduled for Tuesday, Nov. 10. The change will leave charts of outstanding futures and options positions looking backward even as traders compare them with current prices.
Deribit’s updated release notice schedules maintenance for 09:00 UTC, with about 45 minutes of downtime during which clients cannot communicate with the exchange. The release was postponed from Nov. 5.
The broadest change concerns open interest, the positions that remain open. Public figures will show the state eight hours earlier across all futures and options, whether or not any trades were delayed. Deribit says real-time open interest will no longer be available through its API.
What the lag means for leverage charts
A chart combining current Bitcoin prices with that public open interest will mix two different observation times. A price move alongside a displayed rise or fall in positions will therefore be insufficient to establish whether traders added or closed positions during that move.
The same limitation carries into expiry analysis. Concentrations of open interest across option strikes will describe earlier positioning. “Max pain,” the settlement price that would minimize aggregate intrinsic-value payouts to option buyers, will inherit delayed inputs when it uses the affected public data.
Deribit’s education material already describes max pain as a limited tool when used alone. The reporting change adds a freshness problem: a dashboard refreshed moments ago can still be displaying positioning from at least eight hours earlier.
Which trade publication is delayed?
For qualifying opted-in large Block RFQ trades, publication normally waits eight hours, shortened before settlement. The open-interest lag applies regardless.
On-screen and liquidation trades do not use delayed trade publication. Public open interest still shows positions eight hours earlier.
Current prices with delayed OI cannot confirm fresh position changes. Expiry and max-pain maps using that OI inherit the lag.
Changes remain scheduled for November 10, 2026, following maintenance from 09:00 UTC with about 45 minutes expected downtime. Block RFQ publication is normally delayed eight hours, shortened to publish before the final settlement hour; final-hour trades publish immediately. No price forecast or live positions are shown.
CryptoSlate’s Nov. 5 expiry coverage examined a separate timing gap between options expiry and the US jobs report. The new issue concerns the age of the positioning data itself.
The separate trade-publication feature has a narrower scope than the blanket open-interest lag. It is available on request for qualifying large block request-for-quote (RFQ) trades. On-screen trades, liquidations and blocks outside Block RFQ are excluded from delayed trade publication.
For BTC-settled Block RFQs, the minimum is 1,000 BTC per tranche, with an overall requested trade of at least 3,000 BTC within one settlement cycle.
Qualifying trades will normally be published after eight hours. The wait will shorten where needed so publication is scheduled by 07:00 UTC, one hour before daily settlement. Trades executed in the final hour before the 08:00 UTC settlement will be published immediately.
Volume has its own rule: delayed trades enter 24-hour volume eight hours after execution and remain included for the following 24 hours. Other trades continue to count in real time.
Deribit says execution remains immediate and margin and equity updates remain real time under the reporting rules. After the separately scheduled maintenance outage, the data lag will affect public visibility while trading and risk calculations continue on their own clocks.
