BTC PEERS is a leading source of Bitcoin insights, cited by

Wikipedia · Forbes · Coindesk · Nasdaq · Cointelegraph · RBC · Yahoo Finance · Entrepreneur · CoinMarketCap · Hackernoon · The Block · Investing.com · Bitcoin.com · Tech Times + thousands more

BINANCECrypto. Around the clock.Discover digital assets, markets and more.
Explore BINANCE
News

Pumpfun’s V2 Fee Sharing Allows One Final Recipient Update

Pumpfun’s V2 shared-fee workflow permits one final recipient update and pays pending fees to the existing recipients before applying the new split.

Pumpfun’s V2 Fee Sharing Allows One Final Recipient Update

Trader Ton, who posts as @tontheneko, proposed a fee-allocation framework for Solana memecoins on November 17: pay an identifiable creator, and consider holder rewards when that creator rejects the fees. For teams using Pumpfun’s V2 shared-fee configuration, choosing the recipient split carries a specific constraint: the documented workflow permits one final update.

Pumpfun’s creator fee-sharing documentation describes a setup that initially assigns the creator the entire distribution. An administrator can then finalize a list of up to ten recipient addresses. Each allocation must be positive, with all shares totaling 10,000 basis points.

That denominator represents the creator-fee pot being divided. An illustrative 6,000/4,000 split would allocate 60% and 40% of that pot; it would not give either recipient that percentage of trading volume.

The V2 update instruction, update_fee_shares_v2, replaces the list and revokes further administrative updates to that configuration. Teams following this workflow need to settle the recipients and proportions before finalizing, rather than assume they can keep editing the split.

The order of operations also matters. Before applying the new allocation, the instruction sweeps pending AMM fees when applicable and distributes pending creator fees to the existing recipients. The new list does not retrospectively reallocate that balance.

Subsequent distribution can be triggered by anyone, but the payout follows the addresses and proportions stored in the configuration. Permission to trigger a payment does not give the caller discretion over who receives it.

The rule has a defined scope. Pumpfun’s separate collection instructions cover coins that still have a single creator recipient and no shared-fee configuration. The V2 finalization limit should not be read as a description of every Pumpfun coin.

Ton’s framework is a proposal about who deserves the revenue. The shared-fee configuration records an executable allocation. For a project adopting such a framework, the practical check is whether its finalized addresses and shares match the recipients it has promised to pay.

/ Read more