Classification labels
| Label | Meaning |
|---|---|
| DirectUser | The Pump.fun event user appears to be the trader wallet and no routed context is detected. |
| RoutedUserSigner | A route program is involved, but the actual user signer can still be attributed. |
| RoutedUserPda | A routed path appears to use a PDA or program-owned account while logs provide a probable real user wallet. |
| RoutedUnknown | A router is detected but the backend cannot safely identify the real user wallet. |
Signals used
- Invocation depth and parent program ID show whether Pump.fun was called through another program.
- Top-level program IDs reveal same-transaction route or sidecar programs.
- Logged pubkeys can hint at real user wallets when they repeat and are not known Pump.fun fields.
- Core programs such as system, token, associated token and memo are ignored as route candidates.
Limitations
Some routers intentionally hide the end user. In those cases PumpScan tracks the route program and avoids inventing a wallet attribution.