Update, October 14: Bubblemaps has published a new caller-specific allegation concerning Pump.fun Callout Rewards, this time naming the account @anglio. This update preserves the original article’s October 10 publication date and adds the new disclosure to the existing dispute; it does not establish that the alleged trading happened today.

In the thread reviewed through an accessible public reproduction, the analytics firm said it examined 534 callouts over the preceding two weeks. It alleged that a five-wallet cluster connected to the account bought before 61% of those calls, with average buying 20 seconds before a callout and selling beginning four minutes afterward. Bubblemaps cited shared deposit addresses and funding routes as its attribution evidence.

The firm estimated $130,000 associated with the linked wallets: $50,000 from trading and $80,000 from Callout Rewards. These are Bubblemaps’ estimates, not losses confirmed by Dev.Cooking. Its thread also limits the favorable trading figures to trades involving the alleged side wallets. They should not be presented as a complete account-level profit calculation.

The missing distinction is between a suspicious sequence and a demonstrated common-control arrangement. A transfer path can support further investigation without identifying the person who authorized every trade. Reproducing the claim would require complete addresses, transaction signatures, callout records, a stated cost-basis method and identifiable reward payments. Dev.Cooking has not reproduced the wallet attribution, timing statistics or dollar estimate and is not making a finding of fraud, a rug pull or criminal intent.

Attempts to retrieve Anglio’s current public profile did not produce an accessible response for this review. That does not establish that the account has made no response. Nor should Alon’s October 9 defense of the program, discussed below, be represented as an answer to the new October 14 allegation.

The new disclosure makes incident-level accountability more urgent while Pump.fun revises its rewards. A general promise to favor profitable follower outcomes cannot show whether a particular disputed payout was investigated or corrected. An operator decision tied to the relevant receipts would answer a different question from a leaderboard or a revised marketing description.

Earlier update: the unpublished microcap cutoff

Update, October 13: Pump.fun has started changing Callout Rewards, but the rule separating an ordinary microcap call from an exceptional early discovery remains private. Co-founder Alon said on October 10 that rewards for low-cap token callouts would be reduced and that trading volume would stop being the main attribution signal. He said the program would focus instead on whether people who trusted a callout made money.

In an October 12 clarification, Alon said the threshold used to classify a microcap is “not yet public.” He described two goals for the work in progress: stop rewarding accounts that generate large callout volume without regard to follower outcomes, while preserving a path to rewards when an unusually early call produces gains for followers. He said more communication would follow.

The update answers one question raised by the original dispute: Pump.fun is changing the incentives rather than defending the prior formula as final. It leaves the reproducibility problem intact. The public still does not know the cutoff, how follower profit is measured, which entry and exit window counts, or how an exceptional low-cap callout overrides the reduction. Alon described a rollout over several days beginning with the October 10 payout, so the announcement should not be read as a fully specified rule that outsiders can already audit.

The change also matters beyond callers. Paying for follower outcomes may align incentives more closely with what users experience than rewarding raw attributed volume. But without a published observation window and execution assumptions, even an outcome-based score can favor a price peak that followers could not capture or ignore losses after the measurement period. The program’s current terms still give Pump.fun broad discretion over those choices.

Pump.fun’s Callout Rewards program is facing a test that cannot be settled by a leaderboard screenshot. On October 9, blockchain-visualization account Bubblemaps alleged that wallets linked to the Pump.fun account @0xEthan bought tokens before public callouts and began selling soon after. A response from Pump.fun co-founder Alon rejected the broader claim that the program rewards scammers and argued that a circulating table had been constructed to make recipients look worse.

The two posts do not resolve the same question. Bubblemaps made a specific wallet-attribution and trade-timing allegation. Alon defended the quality of the rewards cohort with a different statistical presentation, without addressing the cited wallets or transaction sequence in his post. The dispute therefore exposes a larger design problem: Pump.fun’s published rules prohibit common-control wallet manipulation, but the platform keeps the metric, rankings and reward calculations confidential.

That leaves outsiders able to inspect transactions but unable to reproduce why a caller was paid, excluded or allowed to remain on a ranking.

What Bubblemaps alleged, and what it did not prove publicly

In its October 9 thread, Bubblemaps said it reviewed 49 callouts from @0xEthan and identified a cluster that bought before calls and sold minutes later. The firm said selling began, on average, within three minutes of the first call. It displayed shortened prefixes for one wallet attributed to the account and three alleged side wallets, then estimated $125,000 in total profit: $45,000 from trading and $80,000 from callout rewards.

Those figures and wallet links are Bubblemaps’ allegations and estimates, not findings independently reproduced by Dev.Cooking. The public thread names only shortened address prefixes in its text and relies on attached graphics for the transaction narrative. Short prefixes and screenshots are not enough to establish common ownership, calculate complete cost basis, test transfers outside the illustrated cluster or confirm the reward total from first principles.

The thread also uses the phrase “extraction scheme.” That characterization should not be mistaken for a court finding, regulatory decision or proof of criminal intent. A buy before a post and a sale after it can create a concerning chronology; it does not, by itself, identify who controlled every wallet or establish a prohibited arrangement.

