Open source · data · integration notes

Build on
HIP-4.

Use purpose-built TypeScript utilities, shadcn-compatible outcome components, and an indexed historical data layer—while keeping Hyperliquid's live API as the source of truth for execution.

Toolchain

From raw identifiers to a usable product.

npm

@purrdict/hip4

Zero-runtime-dependency TypeScript utilities for discovery, outcome mapping, tick sizes, and order payloads.

React

@purrdict/hip4-ui

shadcn-compatible market cards, order books, trade forms, positions, and settlement states.

Data API

mute.sh

Enriched HIP-4 fills, market metadata, historical aggregates, SSE, gRPC, and webhook delivery.

Source

Purrdict on GitHub

Inspect the SDK and UI repositories, tests, examples, and release history.

Integration rules worth keeping.

  1. Preserve identifier type and context

    Do not silently collapse #N API coins, +N token names, and integer asset IDs.

  2. Derive ticks before sending orders

    Outcome prices are bounded, but allowed decimal precision still depends on the asset's tick rules.

  3. Separate discovery from execution

    An archive can recover expired context; Hyperliquid's current API remains authoritative for a live order.

  4. Render full resolution metadata

    Question, source, cutoff, tie, cancellation, and void semantics belong in the user interface.