Positions
Phase 1: paste an address, read-only. Wallet connect lands in Phase 2.Paste an address to index its positions. Nothing is stored beyond a ten-minute cache of what the public API already shows.
open positionsfrom the venue, right now
| coin | side | size | entry | notional | lev | liq | unrealised | funding since open |
|---|
no open perp positions
recordclosed round-trips, counted
| structure | trips | wins | net |
|---|
in and outentries and exits on the coin's own candles
a chart appears once a wallet with trips is read
▲ in (long) / ▼ in (short)out with net P&Lfaint line = the hold
round-tripsnewest first
| coin | side | opened | hold | entry → exit | peak size | entry | structure | gross | fees | funding | net | exit |
|---|
no round-trips in the fills read
spota lower bound: transfers are not fills
| token | qty | cost | buys | sells | realised |
|---|
no spot fills
Round-trips are rebuilt by code from the wallet's own fills on Hyperliquid's public API (entry and exit VWAP, fees, funding, hold); leverage and margin mode are known for open positions only. Spot is a lower bound: transfers are not fills. A terminal user's address is never listed and never appears on a public page.