HIP-3 wallet exposure needs a market identity beyond the ticker

Hyperliquid’s HIP-3 specification assigns market definition and operation to the deployer, including oracle selection, leverage limits and settlement where needed. It describes independent order books and deployer settings for each perpetual DEX. Those details are material when the same wallet trades across several venues within HyperCore.

A short label can hide a different instrument

The public Info API documentation identifies HIP-3 assets using a DEX prefix in the coin name. Our analysis: a tracker that drops this namespace risks combining positions or trade histories that refer to different instruments. An attractive display name is useful for navigation, but the underlying identity needs to remain available for verification.

For example, when comparing two wallets with exposure to a similar underlying asset, first establish the contract and venue for each position. Then check the observation time, collateral denomination and whether the exposure is long or short. A common underlying does not make every market interchangeable for liquidity or copying a trade.

What a position comparison should preserve

• The full API market identifier, including a DEX prefix where present.
• Position direction and size separately from a portfolio’s gross exposure.
• Collateral context, current observation time and the scope of the account view.
• A link to the market’s source specification when operational assumptions matter.

This is a reading framework for the current HIP-3 and API documentation, not a new listing announcement. Copying a wallet also requires the chosen market to be supported by the user’s actual execution workflow. A research page showing a position alone is not proof that it can be replicated on another account.