Pump fun is a Solana Memecoin Launchpad for Trading and Managing Token Holdings

Bonding-curve entry versus a PumpSwap fill

A Pump fun coin’s trading stage decides whether a buy meets the launch bonding curve or the graduated PumpSwap pool.

Before graduation, the bonding curve quotes against virtual SOL and token reserves under constant-product mathematics. There is no order book or off-chain matching step. A buy reduces the curve’s available token reserve, adds quote value, and moves the next price upward. After graduation, PumpSwap becomes the canonical venue and prices against pool reserves, including its effective quote-reserve field. Both mechanisms return the same Solana token to the buyer, yet their reserve states, fee schedules, and executable outputs differ.

Jupiter may route a graduated token through PumpSwap or another liquid venue, while Raydium may host an independent pool. Compare the final SOL debit and token output, not the venue label. Before graduation, the native curve remains the direct route; afterward, an aggregator becomes a meaningful alternative.

Preparing a SOL balance before the first buy

A usable SOL balance must cover the intended buy, Pump fees, Solana network fees, and enough residual SOL for the later sale.

One SOL contains 1,000,000,000 lamports, while Solana charges a base fee of 5,000 lamports for each signature. The protocol’s default compute-unit price is 0 micro-lamports, which makes the default priority fee 0 lamports, although a wallet interface can request a positive priority fee. A first Pump V2 trade may also initialize a 137-byte user volume accumulator with a documented 0.0018444 SOL rent amount. Phantom and Solflare show the estimated debit before signing. Preserve a separate SOL remainder because closing the position requires another transaction.

Pinning the mint before sizing the order

The mint address defines the Pump fun asset whose balance the wallet, token program, and explorer will record.

Solana’s Associated Token Program derives the user’s token account from three inputs: owner, mint, and token program. Newer Pump V2 coins use Token-2022, while legacy coins can use the original SPL Token Program. Pump trade instructions express the base token with 6 decimal places, so 1 displayed token equals 1,000,000 base units. The ticker and artwork remain metadata; the mint connects the quote, transaction, and resulting holding.

A standard Pump fun coin starts with 1,000,000,000 tokens, while Mayhem Mode creates 2,000,000,000 by minting an additional 1,000,000,000 tokens for its agent. Mayhem activity lasts for the coin’s first 24 hours and runs no faster than 1 trade per second for that coin. The agent burns its unsold balance after that window. Supply mode therefore belongs beside the mint address when interpreting position size.

Turning a SOL budget into a bounded buy

A Pump fun buy becomes controlled when the signed transaction caps SOL cost and names the token amount that the program should deliver.

Budget in SOL

For a coin still on the bonding curve, the total trading fee is 1.25%: 0.300% goes to the creator, 0.95% goes to the protocol, and 0% goes to liquidity provision. The buy’s maximum SOL cost includes protocol and creator fees. Treat the displayed total debit as the entry amount for recordkeeping, since subtracting only the quoted curve price understates the capital committed.

Maximum cost and token output

The Pump V2 buy instruction accepts an unsigned 64-bit token amount above 0 and a maximum quote cost. The token amount cannot exceed the curve’s real token reserves. The interface converts the readable SOL and token fields into base units, then the wallet presents the complete transaction for approval. A reserve change that pushes the required debit beyond the maximum causes the trade instruction to stop rather than spend through the cap.

Order size still matters inside the cap. A larger buy consumes more of the available reserve and receives a less favorable average fill than several smaller buyers saw earlier. Compare the final token output with the total SOL debit before signing.

How do you read the balance after a buy?

A completed Pump fun buy leaves three matching records: the token-account amount, the wallet display, and the transaction’s post-balance data.

Start with the transaction signature in Solana Explorer and confirm that execution finished without an error. Its token-balance fields identify the mint, owner, account index, raw amount, and decimal-adjusted amount. Next, read the associated token account through an RPC balance query or a wallet such as Phantom or Solflare. The raw integer prevents display rounding from hiding small units, while the six-decimal value supports ordinary position tracking. If one interface lags, the confirmed token account and transaction metadata settle the discrepancy without changing the holding.

Separating token count from position value

Pump fun position value follows the executable SOL quote for the chosen sale size, not the token count or a chart’s last trade.

