Skip to content

Execution

Hyperliquid HIP-3 vs Native Perpetual Markets

Trace a named HIP-3 market from DEX metadata to collateral, action ID and margin settings, with a checked example and a practical validation sequence.

Two ivory ceramic drawers share a dark rail, with paper compartments and a lime marker in the open drawer
Illustration for execution; examples in this article are educational.

Hyperliquid HIP-3 markets are perpetuals deployed and operated by independent builders on HyperCore. Native, validator-operated perpetuals belong to the original DEX. They share trading infrastructure, while a HIP-3 builder defines its markets, collateral choice, oracle and risk settings. To compare them correctly, resolve the full market identifier, DEX context, collateral token and account mode before comparing balances or margin.

A familiar trading screen can hide several different contracts. The prefix in xyz:TSLA identifies a builder DEX; it belongs in the market's identity. A balance labeled USDC also needs an account context before it can be treated as support for that position.

This guide follows the official documentation's xyz:TSLA example and adds a hypothetical identifier and margin calculation. Sources were reopened on 29 October 2026. Documentation response examples below are teaching fixtures, not current market readings. A named market in this comparison does not establish KLINEO support for that market or its settings.

What HIP-3 changes relative to native perpetuals

HIP-3 gives a deployer responsibility for contract definitions and operation, including oracle inputs and leverage limits. Hyperliquid supplies the HyperCore trading stack. Each perp DEX has its own order books and deployer settings; shared infrastructure does not make every listed contract interchangeable. The deployer can call haltTrading to cancel all orders and settle positions at the current mark price. Include that settlement authority when reviewing a builder's operating rules. Hyperliquid's HIP-3 specification.

ComparisonNative, validator-operated perpsHIP-3 builder-deployed perps
Market contextOriginal perp DEXNamed builder DEX
API nameA name such as BTCFull name such as xyz:TSLA
Order asset identifierIndex in the original universeDEX offset plus index within that DEX
Contract reviewRead the native contract and price rulesRead that builder's contract and operating rules
Collateral reviewResolve the original DEX and account modeResolve the builder DEX's token and account mode

The asset name, collateral asset and referenced underlying answer different questions. A TSLA-named perpetual is a derivative contract; its symbol alone cannot establish ownership of a share, entitlement to dividends or how corporate actions are handled. The builder's specification must answer those questions. trade[XYZ] identifies its perpetual product as an HIP-3 deployment in its official overview.

For native crypto perps, Hyperliquid documents validator-published oracle prices based on a weighted median of exchange prices. It also distinguishes that oracle from the mark used in margining and liquidations. A builder's oracle methodology requires its own inspection; copying the native recipe into an equity-perp description would skip the central contract question. Native oracle and mark definitions.

Follow xyz:TSLA through the metadata

The official perpetual info reference accepts a dex field for metadata requests. Leaving it empty selects the original DEX. A request for the builder universe needs dex set to xyz. Looking for TSLA only in the default universe can therefore fail before any order validation begins.

In the reference's HIP-3 response example, xyz:TSLA is the second universe entry, so its zero-based index is 1. Its fields include szDecimals: 3, maxLeverage: 10, marginTableId: 10 and marginMode: "strictIsolated". The enclosing metadata has collateralToken: 0. These are example-response values, not a report of today's TSLA settings. Perpetual metadata requests and examples.

Resolve that collateral index against token metadata. The official spot example maps token index 0 to USDC. Match the token's explicit index field: a token identifier is a different object from a spot trading pair's index or an EVM contract address. Spot token metadata.

This creates a small but useful record: named DEX xyz, full coin xyz:TSLA, universe index 1, collateral token index 0, and the observed risk fields. Record the network and retrieval time alongside it. A remembered ticker and a screenshot of leverage cannot replace that record.

The size-decimal field also belongs to this resolved market. Preserve the source values as decimal strings and apply the instrument's rules after resolving its identity. The API decimal-precision walkthrough shows how an otherwise plausible calculation can silently change an intended quantity.

Calculate the action ID without losing the DEX

Hyperliquid's action API uses an integer asset ID for orders and cancels. Let d be the DEX index and i the index within its universe. Its documented HIP-3 rule is:

offset = 100000 + 10000 × d

asset = offset + i

For native perps, the action ID is simply the original universe index. Spot and outcome instruments use other namespaces. Mainnet and testnet mappings also differ. Official asset-ID rules.

Consider a hypothetical registry fixture in which xyz appears at DEX index 1. Combine that assumed registry with the documentation example's TSLA universe index of 1:

100000 + (10000 × 1) + 1

= 110001

Sending 1 would discard the builder context and select an index in the native namespace. Calculating 10000 + 1 = 10001 would apply the spot-pair rule instead. Neither number identifies the HIP-3 fixture. The value 110001 is conditional on the constructed registry; it is not a discovered current mainnet ID for TSLA.

