On-chain intelligence for Solana launches

Every launch leaves a print.

Launchprint reads what a token launch's rules allow and who is really trading it — before the first buy.

Get API access Try the Telegram bot

Live on Meteora DBC · Raydium LaunchLab coming soon

Move the lens over the tracks. What looks like a crowd is often one hand.

01 — The problem

A token with volume that graduated tells you almost nothing.

Configs nobody reads

Launch rules decide who gets the liquidity, the leftover supply and the fees after graduation. Buyers never see them.

Volume that isn't real

Dozens of wallets, one hand behind them. Farms, fan-out sellers and proxy signers look like an organic crowd.

Risk visible too late

Most tools need trading history. The rules are on-chain from the first second — before anyone buys.

02 — How it works

Two questions, answered for every launch.

Rules first, behaviour second. Each verdict lists the flags that scored, what counts in the launch's favour, and context that does not score.

1known before the first buy

What do the rules allow?

Read from the config account the moment it is created: who gets the liquidity after migration and whether it is locked, how much supply goes to a leftover receiver, the migration fee, how the trading fee is set and shared.

2confirmed by observed trading

Who is behind it, and is the trading real?

Trades are compared with the creator's transfers and with wallets that recur across launches. New configs are linked to known operators through shared addresses.

03 — Verdicts

Five verdicts. Every one explained.

GREEN: No major red flags in the rules or observed trading.
SELF-GRAD: Instant or self-funded graduation, no real market on the curve.
AMBER: Risky rules or suspicious but inconclusive trading; visible before buying.
RED: Synthetic launch: trading dominated by the creator and linked wallets.
RED-LINK: Rules linked by specific addresses to a known synthetic-launch operator, flagged before the first trade.

Labeling principles

Losses alone are never a reason for a negative verdict.
A risky setting gives AMBER, never RED.
RED requires observed behaviour.
Verdicts are about one config, never a whole launchpad.
Operator addresses are never published.

In a permissionless market someone wins and someone loses in every launch. A verdict says what a config allows and what was actually observed in its pools.

04 — Patterns we detect

The same few setups keep recurring.

Each was traced end to end — every transaction of the bonding curve and of the pool after graduation.

Bundle launch

The curve is bought out in seconds, tokens are fanned out to fresh wallets that sell back into the pool.

Proxy signers

Dozens of wallets sign the trades, but one wallet that never signs funds every buy and receives every sale.

Instant graduation

The migration threshold is about zero: the token goes straight to an AMM pool with the creator's own SOL.

Sniper fee

The trading fee starts at 70–99% and decays over minutes — and most of it goes to one address.

Closed arenas

Hundreds of creators and a fixed pool of wallets trade each other's tokens within seconds of launch.

Migration fee traps

99% of the SOL raised on the curve goes to the fee receiver at graduation, 1% into the pool.

05 — By the numbers

What one window of mainnet looks like.

launches analysed

configs

synthetic (RED)

instant graduation

Meteora DBC, ~68 hours, Oct 8–11 2026. Config capability read for every launch; trading evidence from a sample of pools.

06 — Platforms

One verdict format across venues.

Operators move between launchpads. Wallet links follow them.

Live

Meteora DBC

Config capability, trading behaviour, operator links.

In development

Raydium LaunchLab

Platform configs, bonding-curve trading.

Planned

Raydium AMM / CPMM

Liquidity removal, post-migration pools.

Planned

More venues

Following where launches move.

07 — For builders

A verdict is one request away.

A JSON API with the same verdicts as the bot. Public reads are free; on-chain lookup of any address and full addresses come with a key.

LaunchpadsShow users that your configs are clean, and spot operators abusing your platform.
Terminals & walletsOne API call per token — the same verdict as in the bot.
Trading botsA verdict before the buy, not after the dump.
Liquidity providersCheck whether the creator can still pull unlocked liquidity from a pool.

curl https://api.launchprint.xyz/v1/check/<token-or-pool-address>

response.json

{
  "kind": "launch",
  "venue": "dbc",
  "verdict": "AMBER",
  "flags": [
    {
      "code": "migration_fee_high",
      "text": "99% of raised SOL goes to the fee receiver at migration"
    }
  ],
  "launch": {
    "token": "7Vert…pump",
    "created_time": 1791261146
  }
}

GET/v1/check/{address}Verdict and flags for a token or pool address.

GET/v1/latestMost recently analysed launches.

GET/v1/statsAggregate verdict counts per venue.

GET/v1/healthService and indexer status.

Read the API docs

08 — Pricing

Start free. Scale with a key.

Free

For traders and quick integrations.

Public verdicts and flags
Indexed tokens, pools and configs
Rate-limited per IP
Operator addresses hidden

Try the bot

Pro

Launchpad

For platforms that issue configs.

Monitoring of your config keys
Webhooks on new RED / AMBER
Config review and tuning
Direct support channel

Let's talk

Payments in USDC or SOL.

09 — FAQ

Questions we get.

10 — Contact

Building a launchpad or a terminal? Let's talk.

API keys, config monitoring and integrations — usually a reply within a day.

info@launchprint.xyz @launchprint_xyz Telegram bot