Omni Terminal

Wallet Clusters & Trader Insights

Investigation workflows for wallet behavior, cluster context, and public trader profiles.

Omni Terminal pairs wallet cluster outputs with trader-profile workflows so researchers and traders can move from market events to wallet-level investigation without leaving the terminal context.

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.
  • Worst-trader and public-profile workflows help turn liquidation events into investigation starting points.
  • 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.
  • Investigation workflows should prefer bounded probes and not create extra 429 noise during debugging.

Cluster surface

Omni connects cluster outputs to terminal-native investigation flows.

  • Shows wallet cluster panels and trader-profile entry points inside the terminal.
  • Uses a clustering service that adapts canonical snapshots into the nodes / edges / clusters contract expected by Omni.
  • 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.
  • Open the related trader profile or wallet cluster view to inspect public wallet behavior.
  • Cross-check the investigation with current liquidation stats, funding, news, and price context before drawing conclusions.

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