By ChartNothing Product Team · Updated · 7 min read
A technical overview of the read-only Hyperliquid Account Suite, the data it requests, the dashboard it produces, and the limits ChartNothing keeps around permissions, history, and freshness.
What the Account Suite actually does
The Account Suite begins with a public EVM-style wallet address. ChartNothing sends server-side requests to Hyperliquid's public info endpoint for the current clearinghouse state and portfolio history, then combines the useful fields into one app-ready feed. The flow never asks for a private key, exchange password, API trading key, or transaction signature.
Current account state and historical performance are deliberately treated as different data. Equity, open profit and loss, withdrawable value, margin use, leverage, entry price, and liquidation price describe the account now. Portfolio history supplies the time series. If history is unavailable, the dashboard says so instead of drawing a fabricated trend from a single snapshot.
- One wallet and one logical connector refresh.
- Required current-state request plus optional historical portfolio response.
- One normalized feed for web, iPhone widget, and watch surfaces.
- No order placement, account mutation, or custody permission.
How we choose the first screen
A useful account pulse should answer three questions quickly: what is the account worth, how much open profit or loss exists, and where is the immediate risk? That is why equity and open PnL lead the page, while notional exposure stays secondary. Large notional can be important, but it is not a performance chart and it should not dominate a one-position account.
For a single open position, ChartNothing prefers a risk summary and position table over a one-bar chart. The table preserves entry, mark, liquidation, leverage, size, margin, PnL, and return-on-equity context. With multiple positions, comparisons become useful and the template may add bounded exposure or PnL bars.
Freshness, credits, and honest expectations
The browser can run a manual refresh while scheduled plans spend a bounded refresh budget. We describe this as best-effort freshness rather than guaranteed real time because upstream availability, queue processing, plan limits, and native platform scheduling all affect when a surface updates.
Each logical Account Suite refresh is accounted once even though the backend makes two source requests. Run history records success, failure, timing, and credit state without turning ChartNothing into an unbounded store of exchange history. The latest normalized feed remains the device-facing product state.
- Free is suitable for demos, manual checks, and low-frequency use.
- Pro unlocks supported faster schedules, more runs, saved feeds, and native freshness budgets.
- A stale timestamp remains visible so a quiet feed is not mistaken for a live stream.
Security and product boundaries
A public wallet can still reveal financially sensitive activity. Saved connectors, normalized feeds, templates, and app sync remain owner-scoped behind Cognito. A scoped GET share is optional and should be treated like a revocable bearer credential; it is a developer handoff, not the default native sign-in path.
ChartNothing is not affiliated with Hyperliquid and does not provide financial advice. Values come from the selected public account and upstream response at the captured time. Users should verify critical account and liquidation information in the exchange interface before acting.
Frequently asked questions
Does ChartNothing need my Hyperliquid private key?
No. The Account Suite uses a public wallet and public read-only info requests. Never enter a private key, seed phrase, exchange password, or trading credential.
Why can account history be unavailable?
The current-state request and portfolio-history request are separate. A valid current snapshot can exist when the selected portfolio response has no usable timestamped history. The UI reports that state explicitly.
Is the widget guaranteed to update every five minutes?
No. Eligible plans can request a budgeted five-minute schedule where supported, but upstream, queue, device, and WidgetKit behavior prevent a hard real-time guarantee.