Oracle data with the derivatives layer on top.

The oracle starts at the underlying price and builds the derivatives layer on top: forwards, implied volatility, settlement and mark prices, signed and delivered on-chain.

Block Scholes2 min read

Of on-chain options marked
90%+
Pull oracle, as fast as
200ms
Oracle delivery
Push + pull
With the pull oracle
Any chain

/01 The problem

Derivatives protocols need more than a spot price

A typical oracle publishes only the underlying price, which is sufficient for a spot swap. A protocol that lists perpetuals, options or structured products also needs the forward curve, implied volatility at the strikes they list, a settlement value at expiry and a mark price their liquidation engine can trust.

Without that layer, each protocol rebuilds it in-house from thin on-chain liquidity, and the values that determine liquidations and payouts become the weakest part of the stack.

/02 The derivatives layer

The underlying and the derivatives built on it

A spot price tells a protocol where the market is. Everything a derivatives protocol runs on sits on top of it: the perpetual’s funding and basis, the futures curve, the implied volatility at the strikes it lists, the settlement value at expiry, and the mark price its liquidation engine trusts.

Block Scholes delivers that whole layer from one composite, calibrated off-chain and signed on-chain, using the same feeds used to mark more than 90% of on-chain options.

  • Spot — a composite index price across venues
  • Perpetuals — index and mark prices, with funding
  • Futures — every listed expiry on one forward curve
  • Options — implied volatility off a calibrated surface, at any strike and expiry
  • Settlement — a TWAP or point-in-time value at expiry
  • Custom mark prices — derived from the client’s own order book, evaluated against our index

/03 Push or pull

Two ways to read it: push or pull.

Push keeps the latest signed value on-chain, updated on a heartbeat plus deviation triggers. It is straightforward to read and moves more slowly by design, since the value changes only when a trigger fires. Pull fetches a signed update the moment a transaction needs it, as fast as 200ms, verified on receipt, with gas paid only when you read.

  • Push — always on-chain, updated on heartbeat and deviation triggers
  • Pull — as fast as 200ms, verified on receipt, gas paid per read
  • Signed with EIP-712 on EVM and BCS on Sui, or any scheme agreed with you

/04 Any chain

Integration on any chain via the pull oracle

Push feeds run on EVM-compatible chains and Sui. The pull oracle extends further: the payload is signed off-chain and verified by the consuming contract when it is read, so we can deploy and integrate it with any chain or protocol that can verify a signature.

Payloads are signed with EIP-712 on EVM chains and BCS on Sui today, and we can sign with any scheme requested and agreed with you.

/05 The method

The method behind the values

Filter. Every quote is screened before calibration: one-sided, stale and arbitrageable prices are removed.

Repair. The remaining quotes are checked for static arbitrage across strikes and expiries. A violation small enough to repair is repaired; one too large to repair is discarded.

Weight. Each source is weighted by confidence, and the weights sum to one. The result is fitted across every listed expiry onto one continuous surface, so any strike or tenor has a calibrated value.

The method, in full →

Questions

What teams ask before they build.

  • Should a protocol use push or pull?

    Push keeps a signed value on-chain with no callout, but it is slower moving: it only updates on a heartbeat or when a deviation trigger fires. Pull fetches a signed update when a transaction needs it, as fast as 200ms, so the value is as fresh as the moment it is used.
  • Which signatures do you support?

    EIP-712 on EVM chains and BCS on Sui today. We can sign with any scheme requested and agreed with you.
  • Which chains are supported?

    EVM-compatible chains and Sui. With the pull oracle we can deploy and integrate with any chain that can verify a signed payload.

Read next

The data and tools behind this.

Get started

A derivatives data layer for DeFi protocols. Delivered by push or pull, on the protocol’s own chain.

Data Plans
As of
BTC SPOT61,913.61−1.71% (since 19 Nov 2026 00:00 UTC)BTC FWD 30D62,155.96−1.75% (since 19 Nov 2026 00:00 UTC)BTC BASIS 30D+39.1bpBTC FUNDING+0.2bp−0.2bp (since 19 Nov 2026 00:00 UTC)BTC ATM 7D46.91%+0.95 vol pts (since 19 Nov 2026 00:00 UTC)BTC 25Δ SKEW 7D−9.34−2.06 vol pts (since 19 Nov 2026 00:00 UTC)BSIV 30D51.82+2.24 vol pts (since 19 Nov 2026 00:00 UTC)ETH SPOT$1,755−1.10% (since 19 Nov 2026 00:00 UTC)ETH ATM 7D60.30%+2.49 vol pts (since 19 Nov 2026 00:00 UTC)ETH 25Δ SKEW 7D−9.28−2.32 vol pts (since 19 Nov 2026 00:00 UTC)HYPE SPOT$66.73−0.27% (since 19 Nov 2026 00:00 UTC)HYPE ATM 7D75.53%+6.57 vol pts (since 19 Nov 2026 00:00 UTC)HYPE 25Δ SKEW 7D−3.76−4.35 vol pts (since 19 Nov 2026 00:00 UTC)SOL SPOT$73.06−0.65% (since 19 Nov 2026 00:00 UTC)SOL ATM 7D69.16%+4.28 vol pts (since 19 Nov 2026 00:00 UTC)SOL 25Δ SKEW 7D−6.32−6.46 vol pts (since 19 Nov 2026 00:00 UTC)XRP SPOT$0.9592−0.74% (since 19 Nov 2026 00:00 UTC)XRP ATM 7D74.59%+1.49 vol pts (since 19 Nov 2026 00:00 UTC)XRP 25Δ SKEW 7D−5.00−1.21 vol pts (since 19 Nov 2026 00:00 UTC)SPX SPOT$7,170−2.49% (since 19 Nov 2026 00:00 UTC)SPX ATM 7D25.40%+3.64 vol pts (since 19 Nov 2026 00:00 UTC)SPX 25Δ SKEW 7D−6.62−1.53 vol pts (since 19 Nov 2026 00:00 UTC)NVDA SPOT$145.78−4.04% (since 19 Nov 2026 00:00 UTC)NVDA ATM 7D60.32%+1.38 vol pts (since 19 Nov 2026 00:00 UTC)NVDA 25Δ SKEW 7D−8.10−1.99 vol pts (since 19 Nov 2026 00:00 UTC)SPCX SPOT$137.03−5.23% (since 19 Nov 2026 00:00 UTC)SPCX ATM 7D59.37%+2.26 vol pts (since 19 Nov 2026 00:00 UTC)SPCX 25Δ SKEW 7D−9.40−2.19 vol pts (since 19 Nov 2026 00:00 UTC)MU SPOT$683.05−4.10% (since 19 Nov 2026 00:00 UTC)MU ATM 7D87.40%+0.93 vol pts (since 19 Nov 2026 00:00 UTC)MU 25Δ SKEW 7D−12.49−2.59 vol pts (since 19 Nov 2026 00:00 UTC)