Skip to content

Add Yieldo Funding Benchmark to Analytics - #20

Open
polisadov wants to merge 1 commit into
sbs2001:mainfrom
polisadov:add-yieldo-funding-benchmark
Open

Add Yieldo Funding Benchmark to Analytics#20
polisadov wants to merge 1 commit into
sbs2001:mainfrom
polisadov:add-yieldo-funding-benchmark

Conversation

@polisadov

@polisadov polisadov commented Sep 7, 2026

Copy link
Copy Markdown

Adds Yieldo Funding Benchmark to the Analytics section.

What it is

An open dataset comparing annualised perpetual-futures funding rates on Hyperliquid against other perp DEXes and a median line for centralised exchanges, so the three can be read on one scale.

Hyperliquid settles funding hourly while most centralised venues settle every eight hours, which makes raw quotes incomparable. Every value is rescaled with rate x 24 / interval_hours x 365 x 100, and the funding interval is published per row so the normalisation can be checked rather than trusted.

Coverage

  • Hyperliquid: 3,206 daily rows across 56 coins, continuous since 2026-07-05
  • Whole panel: 31,342 rows, 12 venues, 62 coins, 64 days
  • Every exchange appears under its own name — nothing is pooled
  • Each row carries observations and distinct_rates, so readers apply their own quality threshold instead of inheriting the publisher's

Why it belongs here

Same shape as the OpenChainBench and perp.wiki entries already listed: open methodology, machine-readable feeds, CC BY 4.0.

Disclosure

I maintain Yieldo. The data comes from each exchange's own public API; there is no history before 2026-07-05, no backtest and no yield claim, and the limitations are documented in the archived package rather than implied.

Open dataset comparing annualised perpetual funding rates on Hyperliquid
against other perp DEXes and a median of centralised exchanges, archived
with a DOI and published under CC BY 4.0.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EPHvsaMJ8L18ztYg2KYHrb
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant