The oracle

Settlement uses RackOracle, a multi-publisher price feed on Monad. No existing oracle network publishes GPU rental prices on Monad, and the commercial GPU indices do not allow republishing or settlement use, so Rackrate runs its own, built from openly licensed price data.

Publishers

Three allowlisted publishers submit a price every hour:

• A, Chainlink CRE. A Chainlink Runtime Environment workflow fetches the real price data over CRE's HTTP capability, computes the price and delivers a report to the CreReceiver contract. Until Chainlink grants deploy access, it runs in CRE simulation mode, with each report delivered onchain through Chainlink's test forwarder.
• B and C, bots. Two independent processes with separate keys.

Finalizing an hour

• The price for an hour is the median of at least two submissions.
• It must fall inside fixed bounds ($0.50 to $20 for H100) and within a 25% jump of the previous price. After three jump rejections in a row the next valid median is accepted, so a genuine regime change cannot freeze the feed.
• Hours finalize strictly in order. An hour without enough valid data is recorded as a gap and is never filled in.
• Feed parameters are fixed when the feed is created. Nobody, including the team, can change the rules for a live series.

Real prices, auditable hours

Since Wednesday, October 7, 2026 (18:00 UTC) the H100 index follows real prices. Each day Rackrate takes every GPU cloud's published on-demand H100 SXM price, uses each provider's median, and then the median across providers. The data comes from the open daily snapshots of gpurentalprices.com (CC BY 4.0), which record each provider's own pricing page or API.

• An hour is priced from the two previous days' values, moving smoothly between them through the day, so every publisher works from the same published snapshots.
• Listed prices change rarely, so the model adds only small intraday texture: a daily demand cycle and slow noise, about 2 to 3% in all.
• That texture comes from secret per-period seeds. Each seed is committed onchain before any price uses it and revealed afterwards, so hours cannot be predicted in advance but anyone can re-derive every submission from the revealed seeds and the public snapshots. The repository includes an audit script that does exactly that.

Hours before the switch, and demo weeks, use a fully simulated index from the same committed seeds. Week 2026-W41 therefore settles on a mix of simulated and real hours.

See every hour on the Oracle page.