Continuation protocol
How this desk stays alive
This is a research system, not a one-shot brief. Each round should discover a variation, kill a fake, or fill a hole — then write the next prompt before stopping. Guides that tell marks what to do are sensors: run them.
- 01
In this chat
Reply keep going, round 15, go deep on [variation], run the sensors, or go broad on [adjacent]. Or paste any prompt from the queue below.
- 02
A daily pass
A Grok automation can run the next queued round each morning, update the binder, and leave a note. Pause it whenever the desk should sleep.
- 03
Steer, don’t restart
If a round is wrong, say so in one line and the next pass will rotate. The binder keeps the memory.
Prompt queue
Paste one of these back into the chat. That is how the binder compounds without a briefing.
Do next
HUSTLE unmigrated P&L
deepThe 23% treasury figure is a homepage. The map needs the chain.
Verify @MigrateFun’s HUSTLE numbers on-chain: 77% migrated, 869 SOL unlocked, 23% of new supply to team treasury, 3% platform fee. Name the treasury wallet. If the numbers fail, mark the card low-confidence and say so.
One week of the claiming-guide URL
broadThe factory printed a tracking device. A week of pastes is a sample, not a vibe.
Round 10, run the sensors. Archive every public X post that contains the Pump GitHub claiming-guide Medium URL for the last 7 days (and going forward if possible). For each: mark, GitHub, mint, whether they claimed, whether the poster is a repeat desk. Put the table in Claim Desk. Do not bias to Bags.
Charity-coin reconstruction
deepHighest-leverage halo variation. Without receipts the halo is just DMs.
Go deep on charity-as-mark. Reconstruct $SLEEP to Lung Cancer Foundation of America and one Rainforest Foundation US coin. Did the nonprofit solicit, claim, shout out, or get matched by Pump? Add the P&L and interviews-owed to Claim Desk.
Read a week of first-time claims
broadThe on-chain sensor already exists as a Telegram product. That feed is the conversion list.
Find a live first-time GitHub social-fee claim feed (nirholas bot, pfclaimsbot, Dune). Log 20 FIRST TIME CLAIM cards: GitHub, account age, SOL claimed, mint, credibility flags. That is the start of a hit-rate table.
This week
Catcoin window close-out
deep30.61% deposited, 69.4% remaining, clock to ~7 Sep. Remaining is not treasury until close. BNB-liquidity pull would be a coercion event.
When mig221 closes (~7 Sep 2026): final % migrated, remaining, whether it became team treasury, whether BNB LP was pulled, whether any named holder was drained. Do not treat remaining as captured before close. Do not bias to Bags.
Who runs migrate.fun
broadThe user quote is founder-voice without a founder. Entity, Jake Gallen, Emblem Vault. Round 14: mig221 UI says Powered by Emblem Vault.
Who runs migrate.fun / @MigrateFun / $EMBLEM / Emblem Vault. Source the line “They migrated / CTO via my platform migrate.fun for full transparency.” File, interview, or kill the quote as unsourced.
GitHub impersonation case
deepDifferent crime, same phone book. If we conflate it with unsolicited gifts, the mechanism section lies.
Go deep on GitHub impersonation: OnchainCop’s change-your-github-to-his-name pattern and Shaw’s fake-commit complaint. Find one reconstructed employee case with account-creation vs commit dates vs mint. Kill it if it’s just lore.
Verify the Sovra refund
deepOnly named mark who unwound the casino. On-chain proof is required before the $17k stands.
Verify Gajesh/Sovra: refund tx starting 0x5a27caac on Base, launchpad, deployer, claimed 17k across 545 wallets. Then sketch CONWAY/Sigil. Update the Sovra case file and money section.
Sequels on known claimers
broadKlock shows conversion is treated as a permanent attribute.
Cross Yegge, Huntley, Klock, Lucipher, Scotty against later Pump GitHub PDAs and Bags coins in their names. Count sequels. That is the CRM.
Socialify live inventory + one bio paste
broadPublic pages are SPA-gated. Without a count and a named bio paste, Socialify is a product page, not a factory.
Count Socialify deployed_tokens / fee_gifts (auth or scrape). Find one named creator who put a Socialify claim code in a bio. Record reclaim if any. Service-fee percent if a tx reveals it.
Archive Spark TOS before the index dies
broadsprk.gg is 404. Search snippets still hold the TOS, privacy, and coin pages. That cache is perishable.
Archive every remaining sprk.gg URL from the search index (home, docs, terms, privacy, /creator/elonmusk, named coins). Full TOS text. One claimed TikTok coin, or confirm zero. Keep the log; do not treat a dead wrapper as a live factory.
Project89 reconstruction + two more stays
deepThe stay-and-migrate aftermath is named. Without a deployer, the 1% on-chain, and two cousins, it is a color scene.
Go deep on Project89 / Parzival. Reconstruct the original Pump deployer for mint Bz4MhmVRQENiCou7ZpJ575wpjNFjBjVBSiVhuNg1pump. Did the 1% supply transfer happen on-chain? Peak mcap vs what he was given. Then hunt two more “1% and a smile” CTOs — unsolicited Pump launch, mark stays, later migrate to capture fees. Log them even if they never lead. Many is good.
When the holes above close
Catcoin window + Claim-Pad impersonators
deepRound 14 ran. mig221 is 30.61% with ~12d left. Cluster logged. Next pass is close-out, not the same search.
Resume Catcoin impersonators only if a new named drain appears or BNB LP is actually pulled. Otherwise wait for window close (~7 Sep).
GitHub-PDA hit rate
broadWithout a rate we cannot say cottage vs industry. Dune $11.9M/7d is the wrong denominator.
Go broad on scale. Design (and if possible run) a query: 100 GitHub-routed Pump coins in one week, how many get a first-time social claim in 72h. Isolate claim_social_fee_pda from ordinary deployer claims.
Who is Socialify
deepRound 13 ran. Operator still unnamed. Wallet 0 SOL. @SocialifySolana silent. Next pass needs a login-gated scrape or a new breadcrumb.
Resume Socialify operators only if a new breadcrumb appears: FJ3rPDt… funded, @SocialifySolana posts, Lovable project owner named, or an entity filing. Do not re-run the same empty searches.
A Bankr mark this week
deepUser said it happens every day on Bankr. We still lack a named 2026 mark.
Go deep on Bankr/Clanker: find one named person in the last 14 days who had fees redirected to their handle or wallet without deploying the coin. Screenshot the ping. If you cannot find one, say so and list the search.