Fieldcraft
The guide is a tracking device
The factory printed a manual. Bagworkers paste it. Marks follow it. Each instruction is a query. The same is true of “claim MFT” and “follow back for a step by step.” Run the queries and the case list compounds.
14 sensors · each one names a query · run them from Loop
- 01
The official claiming guide URL
URLIn progressConf. High- They tell the mark
- Pump’s own Medium post, addressed to people who did not launch a coin: “If you’re reading this, a community has launched a token for you… and is asking you to claim it.”
- Fingerprint
- https://medium.com/@pumpdotfun_/pump-fun-github-creator-fee-claiming-guide-d6f04af1acf6 — pasted in replies and DMs as if it were a grant letter.
- Query
- X/web: the Medium URL; replies to those posts; GitHub handles named in the same thread.
- Already on the board
- 24 Aug 2026: @jozzzeey drops the guide on Scotty Beam plus github.com/SCOTTYBEAMIO and a CA. 21 Aug: @DEGEN_JESS pastes it with “DMs open if any help is needed.” This is the hunting license.
Next One-week sample of every public post containing that URL. Tabulate mark, mint, whether they claimed.
- 02
The post-claim statement template
PhraseIn progressConf. High- They tell the mark
- After claiming, “make a public statement.” Sample copy in the guide: “Hey guys! Thank you for all the support, I’ve decided to claim the fees for [TOKEN]…” Also: buy some supply, stay active, use fees for marketing.
- Fingerprint
- First-time GitHub claim on-chain within hours of a tweet that names a mint and thanks “the community” or “bagworkers.” Lucipher is this template in the wild.
- Query
- X: “claimed the fees” + pump.fun/coin OR github; pair with claim_social_fee_pda in the same window.
- Already on the board
- Lucipher 26 Aug 2026 matches the shape: first Pump trade of his life, posts the mint, credits bagworkers, says he will spend fees to bond. That is the guide working.
Next Search 30 days of “claimed the fees” / “decided to claim.” Keep only GitHub/OSS authors. That is the conversion list.
- 03
“Connect your GitHub”
PhraseIn progressConf. High- They tell the mark
- Step one on the mobile app: connect GitHub, not X. Marks who have never used Pump get this screen and ask about it in public.
- Fingerprint
- “connect your github to pumpfun and get your fees”; “why am I getting option of connect github instead of X.”
- Query
- X/GitHub issues: connect github pumpfun fees. Replies usually name a mint.
- Already on the board
- Same week as Lucipher: @coinsolmaxi “connect your github to pumpfun and get your fees on this”; @Thebiglup “Just need to verify ur github… pump.fun/coin/7Mtv5C…”; confused users asking why GitHub not X.
Next Treat every “connect github” reply-guy as a deployer. Archive the mint. Follow 72h for a social-fee claim.
- 04
First-time claim_social_fee_pda
On-chainOpenConf. High- They tell the mark
- Nothing — this sensor watches them after they obey. The instruction is public; snipers already pay for the feed.
- Fingerprint
- PumpFees program, platform=GitHub, first SocialFeePdaClaimed with amount > 0. Bots flag zero-lamport fakes.
- Query
- Run or subscribe: nirholas/pumpfun-claims-bot; @pfclaimsbot on Telegram; Dune on claim_social_fee_pda.
- Already on the board
- @nichxbt: “an easy 10x if you were tracking these exact claims.” The GitHub Claim Tracker is sold as alpha, which means the conversion event is frequent enough to trade.
Next One week of FIRST TIME CLAIM cards. Names, GitHub ages, SOL claimed, mint. That is the denominator for hit-rate.
- 05
pump.fun/coin/ pasted under a release
URLIn progressConf. High- They tell the mark
- “Someone made a coin for you. Fees to your GitHub. Claim here.” The mint URL is the payload.
- Fingerprint
- pump.fun/coin/<mint> in a reply to a GitHub README, launch tweet, or LinkedIn-adjacent post.
- Query
- X: url:pump.fun/coin (github OR “your github” OR “claim the fees”) minus known KOLs.
- Already on the board
- 20 Aug: “someone made a coin for you… 3UryJqLm65K…pump.” 25 Aug: 7Mtv5CgX…pump under a verify-github ping. Roemmele: Be7DADB…pump. Lucipher: 9CANf2…pump. Pattern is daily.
Next Script a 7-day scrape of pump.fun/coin links in replies to accounts with github.com in bio. That’s the incoming queue.
- 06
Already claimed once
ProductIn progressConf. High- They tell the mark
- Once you claim anywhere, you are in the phone book. Next desk routes a new coin at the same GitHub because “he knows crypto.”
- Fingerprint
- Public Bags/Pump claim, then a new mint pointed at the same GitHub within days, often with the prior claim cited as proof they will convert again.
- Query
- X: “just claimed” + “send fees to his github”; cross-check prior Bags claimers against new Pump GitHub PDAs.
- Already on the board
- 20 Jun 2026: Carsen Klock (mactop, github.com/metaspartan) cited as having claimed Bags; @RedOval93 launches DvdkSX9…pump “HE WILL PROBABLY CLAIM THIS SINCE HE KNOWS CRYPTO AND CLAIMED BAGS.”
Next List known Bags claimers (Yegge, Huntley, Klock, others). Search Pump GitHub PDAs in their names. The sequel is the industry.
- 07
“It’s like crypto VC”
PhraseIn progressConf. High- They tell the mark
- Copy-paste: community loves your tech; devs have raised 6–7 figures; claim via GitHub under creator rewards; here’s the Medium guide.
- Fingerprint
- “6-7 figures” / “crypto vc” / “crowdfunded a donation to your GitHub” / “haven’t you noticed yet?”
- Query
- Exact phrases above + github. Cluster by author — those accounts are desks.
- Already on the board
- Scotty Beam (the VC script + Medium URL). Oli @oliviazzzu (119k-view Claude-Code post): “A community crowdfunded a donation to your work… sitting there for almost two weeks… DM me.” AGENT 37: “let me know if you need help on how to claim.” DVLPLONDON: “will tell him how to claim fees.” Game devs: “fees is redirecting to your github.”
Next Build a desk list from repeat scripters (@jozzzeey, @voidinzin, @DEGEN_JESS, @RedOval93). One interview attempt per desk.
- 08
Pump support will introduce an “affiliate”
ProductOpenConf. Medium- They tell the mark
- Guide step 1: contact Intercom. “Support may connect you with an affiliate who can provide tailored insights.” Also: download https://join.pump.fun/HSag/x — an affiliate-coded app link.
- Fingerprint
- Intercom tickets + affiliate join links in mark DMs. Harder to see from outside.
- Query
- Ask marks whether Pump support introduced anyone. Search join.pump.fun/ coded links.
- Already on the board
- The sentence is in the official guide. That is a platform-mediated bagworker. No named affiliate yet.
Next FOIA-less: interview two marks about who Intercom sent. Capture the join.pump.fun slug graph.
- 09
Claim and shout out
PhraseIn progressConf. High- They tell the mark
- Nonprofit version of the same guide: fees to your org, Pump will match, please claim and thank the community.
- Fingerprint
- “claim the fees & give a shout out”; charity thank-you tweets after a Pump mint.
- Query
- X: (charity OR foundation OR nonprofit) (claim the fees OR shout out) pump.
- Already on the board
- LCFA $SLEEP 24 Aug; Rainforest Foundation DMs; LCFA later posted thanks to “the crypto trading community” — verify whether that was this machine.
Next Round 9 leftover: reconstruct LCFA and Rainforest. Matching-funds vs docs.
- 10
Claim MFT / Claim-Pad URL
URLIn progressConf. High- They tell the mark
- Not a GitHub celebrity — a holder. Official how-to: deposit the old token, claim an MFT receipt, come back when the window ends, redeem for the relaunch. Catcoin: “click migrate then claim MFT.” BOBO: “Claim BOBO MFT (Migratefun Token) on Solana.”
- Fingerprint
- migrate.fun/migrate/mig…, migrate.fun/claim/, migrate.fun/project/mig…, the phrase “claim MFT”, “Claim-Pad.”
- Query
- X: url:migrate.fun (claim OR MFT OR migrate); “claim MFT”; “claim-pad”. Split official @MigrateFun from lookalikes.
- Already on the board
- 26 Aug 2026: mig221 30.61% deposited (306.1M of 1B), 50M CAT = 1 MFT, ~12d left. Official how-to 19 Aug (SOL one tx, BNB two wallets + claim MFT). Four @catcoin “NEVER DM first / no support account” warnings the same week. 20 Apr: BOBO official “this is the official migration link” plus a scam warning — the warning is the tell.
Next One week of every public migrate.fun URL. Tabulate project, official vs impersonator, whether the poster is a repeat desk.
- 11
“Follow back… step by step guide”
PhraseIn progressConf. High- They tell the mark
- Fake support, riding the official how-to. The holder is already trying to claim. The reply offers a private walkthrough.
- Fingerprint
- “follow back and send a message for step by step”; “claim your tokens directly from migratefun Claim-Pad”; “manually synchronize your wallet with the contract deployer”; bios: “Migrate your liquidity anywhere | DM for requests and support.”
- Query
- X: (“step by step guide” OR “claim-pad” OR “Claim-Pad”) (migrate OR MFT); from: accounts with MigrateFun in the handle minus @MigrateFun.
- Already on the board
- Round 14 Catcoin window: recycled pre-2015 IDs @MigrateFunCTO / @MigrateFun_CTO / @Migratefun_DEX / @MigrateFunCS / @MigrateFun_T plus costume names @noahscholes_, @CptoOvejaNegr (“Kirk Behke | CTO”), @goodtraveloffer (“Carl Williamson | CatCoin Support”). Named holders: @Ovickyoung (“you are the scammer”), @ttvtt0304 (Gate.io), @Dandy09097 (sync with deployer). Same week as the official how-to and four official “we will never DM you” posts.
Next One confirmed drain. Exact join dates vs handle-swap. Watch through 7 Sep close.
- 12
How to claim Creator Fees as a CTO
ProductIn progressConf. High- They tell the mark
- Pump’s own Jul 2025 thread: abandoned-dev coins can apply to redirect creator fees. Form + [email protected] only. “Indisputable proof the community wouldn’t survive without the CTO lead.” Closing tweet: anything after this is a scam.
- Fingerprint
- “claim Creator Fees as a CTO”; [email protected]; “indisputable proof”; Pump thread 1946290140592377889.
- Query
- X: url of that thread; replies offering alternate forms or “I can help you apply.” Those reply-guys are a desk.
- Already on the board
- 18 Jul 2025 announcement, 1.2M views. Migrate.fun quote-tweeted it the next day with a pitch to unlock more than “crumbs.” The application is the honest path; the migration is the productized bypass when Pump will not reroute.
Next Is the form still live? One approved redirect (before/after fee wallet). One impersonated cto@ email.
- 13
“Full transparency” as the CTO press release
PhraseIn progressConf. Medium- They tell the mark
- After a migrate/CTO, the public statement is not “I claimed the fees.” It is “we migrated for full transparency.” Same function as Pump’s post-claim template: a blessing, a candle, a new holder set.
- Fingerprint
- “migrated / CTO via” + migrate.fun; “full transparency” near CTO/migrate; “Operation: Liberation”; “taking back control.”
- Query
- X: (“full transparency” OR “taking back control” OR “unlock the LP”) (CTO OR migrate.fun OR @MigrateFun).
- Already on the board
- User-supplied field line, 25 Aug 2026: “They migrated / CTO via my platform migrate.fun for full transparency.” Permalink not recovered this round — treat as founder-voice until sourced. Project89: “Let’s be transparent.” Catwifmask CTO: “run like a business with full transparency” after the old dev “stole over 200k in creator fees.”
Next Source the user quote. Archive three more CTO-via-migrate.fun blessing posts. They are the press-release template for this rail.
- 14
Claim code in the bio
PhraseIn progressConf. High- They tell the mark
- Socialify: add a unique claim code to your public bio; “I've Added It — Verify Now.” Spark (now 404): put sprk.gg/<code> in your TikTok bio, or Sign in with X. The instruction is the conversion event.
- Fingerprint
- “claim code” + (bio OR tiktok OR github); socialify.fun claim UI; sprk.gg/ short links in bios; CTA “I've Added It.”
- Query
- X/TikTok/GitHub bios containing socialify, sprk.gg/, or an obvious one-off claim code next to a Pump mint. Web: “claim code” “pump.fun” bio.
- Already on the board
- 26 Aug 2026: Socialify docs still live — scraper watches 19+ platforms including GitHub, TikTok, X, Pornhub. Spark coin pages and TOS were indexed with the same bio-link mechanic, then DEPLOYMENT_NOT_FOUND. No named mark photographed this round.
Next One week of bios. One named paste. That is a new incoming queue next to the Medium-guide URL.