Hyperliquid vs Sky (Maker)

Hyperliquid vs Sky (Maker) on 1 shared OpenChainBench benchmark, awaiting live measurements.

Read methodology Last measured Window: rolling 24h1 shared benchmark
Hyperliquid logo
Hyperliquid

Onchain perp DEX on the Hyperliquid L1. Fully onchain orderbook with sub-second matching, no off-chain matching engine.

Sky (Maker) logo
Sky (Maker)

Rebrand of MakerDAO around USDS and SKY. Smart Burn Engine routes protocol surplus to buy and burn SKY against USDS on Uniswap v2.

Side by side measurements

DeFi token buyback tracker, live executed vs promised ratio

Trading

Hyperliquid

Leads

105.0 %

p99
105.0%
rank
#1
samples
15,543,300

Sky (Maker)

No data in window

Two caveats. (1) A low ratio is not a protocol failure. Some programs (Sky SBE) batch executions, so the executed_usd line is lumpy and routinely sits well below promised_usd inside a rolling window even though the long-run ratio converges to ~1. (2) The Sky leg requires an ETHERSCAN_API_KEY on the harness host. Without it the executed side returns 0 and the ratio reads 0; the live deployment has the key set.

Frequently asked questions

Hyperliquid vs Sky (Maker): which one is better?

Hyperliquid and Sky (Maker) are compared on 1 shared OpenChainBench benchmarks. See the live table on this page for every metric.

How is the Hyperliquid vs Sky (Maker) comparison measured?

Every benchmark on this page uses the same open methodology, published at https://openchainbench.com/methodology. Data is CC-BY-4.0. Measurement harnesses are MIT-licensed.

Related comparisons

How this pair was selected

Auto-generated pairs require: both providers in the same benchmark for seven consecutive days, at least 1000 samples per provider, observable third-party search demand, and a public /products/[slug] page on OCB. Editorially curated pairs (like this one) may publish early when search demand is high and data is accruing — panels with fewer than 100 samples are shown as provisional. The full pair ledger is versioned in the public repo.

Live data refreshes via ISR within 60 seconds of a new run. Sources are the same Prometheus queries surfaced on the parent benchmark pages.