Pix-Vu Operations Desk08/06/26, 18:00

Gates / exits / readiness / deployment cycle

Runbook

Control doctrine

Pump.fun Bot Tracker

This page holds the static rules: what the bot is allowed to select, how it exits, what needs to be ready before live execution, and the step-by-step deployment cycle.

GateFilters and scan rules
Scan source
PumpDev free WebSocket new-token firehose
Endpoint
wss://pumpdev.io/ws
Allowed intent
30s_observed_adoption
Observation
30 second observed adoption
Social
twitter / instagram
Followers
not gated
Feed cadence
event-driven WebSocket; no fixed polling interval for token events

Required candidate profile

meme/AI/tech candidate that passes the 30-second observation model with a Twitter/X or Instagram source and at least 10 SOL net inflow.

  • Categories: meme, ai, tech
  • Remix: image reuse, social reuse, description remix
  • Blocked: original, dead_reference, active_copy, unknown, bundle, snipe, multi_deploy, auto_sell
  • One-position rule: choose one eligible row, then lock the bot until the deployment cycle exits
ExitExit policy and millisecond telemetry
No hit
5s then 100%
Hit staging
25% x 4
Executor sells
25% / 33.333333% / 50% / 100%
Staged window
30s
Leave dust
no
Target max
500 ms
Feed RTT
recorded by PumpDev WebSocket client
Hit detection
recorded by deployment cycle
Deploy RTT
recorded by selected executor
Sell RTT
recorded per exit stage
Telemetry freshness
static build snapshot
StatusReadiness and live checks
Gate rulesimplemented
Free tracker firehosePumpDev implemented; no key required
Deploy executorpumpfun-direct selected; live signing locked
One-position lockimplemented
Simulation deployment cycleimplemented
Live executionlocked
Live hit detectorPumpDev implemented; no key required

Implemented

  • PumpDev free WebSocket scan normalization
  • 30s_observed_adoption gate
  • candidate scoring
  • one-position lock
  • deployment cycle orchestration
  • simulated exit plan
  • Pump.fun direct local transaction builder
  • PumpDev token-trade hit detector
  • ms telemetry

Watch before auto mode

  • provide PUMPFUN_WALLET_SECRET_KEY and metadata config in runtime env
  • enable ALLOW_LIVE_PUMPFUN_DIRECT only for a controlled live cycle
  • collect live P&L/slippage after controlled live cycle
RunbookDeployment-cycle process
  1. Operator submits one deployment request.
  2. If no candidate file is supplied, the bot watches the PumpDev free new-token firehose.
  3. Bot acquires the position lock only if phase is IDLE.
  4. Candidate is classified as 30s_observed_adoption.
  5. The candidate must be meme, AI, or tech, pass the 30-second observation model, and be tied to a Twitter/X or Instagram source.
  6. Approved candidates become a remixed direct Pump.fun deployment payload with a 3.5 SOL buy amount, reused image/social reference, near-identical symbol, and remixed description.
  7. Simulation checks the deployment path; live mode stays disabled until explicitly enabled.
  8. Every phase transition, miss, deployment, PumpDev message, and executor round trip is measured in milliseconds.
  9. After exit or failure, the lock returns to IDLE before another deployment can run.