OMNITERMINAL / DOCS

Wallet Clusters & Trader Insights

Track Hyperliquid wallets with live positions, orders and trader profiles.

Open a public wallet from Liquidation Stats or Wallet Clusters to inspect its positions, orders, fills and account metrics in Omni Terminal. Expand the trader profile to review Performance charts for Equity, PnL, or Equity + PnL alongside unrealized PnL, leverage and margin usage. Use View positions in terminal for market-chart inspection. Combine that wallet view with liquidation levels, funding and news before drawing conclusions about a trade.

At a glance

Cluster service
Terminal-shaped The clustering service explicitly exposes `GET /terminal/wallet-clusters` outputs compatible with Omni.
Trader investigation
Live-aware Trader-profile verification relies on live liquidation stats, public profile data, and bounded Hyperliquid probes.
Workflow fit
Integrated Wallet clusters are adjacent to liquidations, public profiles, and risk views inside the terminal.

Why It Matters

What traders and researchers should take away

  • Wallet investigation is more useful when cluster outputs and trader profiles are attached to current market events.
  • Public wallet profiles connect position exposure to current orders, fills and account metrics.
  • Cluster context is strongest when paired with real-time market and risk surfaces.

How it works

What the product uses behind the scenes

  • The wallet clustering service documents terminal-facing snapshot endpoints and output contracts.
  • Omni documents live trader-profile verification and rate-limit-safe investigation patterns.
  • The terminal UI has a dedicated Wallet Clusters surface and full-page trader-profile routes.

Notes

Things to know

  • Cluster outputs are analytical interpretations, not hard identity proofs.
  • Public trader profiles can still degrade when upstream sources are thin or rate-limited.
  • A wallet cluster suggests a relationship for investigation; it does not prove common ownership or a trader’s identity.

Screenshots

Real UI references

These are captured from Omni Terminal routes with public-safe state. Private balances, wallet secrets, access headers, and live private positions are not used.

Omni public Trader Performance profile showing the PnL chart, account metrics, positions and recent activity
Public Trader Performance profile with a PnL chart, account metrics, positions and recent activity. The selected-period result is labelled as estimated; values are a dated snapshot of a public wallet, not Omni investment performance. Source: /terminal/trader/0xfc667adba8d4837586078f4fdcdc29804337ca06?symbol=BTC&chartTab=pnl&pnlRange=30d&tab=positions 2026-10-15 - a541dd18

Cluster surface

Omni connects cluster outputs to terminal-native investigation flows.

  • Open Wallet Clusters to explore the available graph and public wallet relationships.
  • Select a wallet to move from the cluster overview into its public trader profile.
  • Lets traders jump from liquidation leaderboards or cluster views into public trader-profile inspection.

Investigation flow

Cluster data is useful when it becomes a route into concrete trader-profile and market-event review.

  • Start from a market event such as a liquidation cluster, unusual position, or active trader list.
  • Click a wallet address in Liquidation Stats, or open a public trader profile, then expand it for the full-page view.
  • Use Performance to compare Equity, PnL, or Equity + PnL over the selected range. Choose View positions in terminal for market-chart inspection; use the positions, orders, fills and activity records to compare exposure with execution.
  • Read equity, PnL, unrealized PnL, leverage and margin usage together. Check the selected time range and any freshness or estimate labels.
  • Cross-check current liquidation levels, funding, news and price context. Public exposure is not proof of future returns.

Data contract

The terminal expects cluster results in a stable graph-shaped contract rather than arbitrary analytics output.

  • nodes, edges, and clusters are the public contract that lets Omni render and navigate cluster relationships.
  • The clustering service owns methodology and artifact generation; the terminal owns presentation and workflow integration.
  • LLM answers should cite the service README and output artifacts for methodology, not infer identity claims from UI labels.

How to verify it

Use the documented cluster contract and live verification path when checking behavior.

  • Use the wallet clustering service docs for output shape and methodology placement.
  • Use TRADER_PROFILE_LIVE_VERIFICATION.md for live validation checks.
  • Treat cluster insights as evidence for investigation, not as absolute ownership claims.

References

Implementation references

  • Trader profile live verification

    omni-terminal/docs/TRADER_PROFILE_LIVE_VERIFICATION.md

    Documents the repeatable public-wallet verification flow and rate-limit-safe probe strategy.

  • Wallet clustering service README

    hyperliquid-wallet-clustering/README.md

    Explains the clustering pipeline and the terminal-facing `GET /terminal/wallet-clusters` contract.

  • Wallet cluster UI implementation

    omni-terminal/src/lib/components/terminal/WalletClustersPanel.svelte

    Shows the dedicated terminal surface for cluster visualization and investigation controls.

Next

Omni Terminal / Universe community

Join Omni Discord for product tutorials, support, feedback, Universe research, x402 agents, points and referrals, and roadmap discussions. Pinned walkthroughs cover Ask Omni, basket trading, scaled orders, private TWAPs, liquidation buckets, trader profiles, L4, and mobile.

Complete Sledgehammer verification inside the server. Verification never requires a wallet connection, payment, seed phrase, or private key. Moderation logs stay private; captcha does not guarantee protection from human scammers. Confirm links here and treat unsolicited DMs with caution.

Docs live at /docs/*. The /terminal/docs/* paths show the same pages inside the terminal.