Hyperliquid is a blockchain built around financial markets. For a trader, its defining feature is a shared onchain record of orders, fills, positions, and collateral. An app can make those markets easier to use, but the app and the market are different parts of the transaction.
This distinction is useful even if you never write code. If two apps access the same underlying account and market, changing apps need not close the position. If one screen fails, the order may already exist on the underlying system. Understanding where the state lives helps you check what actually happened.
Two parts of the same network
HyperCore contains the native spot and perpetual order books. HyperEVM is the network’s general-purpose smart-contract environment. The first provides built-in trading operations; the second lets developers build applications and contracts around a broader set of actions.
Think of the interface as the place you compose an instruction, the market as the place orders meet, and the account as the record of the resulting assets and obligations. A frontend may add research, portfolio displays, or automation. Its usefulness does not change the contract’s payoff or the venue’s margin rules.
A spot purchase exchanges assets. A perp establishes price exposure supported by collateral. Buying $1,000 of linear perp exposure produces about $50 of gross profit from a 5% favorable price move. It does not place $1,000 of the referenced asset in the wallet. The first Perps 101 lesson works through that distinction.
What an accepted order means
Suppose you submit a buy limit for ten units at $100 while the best offer is $100.10. The order may be accepted and rest in the book, but no purchase has occurred. If four units later trade against it, the account has a four-unit position and a six-unit order remainder.
Hyperliquid’s order-book documentation describes price-time priority: better prices are served first, then earlier orders at a given price. It also explains that resting orders face margin checks again when they match. Acceptance therefore does not reserve an unconditional future fill regardless of later account changes.
After an uncertain submission, inspect the order and position records before repeating it. A lost connection can occur after acceptance. Sending the same economic instruction again can double the intended exposure if the first order was already working.
Where the collateral sits
The balance in a wallet, the balance available for spot trading, and the equity supporting a perp are different accounting concepts. Transfers and account modes determine when they can be used together. In cross margin, eligible positions share supporting equity; in isolated margin, capital is assigned to a particular position.
Builder-deployed markets add another distinction. The margin rules describe when positions across markets share collateral. Two trades appearing on the same screen may use different references or supporting balances. Read the account configuration instead of inferring it from the layout.
For a new market, identify quantity, entry price, current mark, unrealized P&L, funding, and available collateral. Those numbers explain the account more reliably than a single leverage label. A favorable open position can still be accompanied by working orders that would change its exposure.
From fills to the account balance
When closing, compare the actual fills with the intended quantity. Then reconcile price P&L, fees, funding, transfers, and the remaining position. Public records make this check possible, but they still have to be read correctly: a deposit is not a profit, and an open order is not a completed trade.
For the same reason, someone else’s visible account is only a bounded record. It can show a short position without showing a larger long held elsewhere. Transparency improves the evidence available to analysis; it does not remove the need for analysis.
If the interface loses a connection after submission, the order record—not the missing notification—determines whether another order is needed. This is the practical value of separating the app from the market it accesses.