Selling Pump.fun Tokens: The Exit Side of a Snipe

Buying a pump.fun launch is half of a sniper bot's trade. The other half — the exit — is where the trade actually becomes profit, and it is the side most bots get wrong. This guide covers how a pump.fun sell actually works on-chain, what changes for mayhem-mode launches, and how to wire the full buy-to-exit loop through one RPC provider.

The Short Answer

A pump.fun sell is a single instruction against the token's bonding curve: you transfer tokens into the curve's associated token account and receive SOL at the curve's live price, minus protocol and creator fees. The instruction requires the seller's token account, the curve state, the fee recipients, and a slippage-guarded minimum SOL output. Standard launches and mayhem-mode launches use different fee recipients and fee-tier schedules, so a sell builder has to resolve both per-mint. End-to-end, the working loop is: detect the launch → build the buy → sign and submit → confirm landing → build the sell → sign and submit → confirm the exit.

How a Pump.fun Sell Works On-Chain

When a token launches on pump.fun, a bonding curve account holds the token's real reserves and virtual reserves. A buy moves SOL into the curve and mints tokens out; a sell reverses it — tokens flow back into the curve's token account and SOL flows to the seller, priced by the constant-product formula over the virtual reserves.

Every sell pays two fees, deducted from the SOL proceeds:

Protocol fee — routed to a protocol fee recipient named in the sell instruction's accounts.
Creator fee — routed to the launch's creator, at a rate configured per curve.

The instruction also carries a minimum SOL output — your slippage guard. The curve program reverts the whole transaction if landing would return less than that minimum, which is what protects a sell from sandwich attacks and price movement between quote and landing.

What Changes for Mayhem-Mode Launches

Mayhem-mode is pump.fun's newer launch format. Three things differ from a standard launch, and each one breaks a naive sell builder:

Token-2022 mints. Mayhem tokens use the Token-2022 program, so the seller's and curve's token accounts are Token-2022 ATAs, and the sell's transfer instruction is TransferChecked with explicit decimals.
A different protocol fee recipient. Mayhem curves route the protocol fee to a dedicated mayhem fee recipient rather than the standard global one. A sell that names the standard recipient fails on-chain with an authorization error.
Fee tiers by market cap. Mayhem sells select protocol and creator fee rates from a tiered schedule based on the launch's market cap at execution time, and the token's supply lives in the mint account rather than the curve constant.

A correct sell builder resolves all three per-mint, at quote time, from live chain state.

The Full Loop: Detect, Buy, Exit

A sniper bot's cycle through one trade:

Detect — subscribe to a real-time launch feed (a Geyser-backed stream, not a polling loop) and decode the mint.
Buy — request an unsigned buy transaction against the live curve state, with the SOL budget and slippage bound. Sign it with your wallet and submit.
Confirm — poll the transaction signature until it's confirmed. Never assume landing; a launch slot is the most contested block space on Solana.
Exit — request an unsigned sell for the tokens now in your wallet's token account, sign, and submit.
Confirm the exit — verify the SOL proceeds landed.

The buy and the sell are the same shape of operation at the RPC level: the provider builds the transaction against live state (curve reserves, fee schedule, your token balance), and your wallet signs and broadcasts it. The provider never takes custody of keys.

Choosing RPC for Both Sides

Most sniper-bot infrastructure comparisons stop at detection latency and landing paths — the buy side. The exit side needs the same properties:

Live curve and fee-state reads — a sell quoted against a stale curve state produces a minimum output the on-chain program will reject, killing the exit at the worst moment.
Per-format support — a builder that handles only standard launches will strand a position on a mayhem-mode token: the sell has to resolve the fee recipient, fee tiers, and Token-2022 accounts correctly for that format.
Fail-closed inventory checks — the sell should verify the wallet actually holds the tokens before building and billing, so a failed exit attempt is free.
Per-use billing — a trade cycle makes a handful of calls at unpredictable moments; per-call credit billing keeps the cost proportional to actual trading.

Where Nodius Fits

Nodius pairs a decoded launch-signal firehose with an RPC that builds both sides of the trade — executeSnipe for the buy and executeSell for the exit — against live bonding-curve state, including mayhem-mode launches. Both return unsigned transactions your wallet signs and submits; a funded keypair is the account, with per-call credit billing and no signup step.