Data source
LiquidScope keeps a persistent ledger collected about once per minute from the exchange’s public information API (Hyperliquid today), by wallet address and without any key or signature, with per-asset strategy attribution. Placeholder values never fill gaps.
Supported account scope
Live totals cover native USDC perpetuals in standard/manual mode (abstraction API: disabled or default) and the Unified Account mode, where the venue's USDC account value is the equity and daily identity checks flag any effect of spot trades or other DEXs. Portfolio margin and other modes withhold combined equity, margin and withdrawable totals. Spot token balances are shown separately without being added together as dollars. HIP-3 markets, vaults, staking, HyperEVM and lending are outside the aggregate.
Multiple strategies
Each saved strategy uses one distinct account or subaccount address. Duplicate addresses are rejected. Labels are user-declared. API agent wallets are rejected because they sign for a trading account. Positions are netted at account and market level; shared-account attribution needs AlphaNet order and fill identifiers.
Position figures
Positions and account totals come from the clearinghouse state. Mark prices come from market context, with position value divided by absolute size as a fallback. Gross exposure is the sum of absolute notionals. Net exposure offsets long and short notionals. Margin usage is margin used divided by supported perps equity. Position ROE is the value returned by the exchange.
Liquidation distance
For a long: (mark − liquidation price) / mark. For a short: (liquidation price − mark) / mark. It is a directional estimate, not a stress test. Missing liquidation values remain unavailable.
Costs and performance
Trade fees include builder fees; they are not added a second time. Rebates retain their sign. Funding is the actual signed settlement returned by the API. Fee tokens are preserved in activity rows. Only USDC fees enter the displayed fee subtotal.
The server ledger reconciles equity daily to initial deposits + realized P&L + unrealized P&L − trading fees + funding.
Refresh and history
The server collects every wallet about once per minute and keeps the full ledger; this page reloads its data every 60 seconds while visible and after each collection.
Server-side collection and ledger
Accounts enabled under Server monitoring are collected by a scheduled server task about once per minute, independent of any open browser. The server keeps minute snapshots and an immutable, deduplicated ledger of financial events (fills, settled funding, deposits, withdrawals and transfers) with the venue's exact decimal strings and UTC timestamps, plus the raw source records as evidence. Historical backfill is bounded by the venue's documented response caps and retention; irrecoverable ranges are recorded as explicit gaps, never silently skipped. Each API response carries its own source status: last successful sync, coverage, backfill state, gaps and the latest reconciliation result.
Reconciliation and withheld metrics
The daily control identity is: period P&L = ending equity − starting equity − net external contributions. Deposits are not profit; withdrawals are not losses; transfers between two tracked accounts are neutralized in consolidated figures only when both legs are matched by evidence. Cash-flow-adjusted returns are computed with a time-weighted method only when snapshots bracket every flow and no gaps or unclassified events overlap the period — otherwise the figure is withheld with the reason. Sharpe, drawdown, win rate, lifetime P&L and annualized returns are not displayed in this release because the evidence they require is not yet established.
Retention and aggregation
Minute snapshots are kept for 90 days. Before deletion they are aggregated into hourly equity records which are kept indefinitely, so charts and period calculations never lose their underlying evidence. Financial events are never deleted by retention. After downsampling, calculations that need minute resolution older than 90 days (for example flow-bracketing at minute precision) are no longer supported and are withheld rather than approximated.
Missing data
Errors and unsupported modes are shown explicitly. A missing account invalidates combined equity totals. Loaded positions and events from other accounts remain visible with a warning; their presence does not establish complete portfolio coverage. Refreshes are independent requests, not an atomic exchange snapshot.