The account named in the thread later responded publicly that tokens commonly go to zero and that traders are supposed to buy low and sell high. That reply defends selling as ordinary trading but does not address the alleged wallet links, the pre-call timing or whether any Callout Rewards came from the cited activity.

Pump.fun disputes the framing, not the wallet sequence

About two hours after the first Bubblemaps post, Alon published a response opening with a rejection of the claim that Pump.fun rewards scammers. He said a Callout Rewards table circulating over the previous day was “completely manipulated,” then supplied another table using similar filters while intentionally excluding callouts above a $500 million market capitalization. He also argued that using median rather than average callout performance hurt the optics of recipients.

Alon acknowledged that some “bad traders” receive rewards while arguing that many strong traders deserve their payouts. He said the program’s objective remains rewarding ethical traders who are safe for users and added that the platform would get there eventually.

That is a meaningful response about the population-level presentation of the program. It is not a transaction-level rebuttal to Bubblemaps. The post does not name @0xEthan, dispute the wallet prefixes, publish full addresses, provide an alternative chronology or say whether Pump.fun opened an investigation. The reviewed official material also does not say whether any rewards connected to the allegation were frozen, recovered or left unchanged.

The dispute follows an earlier admission that the incentive design needed work. On October 3, Alon said Callout Rewards V1 had inadvertently rewarded the wrong behavior, producing low-quality spam. He said the algorithm was changed to favor quality over quantity and to diminish returns as a user makes more daily callouts. In the same post, he said both spamming and dumping on followers would not work.

The rules are strict; the revised scoring is still a black box

Pump.fun’s Callout Rewards terms, last updated August 13, draw a clear boundary. Section 7 prohibits manipulating rewards or rankings through self-dealing, coordinated engagement or trading between wallets under common ownership or control. It also prohibits automation intended to inflate measured activity and participation in front-running, pump-and-dump, rug-pull or other manipulative schemes.

The operator may investigate suspected violations, exclude users or wallets, withhold or recover rewards and suspend access. Those powers would cover the type of conduct Bubblemaps alleges if the operator determined the allegation was accurate.

But Section 8 creates the reproducibility gap. It says the activity metric, ranking methodology, reward-pool composition and calculations are confidential, may change without notice and need not be disclosed or applied consistently. Rewards are discretionary, and the operator may change a ranking or allocation without explanation. The terms also say the platform does not verify or endorse user callouts.

The October 10 rollout announcement changes the stated priorities, not those disclosure terms. Moving away from raw volume and reducing low-cap rewards could make spam less profitable. Yet an unpublished microcap boundary creates a new classification decision that callers and followers cannot independently reproduce. Until Pump.fun publishes enough of the method to test an example, “followers made money” remains a goal rather than an auditable metric.

Those clauses give the operator flexibility to fight gaming. They also prevent the public from checking whether its enforcement matches its stated rules. A critic can reconstruct swaps and callout timestamps; only Pump.fun can reveal the inputs used to calculate attribution, reward size and eligibility.

What a verifiable resolution would require

The strongest response would not require exposing the entire anti-abuse model. Pump.fun could publish enough incident-specific evidence to answer four narrow questions:

  • Which complete wallet addresses were reviewed, and what evidence supported or rejected common control?
  • Which callout timestamp and attribution window applied to each disputed trade?
  • How much USDC was actually transferred on-chain as rewards for the callouts at issue?
  • Did the operator exclude, recover or uphold those rewards under Sections 7 and 8 of its terms?

Without those answers, the argument can keep moving between two incomplete datasets: public chain activity without the reward formula, and an internal leaderboard without reproducible wallet attribution.

For readers, the practical lesson is to separate a callout’s visibility from its reliability. A rewarded caller is not necessarily a vetted analyst, and a profitable-looking callout table may measure peak price rather than an exit a follower could execute. Save the full contract address, callout timestamp, caller profile and suspected wallets before drawing conclusions. Dev.Cooking’s guide to why holder addresses are not automatically people explains the attribution limit. The Pump.fun–Arkham wallet-label update shows how more labels can aid investigation without proving ownership, while the meme-coin archive tracks related launch-platform developments.

Reporting and image notes

Original Dev.Cooking news analysis based on the listed primary statements and program terms. The October 14 update adds Bubblemaps’ new Anglio thread, whose text was reviewed through the linked public reproduction because direct X retrieval was unavailable. Its publication date is separate from its retrospective two-week trading sample. Earlier coverage and the original publication date are preserved. The reporting distinguishes allegations, platform statements, announced changes and independently observable limits. Dev.Cooking has not established common wallet ownership, reproduced either caller-specific dollar estimate or determined that any person committed fraud, manipulation or a crime. The program terms and existing cover’s exact license record were rechecked on October 14. Distinctive new sentences were spot-checked externally; those limited checks are not worldwide originality or legal certification.

The cover is Knites’ real December 24, 2024 photograph of a loudspeaker, released under CC0 1.0. It is a visual metaphor for token callouts, not a photograph of Pump.fun, @0xEthan, a disputed trade or evidence in the allegation. It was center-cropped, resized and converted to WebP without adding or removing objects. No endorsement is implied. Corrections: Hello@dev.cooking.