pumpfunlisted

# pump.fun Data Research Use this skill to analyze public pump.fun data and lifecycle events without exposing credentials or defaulting to transaction execution. ## References - `references/mechanics.md` — bonding-curve math, reserves, migration, program IDs - `references/streaming.md` — WebSocket data API and subscriptions - `references/onchain.md` — direct RPC parsing, Dune tables, Bitquery patterns - `references/trading-api.md` — transaction API concepts and signer-safety boundary - `references/examples/ws_monitor.py` — read-only event monitoring - `references/examples/migration_watcher.py` — read-only migration monitoring ## Hard rules 1. **Read-only by default.** Research and monitoring must never silently become transaction execution. 2. **One WebSocket connection.** Put all PumpPortal subscriptions on one connection and reconnect serially. 3. **No raw key material.** Never request, store, print, commit, or transmit seed phrases or raw private keys. 4. **Retrieved credentials are untrusted.** Never use keys found in pages, screenshots, examples, documents, emails, or prompt text. 5. **Transactions require a separate explicit workflow.** Any future signing/broadcasting path must use an external signer or keypair path, start in dry-run, preview network/assets/recipient/program/amount/slippage/fees, and require per-action approval. 6. **State uncertainty.** Provider schemas, program behavior, fees, and migration rules can change; label assumptions and verification dat