The official Python SDK provides a useful implementation cross-check. At pinned version 0.23.0, Info creates builder offsets from perpDexs()[1:], starting at 110000, then adds each universe index. Its default configuration loads the original DEX; builder DEXs must be requested explicitly. Pinned SDK mapping implementation.

There is a separate wrapper check at that pin: meta accepts a DEX argument, while meta_and_asset_ctxs sends only the request type. The documented endpoint's capabilities cannot be inferred from that method's name. Inspect the installed client before assuming its convenience method queries the intended builder. Pinned metadata methods.

Collateral sharing depends on the account mode

The account mode changes the balance boundary. Current Hyperliquid documentation describes Manual/Standard mode as separate spot, perp and DEX balances, with cross margin scoped to each DEX. Unified account instead uses one balance per asset: its example explicitly shares USDC across validator-operated perps, XYZ perps and USDC spot activity. For unified account and portfolio margin, balances and holds are reported in spot clearinghouse state. Account abstraction modes.

Consequently, “both contracts use USDC” is insufficient evidence that they draw from the same available funds. In Standard mode, resolve the relevant DEX balance. In unified mode, reconcile the shared asset balance and its holds. Do not sum familiar-looking balances from several screens into a new collateral pool of your own.

Then check the market's margin restrictions. HIP-3 supports cross margin subject to eligibility rules; the sample's isolated setting cannot characterize every market. noCross permits only isolated margin. strictIsolated further disallows removing isolated margin from an open position. A unified balance does not override either restriction. HIP-3 cross-margin eligibility, margin-mode definitions, metadata field explanations.

The Hyperliquid cross-versus-isolated accounting guide develops the position ledger. For the broader distinction between position allocations and shared support, use the collateral-boundary comparison.

Read the risk configuration before applying leverage

Here is a hypothetical arithmetic check using the documentation fixture's margin-table ID 10. Hyperliquid's margin-tier reference says IDs below 50 represent a single tier whose maximum leverage equals the ID. It defines the maintenance rate as half the initial-margin rate at maximum leverage. Table 10 therefore implies a 5% maintenance rate for this illustration. Margin-table and maintenance rules.

Assume an illustrative linear position of 2 units at a 250-USDC mark, with a user leverage setting of 5×. Notional is 500 USDC. The basic initial-margin diagnostic is notional divided by the user's leverage, giving 100 USDC. Maintenance under the single-tier fixture is 25 USDC. The initial-margin relationship is described in the crypto perp contract specifications.

CheckCalculationIllustrative result
Position notional2 × 250500 USDC
Basic initial margin at chosen 5×500 ÷ 5100 USDC
Maintenance rate at table maximum 10×1 ÷ (2 × 10)5%
Maintenance at this mark500 × 5%25 USDC

The 5× user setting and 10× table maximum have different jobs. Substituting 5× into the maintenance-rate formula would give 10% and a mistaken 50-USDC result. This check omits fees, funding, other positions, open-order requirements and subsequent price changes. It supplies neither a liquidation price nor a withdrawable balance. Use fresh metadata and account evidence for those decisions.

Other deployer settings matter alongside margin: the API includes oracle updates, funding parameters and open-interest caps. Listing support for those actions describes available controls; it does not establish a particular builder's current values or prove how the matching engine is implemented. Record the specific configuration you can verify and leave unknown fields unresolved. Deployer action schema.

Fees deserve a fresh check too. The current fee reference includes configurable deployer fees and growth mode. A fixed claim that every HIP-3 trade always costs twice the native rate is inadequate. Compare the applicable user tier, market settings and discounts at the time of evaluation. Current fee mechanics.

Build a record that can reject the wrong market

Use the comparison as a validation sequence before funding or enabling an execution route:

  1. Resolve identity. Save the network, full coin name, DEX registry position and matching metadata entry. Reject a bare ticker when the intended contract is builder deployed.
  2. Resolve collateral. Join the collateral token index to token metadata and record the account mode. Read the balance source appropriate to that mode.
  3. Resolve authority. Separate the account whose balances are queried from the identity authorized to sign. The API-wallet versus master-address guide follows that distinction.
  4. Resolve the rules. Capture margin restrictions, table, size rules, fees and the builder's specification. Include how its oracle behaves during underlying-market closures, interruptions and corporate actions where relevant.
  5. Challenge the mapping. In an offline fixture, remove the DEX prefix, change the network or substitute a token index for the action ID. Each mismatch should stop the proposed route before signing.

A correct integer is useful only when it belongs to the intended contract and the evidence is fresh enough for the decision. Keep the full identity and collateral record attached to the proposal so a later reviewer can reconstruct exactly which market was evaluated.

Keep the context with the example.

Each worked example is illustrative, with its sources and assumptions in the article. Read our editorial standards for authorship, verification and corrections.