Two contracts can display the same company name and still be different investments. One may reference a share price, another an implied company valuation. They may accept different collateral, charge different funding, or follow different rules when the underlying market closes.
HIP-3 makes this distinction particularly important. It lets builders deploy perpetual markets using Hyperliquid’s trading infrastructure. The infrastructure matches and accounts for trades; the builder defines important features of the market being traded. Evaluating one therefore starts with the contract, not just the platform’s name.
What the builder defines
The HIP-3 specification describes the deployer’s role in market settings, reference prices, and settlement actions. An oracle is the mechanism supplying the reference information used by those rules. It does not itself guarantee that the information is timely, economically appropriate, or comparable with another contract’s reference.
For an equity index, a cash-index reference and a particular futures contract need not have the same price. Futures can reflect financing, expected dividends, and a different trading session. If a commodity contract refers to one delivery month, its price can differ from another month because the underlying supply and storage economics differ. A gap between two tickers is not automatically an arbitrage.
Write the unit in ordinary language: one unit of this contract gives exposure to a specified price or valuation, under a named methodology. For private-company exposure, establish whether the quote measures billions of company value or something else. A synthetic price contract does not create the rights of a shareholder.
The reference must work when the market is awkward
The most informative contract provisions often concern interruptions. What updates the reference while the stock exchange is closed? Which source is used if the preferred feed fails? How are corporate actions, an IPO, or a discontinued market treated? These rules decide whether a familiar-looking price continues to mean what you thought it meant.
Suppose a stock closes at $100 and news arrives over the weekend. A perp trades at $105. If the cash market reopens at $102, a long entered at $105 loses $3 per unit when the perp converges to $102, even though the stock rose from its prior close. The relevant comparison is your executable entry with the contract’s later price.
A hedge can still need cash on both sides
Now buy one contract and short a related one. Their long-run economic exposures may offset, but a temporary divergence can produce a margin demand on one side. Profit on the other side only helps if the account rules let it support the losing position in time.
Hyperliquid’s margin documentation distinguishes account modes and collateral sharing. Markets shown beside one another in an interface need not share the same margin pool. Compare the collateral asset and account arrangement before treating two positions as one capital requirement.
Then estimate the round trip at your size: execution fees, spread, funding, and any interface or deployer charge. A cheaper advertised fee may be outweighed by a less liquid book or a reference that does not express your intended view.
A deployer’s stake is not your insurance policy
HIP-3 requires deployer stake and provides a slashing process for specified misconduct. The specification states that slashed stake is burned, rather than distributed to affected users. That is an incentive mechanism for operators, not a promise to reimburse a trading loss. The deployer can also use a protocol action that cancels orders and settles positions at the current mark, subject to the governing rules.
Shared infrastructure can make two markets equally easy to access without making their prices comparable. Different reference methods, collateral pools, or termination rules can justify a persistent gap. That difference has to be understood before the gap can be treated as a trade.