# Canonical: https://www.uddalak.xyz/hyperliquid-academy/article/36-robust-price-indices-oracles
# Author: Uddalak Das
# Last source: https://www.uddalak.xyz/hyperliquid-academy/article/36-robust-price-indices-oracles

---
title: "Robust Price Indices and Oracles on Hyperliquid"
description: "How Hyperliquid separates traded prices from oracle and mark prices used for funding, margin, and liquidation."
track: "Markets & Trading"
level: "Advanced"
primary_icp: ["trader", "builder"]
secondary_icp: ["institutional decision-maker"]
reading_time: "3 min"
last_reviewed: "2026-09-07"
---

# Robust Price Indices and Oracles on Hyperliquid

A perpetual market needs more than the most recent trade price. If one thin trade could determine liquidations or funding, a manipulator could push the order book briefly and affect positions far larger than the trade itself.

Hyperliquid therefore uses **oracle and mark-price systems** that are designed for risk calculations rather than simply copying the last fill.

```mermaid
flowchart LR
    A[External reference venues] --> B[Oracle inputs]
    C[Hyperliquid order book] --> D[Local market inputs]
    B --> E[Robust price logic]
    D --> E
    E --> F[Mark price]
    F --> G[Margin and liquidation]
    E --> H[Funding inputs]
```

## Oracle price anchors the external market

The oracle price represents an external reference for the underlying asset. Validators publish price information according to the protocol's oracle rules, reducing dependence on a single Hyperliquid trade.

For HIP-3 markets, oracle operations can be part of the deployer's responsibility, which means oracle methodology becomes a market-specific risk rather than a uniform protocol assumption.

## Mark price is built for risk

The mark price is used in important account calculations such as unrealized PnL and liquidation logic. It can combine oracle information with local market signals and protective clamps to reduce the effect of temporary dislocations.

That means three prices can coexist:

- **last price:** the most recent executed trade
- **oracle price:** external reference information
- **mark price:** the risk-engine price derived under protocol rules

## Why professionals should care

Price-source design affects liquidation fairness, basis behavior, funding, and the possibility of manipulation. Two exchanges can list the same perp and still have different liquidation outcomes if their mark-price systems differ.

A trader evaluating a market should therefore ask not only whether liquidity is deep, but also how the risk engine values the position when local and external prices diverge.

For builders, oracle choice is part of application security. A strategy that reads one convenient price feed without matching the protocol's actual risk price can misestimate liquidation or hedge exposure.

## Sources

- https://hyperliquid.gitbook.io/hyperliquid-docs/trading/robust-price-indices
- https://hyperliquid.gitbook.io/hyperliquid-docs/trading/funding
- https://hyperliquid.gitbook.io/hyperliquid-docs/trading/liquidations