Deribit options data methodology

PerpFinder covers Deribit only. The BTC and ETH feeds contain inverse options, which use the underlying coin for quotes and settlement. USDC options and other venues are outside this dataset.

The September 13, 2026 metadata check confirmed the first stored observation in the BTC history response and the ETH history response. Each response includes its returned observation count, period, status, and methodology version.

The Deribit book summary API supplies instrument rows with the option filter and BTC or ETH currency. PerpFinder uses these fields:

• instrument_name identifies the asset, expiry, strike price, and call or put.
• mark_iv gives the IV associated with the venue mark price, in percent.
• open_interest gives outstanding quantity in BTC or ETH. One inverse option contract represents one coin.
• volume gives traded quantity over the rolling 24-hour window, in BTC or ETH.
• volume_usd supplies USD traded premium. Premium is the option purchase price; it differs from underlying notional value.
• underlying_price supplies the expiry forward price for USD conversion.
• creation_timestamp supplies the venue response time.

The index price API supplies the separate BTC or ETH index price. The USD open-interest calculation uses the expiry forward price.

Deribit DVOL is the venue's 30-day implied volatility index, expressed on an annual scale. It does not predict price direction or specify a 30-day percentage return. Deribit publishes its DVOL calculation method.

The current headline uses the latest close from Deribit's one-minute DVOL candles. PerpFinder requests a two-hour window through the volatility index API. That source time differs from the time when PerpFinder collects the option rows.

PerpFinder stores DVOL readings alongside its option snapshots. The historical charts use those stored observations. Earlier candles available from Deribit are external history; PerpFinder does not import them into this snapshot series.

• USD open interest: outstanding coin quantity × the instrument's expiry forward price, summed across valid rows.
• USD notional volume: traded coin quantity × the instrument's expiry forward price, summed across valid rows.
• Put/call volume ratio: put quantity traded over 24 hours ÷ call quantity traded over 24 hours.
• Put/call open-interest ratio: put USD open interest ÷ call USD open interest.
• At-the-money (ATM) IV: mean call and put mark IV at the strike nearest the expiry forward price.
• The ATM calculation uses one side if only that side has valid IV. No valid IV means no term-structure point.
• Volatility by strike: separate call and put mark IV for the nearest expiry with at least two rounded days remaining.
• The strike curve includes strikes from 0.5 to 1.6 times the forward price. It does not calculate 25-delta skew.
• Largest open-interest expiry: the future expiry with the largest total USD open interest. The nearest expiry can differ.

USD notional can change when the forward price changes, even with unchanged contract quantity. Open interest does not identify trader intent, execution capacity, or price direction.

• The parser rejects malformed instruments, nonpositive strikes, expired contracts, and missing or nonpositive forward prices.
• It rejects venue timestamps more than five minutes in the future. Duplicate instruments keep the newest timestamp.
• IV must be greater than zero and below 1,000%. Invalid IV becomes null; other valid fields remain available.
• A missing or zero call denominator produces a null put/call ratio. The display shows an unavailable value or a dash.
• Current normalization maps missing or invalid quantity and premium-volume fields to zero. Those zeros cannot distinguish invalid source values from inactivity.

The current API can serve its last successful snapshot after a venue failure. Its status describes collection age or asset availability. Individual DVOL readings have a separate source timestamp and availability status.

The bulk feed supplies mark IV without bid/ask IV or option-price sensitivities called Greeks. Mark IV does not establish the price or size available for an order.

Self-collected history starts at the first observed datapoint in persisted metadata. The collection target is one snapshot every 15 minutes, or 96 observations per complete UTC day. Failed collection can reduce that count.

• sourceTimestamp records venue time; ingestedAt records storage time.
• intervalStart identifies the 15-minute bucket; generatedAt records aggregate calculation time.
• The raw record preserves venue rows with schema and normalizer versions. Each aggregate carries its methodology version.
• Daily summaries below 70% of expected observations carry a partial status.
• Rolling 24-hour volume windows overlap. Daily summaries store closing and mean window values; they do not sum the windows.
• Historical charts require seven days of collection, 500 stored observations, and 100 valid chart points.
• Charts include partial observations with labels and exclude stale or invalid observations. The history API can return stale observations with its status.

No synthetic backfill: PerpFinder does not reconstruct past option markets from current contracts. A requested history period can contain fewer observations than the schedule implies.

Retention policy: the storage design targets at least 90 days of raw snapshots and permanent intraday and daily aggregates. This policy does not establish complete coverage for any period.

Deribit inverse options expire at 08:00 UTC. Their delivery price uses the relevant index's time-weighted average from 07:30 to 08:00 UTC. The inverse option specifications define contract size and settlement currency.

• Collection: PerpFinder data
• Content: PerpFinder editorial
• Review: PerpFinder review

Report data or content errors through the correction policy.