The Pump.fun bonding curve is a per-token account, derived from the seeds bonding-curve and the mint, that prices the token from virtual and real reserves. Buys add quote and remove tokens, sells do the reverse, and when the real token reserves reach zero the curve is marked complete and its liquidity can migrate to PumpSwap.
The curve account#
This is a real curve account, read from mainnet at slot 470,920,792 a few minutes after its token launched, and decoded with the official IDL. All 166 bytes decode, starting with the account's 8-byte discriminator.
| Field | Value | What it means |
|---|---|---|
virtual_token_reserves | 1,073,000,000,000,000 | the token side of the pricing pair |
virtual_quote_reserves | 3,260,618,071 | the quote side of the pricing pair |
real_token_reserves | 793,100,000,000,000 | tokens the curve can still sell |
real_quote_reserves | 4 | quote actually collected so far |
token_total_supply | 1,000,000,000,000,000 | all tokens ever minted for this coin |
complete | false | still trading on the curve |
quote_mint | a mint other than wrapped SOL | this coin is priced in another token |
depth | 0 | paired with a listed quote mint, not another Pump.fun coin |
creator_fee_bps | 30 | its own creator fee rate, which only custom pairs have |
is_holder_reward | true | creator fees go to holders instead of a creator wallet |
Amounts are in base units. The token has six decimals, so the total supply is one billion tokens and the curve still holds 793.1 million of them to sell.
Virtual and real reserves#
Pump.fun's documentation describes the pricing formula as based on Uniswap V2, using synthetic reserves so that a coin has liquidity from its first trade. The virtual pair sets the price; the real pair records what is actually in the curve. A fresh curve starts with the virtual reserves copied from the program's global settings and nothing real on the quote side, which is why the example above has collected almost nothing yet while its virtual quote reserves are already in the billions of base units.
The real token reserves start below the total supply: the tokens that are never sold on the curve are the ones that later seed the PumpSwap pool.
How buys and sells move the curve#
The documentation states the rule exactly. A buy increases the virtual and real quote reserves by the same amount and decreases the virtual and real token reserves by the same amount; a sell does the reverse. So the difference between virtual and real reserves stays constant for the life of the curve, and every trade shows up as a matching change on both pairs.
The trade instructions carry only the trader's limits: the tokens wanted and the most they will pay, or the amount they will pay and the fewest tokens they will accept. The amounts actually exchanged come from execution, through the program's trade events or the curve account's new state.
Completion and migration#
complete turns true at the end of the buy that takes the real token reserves to zero. From then on the curve refuses trades. Migration moves the liquidity to a new PumpSwap pool, and the documentation describes the migrate instruction as permissionless and idempotent: anyone can run it on a completed curve, and running it twice does nothing more.
Newer buys add a twist the documentation calls synthetic migration. With buy_v3, buy_exact_quote_in_v3 and multi-hop routes, the buy that empties the curve may keep going: it takes what the curve has left, completes it, then buys the rest at the price the future pool would charge, and migrate_v2 creates the pool from exactly the reserves that buy left behind. So the last buy on a curve can be larger than the curve itself.
Following a curve from shreds#
From shreds you see the instructions that touch a curve as they are broadcast: the launch, each direct buy and sell, and the migrate call. Each one names the curve account, so you can group a token's whole life by that one address. What shreds do not give you is the curve's state; reserves change during execution, so read them from the account or from the program's events once the trade has run. The Pump.fun recipe decodes the instructions, and detecting new tokens weighs the ways to spot launches.
Questions about the bonding curve#
How do I find a token's bonding curve account?#
Derive it: it is the program-derived address of the seeds bonding-curve and the mint, under the Pump.fun program. Every launch and trade instruction also lists it.
Why does my decoder fail on an older curve account?#
Fields were appended over time. The documentation says accounts written before a field existed are shorter, and the missing trailing fields should be read as zero, false or the default key.
Is migration automatic?#
The curve completes automatically on the buy that empties it. The migrate instruction itself is a separate call that anyone can make.
What the curve account will not tell you#
The account is a snapshot. It does not record who traded, at what price each trade filled or when the curve completed; those come from the trade events and the transactions. And shreds do not carry the account's state at all, only the instructions that changed it, so a curve's live reserves always need execution data or an account read.
Decoding the instructions that move it#
The Pump.fun recipe turns launches, buys and sells into events, the PumpSwap recipe follows the token after migration, and a launch byte by byte walks through one create. Swaps on other venues share a shape described in reading a DEX swap; to watch curves fill on your own feed, see pricing.
Sources#
- pump-fun/pump-public-docs docs/PUMP_PROGRAM_README.md, commit 639b87f: bonding curve, reserves, complete, migrate (checked 2026-11-18)
- pump-fun/pump-public-docs docs/SYNTHETIC_MIGRATION.md, commit 639b87f (checked 2026-11-18)
- pump-fun/pump-public-docs docs/instructions/CREATE_WITH_PUMP_COIN_QUOTE.md, commit 639b87f: depth (checked 2026-11-18)
- pump-fun/pump-public-docs idl/pump.json, commit 639b87f: BondingCurve type (checked 2026-11-18)
- Bonding curve account BWPaVcPtbYwmHQ3tckvxR8XnuYLwRyRLs3ZFvagbSJ7P read with getAccountInfo at slot 470,920,792 (checked 2026-11-18)
Raw shreds on your own server
Ultra Low Latency Shreds is $200 and Standard Shreds is $100. You pay in crypto, tell us which IPv4 address and UDP port should receive the stream, and we wire it up by hand.