WebSocket receives the Pons v2 factory event. Independent log polling runs as a discovery backstop.
SNIPE DOCUMENTATION
Operator
documentation.
SNIPE watches fresh Robinhood Chain launches, follows real Pons v2 curve activity, ranks early wallet flow and promotes genuine acceleration without fabricating market data.

01 / GETTING STARTED
Quick start
Node 20+ is required. The default public endpoints work for development, but a private Robinhood Chain RPC/WebSocket provider is the better production setup.
git clone https://github.com/0xwhrari/SNIPE.git
cd SNIPE
npm install
npm startOpen http://127.0.0.1:4173.
02 / DISCOVERY
Live launch feed
The live feed is session-only: it starts empty when the server boots and then accepts new real Pons v2 launches as they happen, up to 100 targets. Historical launches are read only for aggregate launch-rate and deployer context. SURGING is only a temporary priority layer on top.
Name and symbol are resolved before the row is exposed, using launch calldata and ERC-20 reads.
CurveBuy and CurveSell produce real buy/sell counts, unique buyers, net flow and recent wallet activity.
Observed launch and flow checks become the SNIPE score. Missing data is not invented.
0x7eD598BcEf8bd9Edd8C97A195C6d13f40801EC7e03 / MOMENTUM
SURGING means acceleration,
not freshness.
A token cannot flash merely because it was just launched. SNIPE first warms a momentum cache and then waits for a real trade event before it can be promoted.
HOT vs SURGING
HOT is sustained current strength: score, buyer pressure, repeat buyers and positive tape. SURGING is a temporary acceleration event detected against the token’s cached baseline.
Current acceleration triggers
+$3K60-second flow, or+4unique buyers, or+$1.5Kflow and+2buyers, or+$1Kflow and+5buys, or- score
+7with positive flow and buyer confirmation.
Confirmation: score ≥ 55, positive net flow, at least 3 buyers, and buys > sells. Snapshot/enrichment updates can build the cache but cannot trigger SURGING.
04 / SIGNAL ENGINE
Explainable checks,
not a mystery AI number.
The current score is deterministic and built from fields SNIPE actually observes. It is a ranking heuristic, not a prediction or promise of profit.
Creator share of supply. The current preferred band is 1–6%.
Lower launch creator tax scores better; high tax is a hard warning.
Declared token metadata links.
Opening-tax exempt wallet count from launch calldata.
Recent launch and graduation history for the deployer.
Unique/repeat buyers, B/S pressure and positive net flow.
Observed Pons curve progress.
Current decaying Pons opening snipe tax.
05 / WALLETS
Hot wallets
SNIPE builds the wallet table from real curve trades seen during the rolling 15-minute window. It ranks recent buy/sell money flow, net flow, trade count and token breadth.
GMGN profile links are provided as an external research layer. The current SNIPE server does not pretend GMGN data is live enrichment when it has not fetched it.
06 / PROVIDERS
Data sources
Canonical blocks, transactions, logs and contract reads. Mainnet chain ID 4663; ETH is the gas token.
Launch factory, bonding-curve state, creator tax, opening snipe tax and graduation state.
Explorer fallback for contract/token metadata, holder counters and external links.
External token and wallet research links. Future adapter territory; not silently marked LIVE today.
07 / CONFIGURATION
Environment
RH_STATE_RPC_URLcontract reads / multicallRH_LOGS_RPC_URLeth_getLogs discovery backstopRH_WS_RPC_URLprimary WebSocket stream; set off for HTTP-onlyBLOCKSCOUT_BASEexplorer API basePOLL_MSdefault 300ms, minimum 250msBOOTSTRAP_BLOCKSrecent launch history on startup; default 25,000MAX_TOKENSin-memory target cap; default 240ENRICH_MSbackground enrichment interval; default 12s08 / ARCHITECTURE
Runtime architecture
Robinhood WS→TokenLaunched→identity→curve trades→score + momentum→SSE UI
The backend owns discovery and on-chain enrichment. The browser owns filtering, the momentum cache and temporary SURGING promotion. Execution remains outside the live analytics path.
09 / IMPORTANT
What SNIPE does not claim.
- No fake token identities or pseudo contract addresses.
- No claim of “insider information”; wallet clustering is an on-chain heuristic.
- No guarantee that a HOT, LOCK or SURGING target will perform well.
- No live signer or autonomous trading in this build — execution is paper-only.
- Public Robinhood endpoints are rate-limited; production should use dedicated infrastructure.