Deribit’s Eight-Hour Public Open-Interest Lag Complicates BTC Analysis

By Elena Vasquez

Deribit plans to delay affected public open-interest data by at least eight hours, so a refreshed Bitcoin leverage chart can still display positioning from at least eight hours earlier. The change follows a separately scheduled maintenance outage, while Deribit says order execution, margin and equity updates remain real time.

What does the lag mean for leverage charts?

A chart combining current Bitcoin prices with public open interest will mix two different observation times. A price move shown beside a rise or fall in displayed positions cannot establish whether traders added or closed positions during that move.

The problem extends to open-interest concentrations across option strikes, which will describe earlier positioning. “Max pain,” the settlement price that minimizes aggregate intrinsic-value payouts to option buyers, will inherit delayed inputs whenever it uses the affected public data.

Deribit’s education material calls max pain “a limited tool when used alone.” A dashboard refreshed moments ago can still show positioning from at least eight hours earlier, so a fresh timestamp does not cure a stale input.

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, rather than the interval between two scheduled events.

In plain terms, a live-looking chart will not provide synchronized price and leverage data.

Which trades receive delayed publication?

Deribit’s 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 trades, or RFQs.

On-screen trades, liquidations and block trades outside Block RFQ are excluded from delayed publication. That limit keeps the feature confined to qualifying blocks; it does not remove the broader lag from public open-interest data.

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. The aggregate threshold is three times the tranche threshold and defines a narrow group of large bitcoin-settled requests.

The delayed tape covers qualifying large blocks, not every execution shown on the platform.

What happens around the 08:00 UTC settlement?

Qualifying trades normally publish after eight hours, an interval equal to one-third of a full day. Deribit will shorten the wait where needed so publication is scheduled by 07:00 UTC, one hour before daily settlement at 08:00 UTC.

Trades executed in the final hour before the 08:00 UTC settlement will publish immediately. This exception narrows the wait for trades nearest settlement, but it does not make other qualifying blocks current.

Most qualifying blocks still wait eight hours, while trades in the last pre-settlement hour receive immediate publication.

How do volume and risk data change?

Delayed trades enter the 24-hour volume measure eight hours after execution and remain included for the following 24 hours. Other trades continue to count in real time, so the delay affects when qualifying trades enter the rolling window rather than whether they remain in it.

Deribit said execution “remains immediate” and margin and equity updates “remain real time” under the reporting rules. Trading and risk calculations continue on their own clocks even as public data carries the reporting delay.

The cited materials do not provide a date for the maintenance outage. After that outage, the market-structure change will be testable: traders can transact and receive risk updates on current data while public open-interest data may lag by at least eight hours.