pump-fun

v3 smaller account list of pump is a welcome cleanup Pump's V3 docs bring buy_v3, buy_exact_quote_in_v3 and sell_v3 down to 17 accounts, compared with 26 or 27 for their V2 equivalents. That's fewer accounts to pass into a trade instruction. Pricing and slippage checks stay the same, and so do fee amounts. github.com/pump-fun/pump-public-docs/blob/main/do… Protocol and creator fees accumulate on the bonding curve before being swept. The buyback portion still gets paid during the trade. For indexers, the balances are in BondingCurve.protocol_fees and BondingCurve.creator_fee, with the later payouts to reconcile against them. I also like that legacy and V2 instructions keep working. Builders can use the smaller instructions where supported, while cashback coins continue using V2.

Checking out the GitHub for pumpfun (link below) and the CA for $FR is in there. Genuinely curious what’s going on lmao Coin’s at 6k rn $FR Coyj3LtKn1BNSgWc9HsGK5SKoGfEoDaymig4wrN6pump github.com/pump-fun/pump-public-docs/blob/main/do…

Holy fuck in new pumpfun git update THEY GAVE US A COIN THE Q COIN ELONCOIN AT 3M, THIS HAS TO BE A RUNNER NOT LARP Check for yourselves github.com/pump-fun/pump-public-docs/blob/main/do… t.co

Pump and LaunchLab: which accounts define creator-fee rights after graduation? The creator-fee docs are a useful part of a launchpad comparison if you’re building an indexer or a claims interface. Pump’s V2 sharing config supports up to ten recipients. The documented update instruction sets the final shares and revokes further admin updates. Its AMM sweep instruction moves accrued creator fees into the Pump creator vault for distribution through the sharing config. LaunchLab’s guide calls out an August 17 policy change for Fee Key ownership. For migrations under the newer policy, the platform receives the combined platformScale + creatorScale position; older creator Fee Keys remain unchanged. Creator revenue through CPMM fees depends on the recorded pool creator and the selected configuration. I’d want an interface to show the recipients, their percentages and who still has permission to change anything. The relevant program version and migration date belong there too. Anyone indexing both systems already? Which on-chain fields do you treat as authoritative for the claim rights? Pump: github.com/pump-fun/pump-public-docs/blob/main/do… Raydium: docs.raydium.io

I just found a token on @Pumpfun official github, they were showing how mints work and used this ca as an example: 3cLSxG6eXcCD9NSMawkhUcrvVCUC8KHKHMCxx6bhpump see for yourself: github.com/pump-fun/pump-public-docs/blob/main/do… t.co

Pumpfun has official agent skills now Was digging through Pump’s GitHub and found an skills repo for AI agents. It covers creating coins, swapping across the curve/PumpSwap, distributing creator fees and verifying agent payments onchain. Most “AI x crypto” tooling still ends at fetching prices. This can actually compose transactions. Anyone here wired these into Claude or Codex yet?

Imagine fading solana:pumpCmXqMfrsAkQ5r49WcJnRayYRqmXz6ae8H7H9Dfn memecoin $sharkcoin that deployed by @pumpfun @a1lon9.. $Sharkcoin CA: AcmjBHk6H1Y1H5USZpdEwim7BRGdmEkfLprtJQiWPJCS 9k not even bonded yet.. early! github.com/pump-fun/transfer-hook-authority/blob/… solscan.io @solana @sapijiju

@Pumpfun @a1lon9 Extra proofs: github.com/pump-fun/transfer-hook-authority/blob/… solscan.io $Sharkcoin ca: AcmjBHk6H1Y1H5USZpdEwim7BRGdmEkfLprtJQiWPJCS t.co