> For the complete documentation index, see [llms.txt](https://liquidiction.gitbook.io/liquidiction-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://liquidiction.gitbook.io/liquidiction-docs/readme.md).

# Welcome to Liquidiction

Liquidiction is the prediction market frontend for HIP-4 on Hyperliquid.

Trade binary and multi-outcome prediction markets directly on HyperCore L1 with full on-chain settlement, non-custodial execution, and real-time data.

## What is Liquidiction?

Liquidiction provides a purpose-built trading interface for Hyperliquid's native prediction market infrastructure (HIP-4). While Hyperliquid's own UI supports outcome trading, Liquidiction focuses entirely on the prediction market experience with features like:

* **Trading**: Market, limit, ladder, and TWAP orders
* **Real-time charts**: Price, volume, and multi-outcome visualization
* **Portfolio**: Live positions, PnL calendars, trade history
* **Explorer**: Sortable market data with depth, volume, and open interest
* **Leaderboard**: Top traders ranked by PnL, volume, and win rate
* **Analytics**: Aggregate volume charts, unique traders, and cross-platform market share (Polymarket vs Kalshi vs HIP-4)

## Why Hyperliquid?

Prediction markets on Hyperliquid are fundamentally different from platforms like Polymarket:

|                    | Liquidiction (HIP-4)     | Polymarket              |
| ------------------ | ------------------------ | ----------------------- |
| **Execution**      | On-chain L1 orderbook    | Off-chain matching      |
| **Custody**        | Non-custodial, always    | Deposits to contract    |
| **Settlement**     | Native HyperCore         | Smart contract / oracle |
| **Speed**          | Sub-second block times   | Variable                |
| **Fee model**      | Standard spot fees       | Platform fees           |
| **Infrastructure** | Same as HYPE spot/perps  | Separate system         |
| **Margin**         | Unified account (future) | Isolated per market     |

HIP-4 outcomes trade on the same spot orderbook infrastructure that powers all of Hyperliquid's spot trading. This means the same speed, the same liquidity engine, and the same security model.

## Capital Efficiency

Research shows 100,693 wallets are active on both Polymarket and Hyperliquid, generating $6.1B in PM volume. These traders currently split their capital across platforms. HIP-4's unified margin account means prediction positions can eventually share collateral with perps and spot, reducing capital requirements by 30-60%.

## Current Status

Liquidiction is live on **Hyperliquid testnet**. All markets, trades, and positions use testnet USDH. Mainnet launch will follow Hyperliquid's HIP-4 mainnet deployment.

Grab some USDH and help us battle-test before mainnet.

## Quick Links

* [Getting Started](/liquidiction-docs/getting-started/connect-wallet.md)
* [How HIP-4 Works](/liquidiction-docs/hip-4-prediction-markets/how-it-works.md)
* [Trading Guide](/liquidiction-docs/trading/buying-and-selling.md)
* [Order Types](/liquidiction-docs/trading/order-types.md)
* [FAQ](/liquidiction-docs/faq/common-questions.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://liquidiction.gitbook.io/liquidiction-docs/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.