MAINNEAT

What are HIP-3 markets?

Understand builder-deployed perpetuals, venue names and separate market identities.

By Mainneat / Reviewed / Independent documentation

What does HIP-3 enable?

HIP-3 lets deployers define and operate perpetual markets on HyperCore. Responsibilities include contract specifications, the oracle definition and market settings. These markets use HyperCore order books.

Why does a symbol contain a colon?

A name such as xyz:ASSET identifies a market on the xyz perpetual venue. Preserve the complete API name when inspecting a book or account. A similar ticker on another venue is a different market.

Is a deployer the same as a trade builder?

No. A deployer operates the market. A builder can receive a fee for routing an eligible order. The same execution can have both labels, one or neither. The terminal keeps them in separate columns.

Why show balances by venue?

A single address can have collateral and positions in different perpetual venues. The profile preserves the API venue breakdown instead of assuming that every displayed balance is one freely interchangeable balance. Account mode also matters.

Do native perps and HIP-3 always use identical parameters?

No. Check the actual market specifications, collateral denomination, oracle and deployer settings. Sharing infrastructure does not mean that two contracts with similar names have identical economics.

Sources and methodology

Protocol details refer to the official sources below. Terminal behavior describes this site's implementation and its stated coverage limits. Examples are illustrative.

Open the related terminal view

Related guides