> ## Documentation Index
> Fetch the complete documentation index at: https://docs.defiloops.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Hyperliquid

> Live funding and open interest per coin, and liquidations with the address they happened to — a stream that records forward only

A third perpetuals venue, kept apart from the other two on purpose.

## Why it is not folded in with the others

Three differences, each of which would corrupt a shared table:

* **Funding settles hourly.** A complete day is twenty-four intervals, not
  three. Annualising it with the other venues' factor overstates by eight, and
  the two numbers look equally plausible side by side.
* **Open interest has no history at all.** The venue reports it as it is *now*.
  There is nothing to backfill and never will be.
* **History begins 2023-05-12**, the venue's own start. An empty answer for 2021
  is correct rather than a failure.

Folding these into the same day rows would need one "is this day complete" test
that has to know which venue wrote each row.

## What it gives that the others do not

**Liquidations with the address.** No centralised venue publishes who was
liquidated. Here each forced close carries the address, the fill price, the mark
price at the time, whether it was taken **at market or backstopped**, and which
HLP vault absorbed it.

```json theme={null}
{
  "coin": "TAO",
  "px": 233.91,
  "sz": 0.008,
  "ntlUsd": 1.87,
  "user": "0xd976af15de1feddd643eda7768cb3bb26a6cdd74",
  "markPx": 234,
  "method": "market",
  "vault": "HLP Strategy B"
}
```

**Live state per coin**, not just BTC and ETH: the current hourly funding rate,
open interest, oracle and mark price, and the premium between them — which is
what funding is computed from and the cleanest single reading of whether the
perpetual is trading rich.

## It records forward only

Because neither series can be fetched retrospectively, this stream contains
exactly what has been watched and nothing earlier. Both responses say so.

<Warning>
  A reader cannot tell a short history from a quiet market by looking at the rows.
  That is why the answer states when the record begins rather than leaving it to
  be inferred.
</Warning>

## Status

The endpoints are deployed and behind the same key as everything else. The
watcher that fills them runs on a schedule; until it has, they answer with what
is missing and why rather than with an empty list.


## Related topics

- [What we hold](/data/streams.md)