# Accessing Stratium

Stratium operates three interfaces on Hyperliquid mainnet.

### Staking: [app.stratium.xyz](http://app.stratium.xyz)

Deposit HYPE, receive srHYPE, manage withdrawals, and track points at [app.stratium.xyz](http://app.stratium.xyz). This is the Stratium interface for all staking operations.

### Perpetuals: [trade.stratium.xyz](http://trade.stratium.xyz)

Trade perpetual futures through Stratium's Builder Code at [trade.stratium.xyz](http://trade.stratium.xyz). Stratium runs a unified perpetuals interface on Hyperliquid's Builder Code infrastructure through the terminal.

Your existing Hyperliquid USDH balance works across all markets. Same orderbook, same matching engine, same margin system as native Hyperliquid perps.

### Binary Options: [markets.stratium.xyz](http://markets.stratium.xyz)

Trade binary options through HIP-4 at [markets.stratium.xyz](http://markets.stratium.xyz). Stratium was one of the launch frontends when Hyperliquid activated HIP-4 on mainnet on May 2, 2026.

HIP-4 markets are fully collateralized outcome contracts denominated in USDH. Positions settle to 0 or 1 at expiry. Zero fees to open positions. No leverage. No liquidation.

The interface includes a real-time orderbook, price charts, position and P\&L tracking, and a leaderboard.

### One Account

All three products run on Hyperliquid mainnet. Spot, perpetuals, and binary options share the same account. No separate deposits, no bridging, no fragmentation.


---

# Agent Instructions: 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:

```
GET https://docs.stratium.xyz/trading-hip-3-markets/accessing-stratium.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.