Terminology and feature boundary
Entry and exit are Pumpscan behavioral labels, not Solana account types and not pump.fun instruction names. The underlying identity is the attributed trader public key of a core TradeEvent or resolved PumpSwap trade leg, including routed trades when Pumpscan can resolve the canonical user. Conversion legs and unresolved AMM rows do not count.
| Term | Meaning in Pumpscan |
|---|---|
| Entry wallet | A canonical Pump trader address whose retained core and resolved PumpSwap trade activity is at least 95% buy-side by event count. |
| Exit wallet | A canonical Pump trader address whose retained core and resolved PumpSwap trade activity is at least 95% sell-side by event count. |
| Mapped pair | A reciprocal relation between one entry wallet and one exit wallet, supported by exact same-mint token-flow matches in retained data. |
| Copy-trading review | A reconstruction of observed execution quality and position outcomes. It is not a claim that another wallet followed or copied the address. |
Directional wallet classification
For each retained trader wallet, Pumpscan compares buy-side and sell-side core and resolved PumpSwap trade counts. A wallet is an entry candidate when it has at least one buy and buys represent 95% or more of its retained directional trades. It is an exit candidate under the symmetric sell rule. For example, 95 buys and 5 sells qualifies as entry; 94 buys and 6 sells does not.
Classification is retention-bound. It can change as new trades arrive or older events expire, and it describes only the indexed core and resolved AMM trade activity attributed to that address.
Cross-wallet token-flow correlation
The detector correlates observable token flow; it does not inspect private keys, off-chain agreements, or legal ownership. A valid match may reflect delegated token authority, co-signed execution, custody infrastructure, purchased tokens delivered to the exit wallet's associated token account (ATA), or a direct token transfer between trading phases.
| Stage | Rule |
|---|---|
| Read | Load each candidate wallet's retained user-indexed event history; the production job does not call Solana RPC. |
| Project | Keep Pump core TradeEvent rows and resolved PumpSwap amm_leg=trade rows attributed to that wallet; exclude route/unresolved legs. Aggregate entry buys and exit sells by SPL-token mint in raw token base units. |
| Match | Require the entry-buy total and exit-sell total to be exactly equal for the same mint, and require the latest exit sell not to precede the earliest entry buy. |
| Correlate | Count distinct time-consistent mint matches for each directional entry/exit wallet pair. |
| Publish | Write the same grade in both directions so an entry wallet lists exit counterparts and an exit wallet lists entry counterparts. |
Mapping grades
Grades summarize the number of exact, time-consistent mint matches; they are not calibrated probabilities. Even grade 100 remains a token-flow classification rather than proof of common ownership. Each relation index is capped at ten counterpart wallets and expires with its parent retained account record.
| Matched mints | Stored grade | UI label |
|---|---|---|
| 1 | 85 | Possible |
| 2 | 95 | Highly likely |
| 3 or more | 100 | Bound |
Pump protocol scope
A resolved Pump AMM trade leg uses the same raw base-token units as a curve trade, so a curve buy can match an AMM sell of the same mint. Pumpscan only sees AMM swaps that reach its Pump core subscription, mostly Pump multi-hop routes; a plain wrapped-SOL pool exit that never mentions Pump core is not retained and cannot be linked.
| Included | Excluded from Stage 1 |
|---|---|
| Pump core bonding-curve TradeEvent buys and sells, and resolved Pump AMM (PumpSwap) trade legs retained from the Pump stream | Pump AMM route legs and AMM rows whose pool or trader is not proven |
| Exact aggregate token_amount equality in mint base units | Near-amount matches, tolerance bands, and several exit wallets jointly satisfying one entry |
| Retained events with canonical trader attribution | Expired history, unsupported venues, and RPC recovery of missing event payloads |
How mapped trades are used
When the viewed wallet is currently classified as entry or exit, the account workspace loads every counterpart returned by the mapping API, including grades 85, 95, and 100. It retains counterpart trades only for mints also traded by the viewed wallet, merges those rows with the wallet's own retained trades, and reruns position reconstruction.
The merged history feeds account summary metrics and charts, the Events and Positions workspaces, and the browser-side Copy Scores review. The grade describes the original pair-level evidence; the current frontend does not re-prove exact token flow on every merged mint.
Following mapped activity means observing and reconstructing cached trades. Pumpscan does not submit copy trades, subscribe a user to future wallet transactions, or infer a causal leader/follower relationship from timing alone. The scheduled backend Today Copy Score remains a separate single-wallet metric; mapped multi-wallet backend scoring is not currently published.
API and freshness
| Interface | Behavior |
|---|---|
| GET /v1/accounts/:account/mapped-accounts | Returns the requested wallet plus up to ten mapped account/grade rows, ordered by grade descending and address ascending within a grade. |
| Reciprocal storage | A newly accepted pair is written atomically to both wallets' bounded relation indexes when both parent account records are live and have capacity. |
| Retention | The mapping job uses a fixed retained-event snapshot. Stored relations are not continuously re-graded and expire with their parent account cache entries. |
Interpretation limits
- Do not present a mapped pair as proof that two addresses belong to the same person or entity.
- Do not describe Entry Account or Exit Account as a permanent wallet identity; each label is derived from the retained event window.
- Do not describe the feature as leader/follower detection, copy-trade execution, or investment advice.
- Do not imply complete coverage after bonding-curve migration: only AMM swaps delivered by the Pump core stream are retained.
- Treat combined P&L and position metrics as retained-event reconstruction, not complete wallet accounting.