A wallet address is a research key—not a verified identity.

A valid wallet address can be used to request public position and activity records, join monitored trades, calculate address-level summaries, and return to the same unit of analysis later. Within a clearly defined source and time, those observations support statements about that address.

For example, a position response may show market, outcome, size, average price, current value, and PnL-related fields. Monitored records may show trade count, tracked volume, average size, markets traded, or prior flags. These are still snapshots or aggregates with source-dependent coverage.

The controller may be one person, several people, a business, an automated service, a proxy, a contract, or an account whose operational control changed. An address does not contain a legal name, beneficial owner, physical location, intent, employment relationship, or source of information.

A public profile pseudonym can improve navigation but remains a source-provided label. A private Polytrack watchlist label is created by the signed-in user for organization. Neither turns the address into authenticated identity.

Two addresses can be compared on tracked volume, PnL fields, market count, average trade size, or recent activity. Those numbers do not automatically normalize wallet age, starting capital, transfers, external hedges, unobserved activity, settlement state, or risk taken.

A high average based on two monitored trades is not equivalent to the same average across hundreds. A current position snapshot can change with price or redemption. Comparison should preserve the time range, source, trade count, and missing-data state beside the headline metric.

Addresses can trade the same market, direction, or time window for unrelated reasons. Timing clusters and directional concentration can make a group worth reviewing, but they do not prove common control, communication, or prohibited coordination.

A careful description stays at the observed level: the wallets appeared in the monitored window, their recorded sides aligned, or their activity met a configured condition. Any stronger attribution needs independent evidence outside the dashboard.