Pump Lineage

Live family tree of pump.fun tokens launched on custom pairs: who is paired to whom, and how every token settles in SOL.

CATBA Connecting…

Latest launches

Hot parents

Family

SOL graduated on curve bypass pool flagged creator
Data: on-chain pump.fun launches (create_v2 with a non-SOL parent), prices from bonding curves and DexScreener. Market cap assumes a 1B supply. See Docs for how to read the map.

Docs

What this is

Pump.fun now lets a new token launch against another token instead of SOL. Pump Lineage indexes every such launch on-chain and draws the result as a family tree: each token, the parent it trades against, and the path that eventually ends in SOL.

The tree matters because a custom pair is not just a label. Money has to pass through the parent to reach the child, so families of tokens move together, share risk, and leave traces that are invisible on a normal price chart.

How a custom pair works

A buyer still pays in SOL. Pump.fun's router does two swaps inside one transaction: SOL into the parent on the parent's bonding curve, then the parent into the child on the child's curve. The child's curve holds the parent token as its reserve.

Walletpays 1 SOL Parent curvereserve: SOLRARI / SOL Child curvereserve: RARIA / RARI Atokens SOL RARI one transaction, routed by the Pump App program step 1: buys the parentstep 2: buys the child
Every child buy is also a parent buy. Real example: Coin A (pair A/RARI) was created this way on 8 Oct; its launch transaction swapped SOL into RARI, then RARI into A.

Chains can be deeper: a grandchild routes SOL → grandparent → parent → child. The explorer's Path to SOL shows that route for any token.

Reading the explorer

  • Latest launches. Every new custom-pair token, newest first, with its parent. A dev 40% or serial ×5 chip means the creator is flagged (see Creator flags).
  • Hot parents. Tokens ranked by how many children launched on them in the last hour, 24 hours, or ever. This is the fastest way to spot where new money is being routed.
  • Family tree. The selected token's whole family, from SOL on the left to the youngest generation on the right. The stripe on each card is its stage: purple SOL, amber still on the bonding curve, green graduated to PumpSwap. The label on each edge is the child's price in its parent token.
  • Markers. A filled orange dot means the token also trades against SOL in a separate pool, bypassing its parent. An orange ring means its creator is flagged.
  • The ≈ sign. Prices marked ≈ are derived: price in parent × parent's USD price. Market cap assumes pump.fun's standard 1B supply.

Hidden demand on parents

Because every child buy passes through the parent, a parent that suddenly gains many children is receiving buy pressure that nobody announced. On the parent's chart it looks like an unexplained rise; in the tree you can see where it comes from.

IllustrativeChild launches lead the parent's price. Bars are children launched per hour; the line is the parent's price, indexed to 100. Not real data: a sketch of the pattern to look for in Hot parents → 1h.

How to use it: sort Hot parents by 1h. A parent with several fresh children and a still-flat price is worth a closer look; a parent whose children stopped launching is losing that support.

A child is leverage on its parent

A child's USD price is its price in the parent multiplied by the parent's USD price. If the parent halves, the child halves in dollars even if nobody sells the child. If child holders also start leaving, the two effects stack.

IllustrativeThe child falls further than the parent. Parent price drops 50% over six days; the child's price in the parent drifts down 10%. In USD the child loses 55%. Not real data.

The deeper the branch, the more tokens your position depends on. Check Path to SOL before buying: every hop is another price that can move against you.

Price gaps and bypass pools

Bots often open a second pool for a child directly against SOL, usually on Meteora. Now the same token has two prices: through the parent, and through the bypass pool. They drift apart because few people arbitrage tiny pools.

SOL HKparent, PumpSwap Meteora poolbypass, $1 liquidity testchild of HK ≈ $3.8k mcap ≈ $9.4k mcap
Same token, two prices, 2.5× apart. Real snapshot of test on 8 Oct: via its parent HK it was worth about $3.8k; on its Meteora bypass pool, about $9.4k. With $1 of liquidity this is a signal rather than a trade, but on larger families the same gap can be real arbitrage.

Bypass pools also weaken the link to the parent: buyers who use them send nothing up the family. A family where most volume runs through bypass pools supports its parent less than the tree suggests.

Creator flags

Each launch records its creator and how much of the supply the creator bought in the launch transaction. Two patterns are flagged:

  • Big dev buy dev 40%: the creator ended the launch holding 20% or more of the supply. Whoever holds that much can sell into every later buyer.
  • Serial launcher serial ×5: one wallet launched three or more children of the same parent. A common way to pump a parent you already hold: launch children with large first buys, each of which buys the parent, then sell the parent.
Creatorholds the parent Parentprice pushed up Child 1dev 35% Child 2dev 40% Child 3dev 30% launches + first buyeach buy routes into parent
The serial-launcher pattern. One wallet launches several children with large first buys; each buy is routed into the parent the wallet already holds. In the explorer these children carry serial ×3 and the tree shows them with an orange ring.

Real reference point: when Coin A launched on RARI, its creator authorised up to 6 SOL and took roughly 40% of A's supply in the launch transaction. That alone would earn a dev 40% flag.

A third label, bot ×140, marks wallets that launched 20 or more children of one parent with no first buy. That pattern looks like an automated launcher or a launch service rather than someone pumping a parent they hold.

A flag is a reason to look closer, not proof of bad intent. Some creators buy a large share to stop snipers. Others just like their own token.

Which tokens people choose as parents says what the market treats as money this week. A meme that collects children across many unrelated creators is turning into a base currency for a community, which is a different and stronger signal than price alone. Watch Hot parents → 24h over several days to see these shifts.

Testing a layered ecosystem

If you plan a project where every new token is paired to the previous one, the tree lets you measure how real families behave before you launch: how many children survive a day, whether new launches lift the parent, how deep chains get before liquidity runs out, and how much volume leaks into bypass pools instead of flowing up to the root.

What to build on top

  • Alert bot. “8 children launched on X in the last hour”, “wallet Y launched 5 children of its own token”, “price gap above 50% between parent route and bypass pool”.
  • Data API. The family graph as an endpoint for trading bots and dashboards.
  • Featured families. Paid placement for communities that want visibility for their tree.

Limitations

  • The feature is new. Most families are micro-caps with tens of dollars of liquidity; numbers move fast and can be thin.
  • Prices on the bonding curve are read on-chain; graduated tokens, trade counts and bypass pools come from DexScreener, which can lag by minutes.
  • The index covers launches seen since the indexer started, plus optional history backfill. Pump.fun can change or close custom pairs at any time.
Nothing here is financial advice. Many tokens on pump.fun are launched so their creators can sell to later buyers; the tree helps you see structure, not predict outcomes.

Methodology

  • Detection. The indexer subscribes to the pump.fun program (6EF8rr…F6P) and decodes every create_v2 instruction (discriminator d6904cec5f8b31b4), including calls made from inside the Pump App router. A launch with 17 or more accounts is a custom pair; account 17 is the parent mint, account 3 the child's bonding curve.
  • Price in parent. From the child's curve: (virtual quote reserves / 10^parent decimals) ÷ (virtual token reserves / 10^6), refreshed every 20 seconds.
  • USD. Root parents on a SOL curve: curve price in SOL × SOL/USD. Graduated tokens: DexScreener. Children: price in parent × parent USD, marked ≈.
  • Dev buy. The creator's balance of the new token at the end of the launch transaction, as a share of 1B supply.
  • Names. Token metadata via the RPC's asset API, falling back to DexScreener.