The play

Six beats, any launchpad

The technology is fee routing to a social identity. The social technology is making a claim look like a product launch. Platforms documented the first half. Bagworkers run the second. This six-beat is the core. 32 documented variations change who the mark is, how the blessing is faked, and what happens after.

01
Find a mark
A GitHub repo with stars, a new OSS release, a LinkedIn engineer, a charity, a meme subject. The identity has to be googable and, ideally, unused to crypto DMs.
02
Launch without them
Deploy on Pump, Bags, or Bankr. Configure fee sharing so a cut of every trade accrues to their GitHub username, X handle, or a wallet you hope they will control.
03
Attach the name in public
Coin name, bio, and replies all say the fees are “for” the project. Dashboards show a GitHub recipient. Retail reads affiliation.
04
Hunt the claim
Reply-guys, Telegram, paid LinkedIn InMail, Medium “how to claim” guides. Script: peer already cashed six figures; this is crowdfunding; it’s free money.
05
The claim as event
A first-time social-fee claim is watched by bots. Snipers treat it as a candle. Holders screenshot it as blessing. The mark has now been drafted as the “dev.”
06
Exit and leftover heat
Inventory dumps. If the mark stays, they inherit support tickets and blame. If they vanish, bagworkers say they rugged a coin they never launched.

Glossary

Mark: The developer, maintainer, or public person whose identity is used as the fee sink, usually without a launch agreement.
Bagworker: Slang for the person (or desk) that launches the coin, seeds chat, and nags the mark to claim so holders can exit.
Claim: On-chain collection of accrued creator fees. Socially: treated as endorsement.
Social fee PDA: Pump.fun account that holds fees for a GitHub (or other social) user id until they authenticate and sweep.
Fee sharing / redirect: Configuring who receives the creator cut — wallets or social identities — often after or instead of a fair deployer.
Vamping: Changing the fee recipient after the coin has traction, pulling cashflow away from the trusted destination.
Bond: On Pump, completing the bonding curve so the coin migrates to an AMM. Marks are sometimes asked to spend claimed fees to “help it bond.”
Get Bagged: Bags’ product name for launching a coin on someone else’s identity or content without asking, then letting them claim royalties.
Charity coin: Pump feature routing creator fees to a nonprofit via Donate.gg. Also the narrative bagworkers use when DMing that nonprofit for a shout-out.
Impersonation git: Standing up a GitHub that looks like a real employee — often backdated commits — so the bagworker can claim fees as if they were the mark.
Sensor: An instruction in a claiming guide that leaves a public fingerprint — a URL, a phrase, an OAuth screen, or an on-chain instruction — which can be queried to find more marks.
Canonical token: Pump’s claiming guide tells marks to claim fees from only one coin, which communities then treat as the official one. That sentence is how a hijack becomes a brand.
1% and a smile: Unsolicited coin; the mark is given a sliver of supply instead of creator fees, stays as the face, and later migrates to a contract that actually pays them.
CTO: Community takeover: holders or the drafted mark inherit a coin the original deployer abandoned or never intended to run. Fees become a political office, or the team migrates off the launchpad to capture them.
Launch-for-you: A website that deploys a Pump coin pointed at someone else’s social identity. Socialify is live; Spark lasted four days. Ambush is the product.
Claim code: A one-off string the mark is told to paste into a public bio so a scraper can treat that edit as verification — and as the attention event.
Reclaimable gift: Socialify’s escrow: creator fees sit with the wrapper until the mark claims. The deployer can take them back at any time. Not a donation.

Six beats, any launchpad

Find a mark

Launch without them

Attach the name in public

Hunt the claim

The claim as event

Exit and leftover heat