Hyperliquid HIP-3 DEX Bot Integration: Asset IDs and Multi-DEX State

Engineering requirements for bots that trade builder-deployed Hyperliquid perps across multiple HIP-3 DEXs.

Do not hard-code familiar asset indexes

Builder-deployed perp identifiers incorporate the perp DEX index and position in metadata. Resolve identifiers from authoritative metadata at startup and version cached mappings.

Carry the DEX dimension everywhere

Orders, positions, mids, risk limits and PnL need an explicit DEX identity. A coin symbol alone is not a safe database key across multiple venues.

Normalize streaming state

Subscribe to the relevant DEX feeds and reconcile snapshots before execution. Measure stale state independently for each market and suspend only the affected routing path.

Aggregate risk deliberately

Set per-market, per-DEX and portfolio limits. Cross-market correlation and shared collateral can turn apparently isolated strategies into one liquidation domain.

Commission a multi-DEX bot

TierZero builds Hyperliquid market makers and custom perps systems. Send target DEXs via contact.

Discuss your integration

Share the current stack, API surface, production constraints and target launch date through the TierZero contact page.