Worked example: every changing input is hypothetical: the entry debit is 0.800 SOL including all entry costs, the received balance is 1,200,000 tokens, the full-sale executable quote is 0.900 SOL, and all sale and network costs total 0.018 SOL. Net sale proceeds equal 0.882 SOL. Subtracting the 0.800 SOL entry debit leaves 0.082 SOL, which is a 10.25% change on committed SOL. The calculation uses the executable quote because a displayed spot price does not include the full order’s price impact.

Resizing a holding without losing the reference point

A position resize should change the token amount deliberately while preserving enough SOL and a clear entry record for the eventual exit.

Adding to the holding

An additional buy creates a new transaction, a new SOL debit, and a larger balance in the same associated token account. Record each debit after platform and network costs, then sum those debits for total committed SOL. Divide that total by tokens still held only when a blended entry figure serves the intended record. A post-graduation addition uses PumpSwap reserves, so it should not inherit the earlier bonding-curve quote.

Trimming the holding

A partial sale sends an exact base-token amount above 0 and no greater than the wallet’s balance. Pump V2 also requires a minimum quote output after creator and protocol fees. Once confirmed, subtract the sold raw units, record net SOL received, and leave the remainder tied to the same mint. Trimming reduces exposure while retaining a token balance; a full sale replaces that choice with a complete exit.

What changes when a coin graduates?

Graduation moves a completed Pump fun bonding curve into its canonical PumpSwap pool automatically and irreversibly, so later trades quote a different reserve state.

The platform fee schedule assigns 0.015 SOL to the graduation action. For SOL-denominated canonical pools, the first market-cap band runs from 0 to 420 SOL and charges 1.25% total: 0.300% creator, 0.930% protocol, and 0.020% liquidity-provider fees. At 98,240 SOL and above, the schedule charges 0.300% total, divided into 0.050% creator, 0.050% protocol, and 0.200% liquidity-provider fees. The program selects the applicable band from the pool’s SOL-denominated market cap.

Graduation does not replace the holder’s mint or associated token account. It closes the curve and migrates its liquidity atomically into the protocol-owned canonical pool. Refresh the quote because the venue, reserve balances, and fee band have changed. Jupiter can compare available routes after graduation, while a direct PumpSwap fill remains the canonical alternative.

Setting the sale floor around price impact

The sale floor decides whether a Pump fun exit executes: minimum SOL output must remain below the program’s fresh post-fee quote.

After that point, Pump V2 represents the minimum output as an unsigned 64-bit quote amount after creator and protocol fees. For native SOL, 1 output base unit is 1 lamport; a floor of 0 removes output protection entirely. The executable quote falls as the sale becomes large relative to available reserves, since the constant-product curve moves during the order. Requote immediately before signing, review the final minimum, and decide between one full exit or smaller partial sales. A tighter floor favors price control, while a wider floor favors execution.

Closing the position and checking settlement

A Pump fun position closes cleanly when the sale is confirmed, the SOL credit is verified, and the selected mint has a zero raw balance.

Confirming the SOL credit

Use the sale’s transaction signature to inspect status, pre-balances, post-balances, and token-balance changes in Solana Explorer. Solana executes a transaction atomically: every included instruction succeeds, or none of its state changes remain. Network fees are still charged when execution fails, so a submitted signature alone does not prove a sale. A successful full exit shows the expected token account falling to zero and the wallet’s SOL increasing by net proceeds after the trade and network charges.

The wallet notification is convenient. Confirmed on-chain metadata is the settlement record that closes the position ledger.

Resolving residual token units

Readable wallet rounding can display zero while a few six-decimal base units remain. Selling the exact raw balance removes that ambiguity. The associated token account can then stay open with a zero balance, or its owner can close it and send the rent lamports to a chosen destination. Account closure is a separate Solana token instruction, not part of the economic sale unless the interface bundles it. A zero balance closes the holding; closing the account also clears its storage.

The on-chain mechanics behind the lifecycle

Under the interface, the Pump fun lifecycle is a sequence of signed Solana instructions that update reserve and user token accounts atomically.

The bonding-curve buy carries a base-token amount and maximum quote cost; its sale carries a base-token amount and minimum quote output. PumpSwap follows the same decision boundary through exact base inputs and quote limits. The Associated Token Program supplies the user’s account, while Token-2022 or the SPL Token Program moves the balance. Solana caps a serialized transaction at 1,232 bytes and compute at 1,400,000 units. A non-built-in instruction receives a 200,000-unit default, while a built-in instruction receives 3,000. These constraints explain why wallet interfaces compose, simulate, and sometimes split lifecycle actions.