First-time fee claims for GitHub-linked coins. Price, market cap, developer history, project activity, socials and more — a read-only Telegram feed.
Follow @pumpfunclaims · Product rules · Architecture · Implementation status
Someone discovers a developer's project, launches a coin around it and delegates trading-fee rewards to the developer's GitHub identity. When the developer collects those rewards, traders get a new reason to investigate the project. This feed is built to surface that moment quickly, with the context needed to assess the developer and coin.
The developer need not launch the token or publish its CA in GitHub. A developer may have many coins delegated to them and choose to support a particular one. The claim and that ongoing choice are separate facts.
| Label | Meaning |
|---|---|
| Transaction-Attributed GitHub Fee Claim | This transaction names the coin and distributes its fees to the claimed GitHub fee account. |
| Fee-History-Attributed GitHub Fee Claim | The claim transaction names no coin, but one coin paid at least 90% of the withdrawn fees into this exact fee account since its previous claim, and those distributions cover at least 90% of the withdrawal. |
| Verified GitHub Fee Claim | Claiming username exactly matches the repository owner in token metadata. |
| Creator-Wallet GitHub Fee Claim | Recipient wallet also created the token; repository ownership is not established. |
| Identity Mismatch | Claiming username differs from the metadata repository owner; a lookalike is possible. |
| Unverified | The withdrawal is real, but the GitHub-to-coin relationship is not proven. |
| Unresolved | The withdrawal lacks same-transaction coin-distribution evidence and is not published as a trading alert. |
“First” means the GitHub fee account's first-ever withdrawal, proven by the lifetime totals in the on-chain claim event. Claims that look like impersonation are held, not posted: a GitHub account younger than 30 days claiming a coin that is either a smaller copy of a same-name coin or points at a repository created in the last 7 days. A lookalike account can make the repository owner match by construction, so that match alone never vouches for a new account.
Trade buttons are limited to verified relationships. Every card is a research lead, not an endorsement.
| Claim | Notify? |
|---|---|
| Developer first claims coin A | Yes |
| Developer claims A again | No |
| Same developer first claims coin B | Yes, with previous claimed coins as context |
| Another token has the same name but a different CA | It is a different coin |
The key is the numeric GitHub user ID + full mint address. A developer's first-ever GitHub claim is additional context, not a gate that excludes their first claim on a different coin. Mere delegation does not trigger an alert.
The product contract explains this using the owner's three.ws / THREE example and sets out attribution, history and delivery rules.
This is the standalone home for the concept, extracted from nirholas/pump-fun-sdk. It includes the existing TypeScript monitor, enrichment clients, Telegram delivery, diagnostics and tests. The source can build and run independently of the general SDK.
The runtime implements the per-coin rule with same-transaction
DistributeCreatorFeesEvent evidence. It never selects a mint by market cap or
by a historical shared-PDA candidate list. Unattributed withdrawals remain in
the event/API stream without producing a channel card. A fee sweep, which only
moves fees into the creator vault ahead of a claim, is never treated as a claim. See the
2026-09-15 repair audit for evidence and limitations.
This repository's creation does not change the live channel deployment.
Requires Node.js 22 or newer.
npm ci
npm run checkcheck runs typechecking, tests and a build. No wallet, Telegram credentials or
live channel access is required for these checks.
To operate a configured instance:
cp .env.example .env
# Set your bot token, numeric channel ID and RPC endpoints in .env.
npm run build
npm startnpm start is the real publisher and can send alerts to the configured channel.
For diagnostics, persistence and migration, read operations.
The example selects the GitHub claims profile; other feed paths remain in the
inherited source for compatibility but are disabled by that profile.
PumpFun Tracker [Github Claims] 🛠️ 💊🟢 — Pump.fun GitHub Claims
- Feed: t.me/pumpfunclaims
- Suggestions: DM @nichxbt
- Related bots: @pfclaimsbot, @cryptocurrencyvisionbot
- Graduation channel: @migratedpumpfun
More channels coming soon. These are community links; verify the actual posting bot through the deployment configuration.
See provenance for the extraction revision and boundaries. Copyright 2026 nirholas. The upstream license is preserved; this public repository does not grant an open-source license.
If pumpfun-github-claims saves you time, star it on GitHub. Stars are how other developers and AI agents find the repositories worth trusting, and they cost you one click.
Know someone who would use it? Post on X · Share on Bluesky · Share on LinkedIn · Submit to Hacker News · Share on Reddit
Coding agents and LLM tooling can read this repo directly: AGENTS.md, llms.txt, llms-full.txt. Point an agent at https://github.com/nirholas/pumpfun-github-claims and it has the context it needs.
- All repositories by nirholas: the full catalog, grouped by topic
- three.ws: the platform for 3D AI agents with Solana wallets, a skill marketplace and x402 payments
- Questions or ideas: open an issue or start a discussion