PLATFORM GUIDE

Wallet tracking

Current availability: production wallet-event ingestion is unconfigured. The management and reader interfaces exist, but a saved wallet does not establish a working live activity feed. Public spectating is a separate account-read capability.

Wallet feed

Sign in to open the Wallets management surface. The full page separates LIVE FEED from TRACKED WALLETS. In the terminal widget, Feed shows available received events and Manage shows tracked accounts. The Feed count reflects events remaining after filters, rather than all raw received rows.

An empty or reconnecting feed cannot prove that a tracked wallet is inactive. Resolve provider availability before relying on the feed for monitoring.

Tracked wallets

With a VertigoPro session:

  1. Open WALLETS → TRACKED WALLETS, or select Manage in the Wallets widget.
  2. Choose Add and provide the public address and label requested by the form.
  3. Save and confirm the entry appears in your managed list.
  4. Check the feed’s availability separately.

Search managed entries by name or address. Limits are shown by the management counter and can depend on account entitlement; this documentation does not promise a universal wallet allowance. Import and the export controls manage lists, not signing credentials.

Wallet groups

Use the group controls to organise tracked addresses and change membership. Groups affect monitoring scope and are carried with supported signed-in preferences. Renaming or removing a tracked entry does not alter the wallet on its venue.

Before bulk removal, check the selected entries and preserve an exported list if you need to restore the grouping later.

Curated wallets

Curated entries are starting points for a watch list. They are not evidence of audited profitability or a guarantee of future performance. The current deployment does not establish complete wallet-performance ingestion merely because a curated address can be selected.

Trade and transfer filters

Settings → Wallets includes Show trades, Show transfers, Minimum trade size and Minimum transfer size. The feed also offers search and market/group filters. Use the correct venue instrument when the same symbol exists on both venues.

Filtering changes what is visible; it cannot repair missing events or prove that excluded activity did not occur.

TWAP activity

Show every TWAP fill expands available TWAP activity into individual execution slices. With it off, the reader can present aggregated activity. This is a display preference over received events, not a guarantee that every venue TWAP or fill is captured.

Wallet-event details

Expand an available event to inspect its decision, size and associated execution context. Trade and transfer events have different meanings; a transfer is not an entry or exit signal. Where an explorer link is available, it belongs to the event’s originating venue. The interface must not substitute a Hyperliquid explorer link for a Lighter event.

Spectate a public account

Use SPECTATE to inspect supported public account data without granting control of that wallet. Tracking a wallet and spectating it are independent actions. Account data explains venue-specific visibility and the required identifiers.

Select a market action on an event only when its instrument can be resolved. Venue and market identity should travel with the event. Confirm the resulting chart context before comparing the event with current prices; unresolved events should not be treated as a same-symbol trade on another venue.

Alerts

Wallet popup and sound preferences are separate controls in settings. They require eligible live events from a working provider. Sign-in, saved addresses and enabled notification switches alone do not provide monitored delivery.

Data coverage and limitations

No complete production wallet history, latency commitment, copy-trading service or calculated smart-money ranking is established by the current deployment. Historical or retained rows may remain visible independently of source health. Use venue records for authoritative account activity and treat monitoring gaps as unknown coverage.