PumpFun Claims Bot

PumpFun Claims Bot

Read-only Telegram channel feed that broadcasts PumpFun on-chain activity — GitHub social fee claims, token graduations, and more. Posts rich, intelligence-enriched cards to a Telegram channel in real time.

Website · Live Channel · MCP Server · Deploy Guide · Contributing

Looking for interactive monitoring? The telegram-bot supports watch management, group chats, REST API, SSE streaming, and webhooks. Use this channel-bot for simple broadcast-only channels.

Related Source

Pump.fun GitHub Claims — `nirholas/pumpfun-github-claims` is a focused companion repository for the @pumpfunclaims feed. It provides standalone bot source and documentation for first reward claims per GitHub developer and coin, with previous claimed coins as context. Its implementation status tracks the remaining coin-attribution work. This repository offers the broader toolkit, including web dashboards, an MCP server, credibility scoring and developer reputation tracking. Both repositories remain available as sources.

Features

What a GitHub claim actually proves

A claim card starts with a real on-chain withdrawal from a Pump.fun GitHub social-fee account. That is useful evidence, but it is not automatically proof that the GitHub user created, owns, or endorses a coin. Token metadata is user-supplied, lookalike accounts exist, and one social-fee account can be shared by several coins.

“First-ever” refers to the GitHub fee account, not necessarily the displayed coin. Trade buttons are shown only for verified repository or creator-wallet relationships. The feed is discovery evidence, never an endorsement.

Feed Types

Claim Intelligence

Every GitHub social fee claim card includes:

Graduation Cards

Rich graduation cards include creator profile, top holders analysis, 24h trading volume, dev wallet activity, pool liquidity, and bundle detection.

Influencer Tier System

Combines GitHub and X/Twitter follower data to classify claimers:

Either threshold triggers the tier — a user with 50K X followers and 50 GitHub followers still qualifies as Influencer.

Credibility Score & Dev Track Record

Every claim card leads with a deterministic 0-100 credibility verdict synthesised from the trust signals the bot already gathers, plus the claiming dev's persistent track record across prior tokens.

The score is deterministic and transparent — same inputs always produce the same number, no model call, and every point is attributed to a named factor shown under the headline:

Scoring starts at a neutral 50 and adjusts by weighted factors: claim verification (+22, or -20 on a GitHub-owner mismatch), account age (+14 for 5y+ down to -18 for < 30 days), public repos, followers, starred non-fork repo, copycats (-10/-16), bundling, holder concentration, prior rugs, and bans.

Dev track record turns that one-shot score into memory. Every score is recorded against the claiming GitHub user id and persisted, so the next time that dev launches a token the card shows their history — exposing a serial fee-farmer whose newest coin looks clean, and crediting a builder with a real record:

🟢 Credibility: 100/100 · Strong

↑ claim verified · GitHub 6y · 42 repos · repo 150★ 📊 Dev track record: 3 prior tokens · avg 🔴 19/100 (High Risk)

Logic lives in src/credibility.ts (pure scoreCredibility) and src/dev-reputation.ts (persistent store), both fully covered by tests.

AI-Powered Claim Summaries

First-time claims get a one-line AI take generated by Groq (llama-3.3-70b-versatile):

• Analyzes 30+ signals: token metadata, GitHub profile, creator history, trading activity
• Max 120 characters — direct, opinionated, trader-focused
• 5-second timeout with graceful fallback (empty string on failure)
• HTML-sanitized output safe for Telegram

Examples:

_"Real GitHub project, dev claimed fast"_ · _"Fork of popular repo, proceed with caution"_

Architecture

Solana RPC (WebSocket + HTTP polling)

│ ▼ ┌───────────────────┐ │ SocialFeeIndex │──▶ Bootstraps ~148K SharingConfig → mint mappings └────────┬──────────┘ │ ┌────────▼──────────┐ │ ClaimMonitor │──▶ Decodes PumpFees program claim transactions │ EventMonitor │──▶ Decodes Pump program logs (graduations) └────────┬──────────┘ │ FeeClaimEvent / GraduationEvent ┌────────▼──────────┐ │ Enrichment Layer │ │ ├─ GitHub API │──▶ User profile, repos, followers │ ├─ X/Twitter API │──▶ Follower counts, influencer tier │ ├─ PumpFun API │──▶ Token info, creator profile, holders, trades │ ├─ ClaimTracker │──▶ First-claim detection, persistent counts │ └─ Fake Detect │──▶ Instruction called but no payout (amountLamports=0) └────────┬──────────┘ │ ClaimFeedContext ┌────────▼──────────┐ │ Formatters │──▶ Rich HTML cards with sections & emoji layout └────────┬──────────┘ │ ┌────────▼──────────┐ │ grammY Bot │──▶ Posts photo + caption to Telegram channel │ (retry + rate │ Falls back to text-only if photo fails │ limiting) │ └───────────────────┘

Multi-RPC Failover

The RpcFallback class manages multiple Solana RPC endpoints with automatic rotation:

• Round-robin rotation after 3 consecutive failures on any endpoint
• 60-second cooldown per failed endpoint before retrying
• Earliest-expiry fallback — if all endpoints are in cooldown, picks the one expiring soonest
• Success resets — a single successful call resets the failure counter
• Configure via SOLANA_RPC_URLS (comma-separated)

Programs Monitored

Claim instructions decoded (v1 and the V2 variants from the October 2026 upgrade):

sweep_creator_fee and sweep_protocol_fee (Pump and PumpAMM) are recognised but are never counted as a claim: a sweep only moves fees the curve or pool still holds into the cr