Launch programs
Which programs launch tokens, and which only look like it
Reading every block on Solana finds every token creation, and most of them are not launches. This is the list of programs we have identified, with the evidence for each, so that a reader can check the label rather than take it. It is incomplete by construction and grows as programs are identified.
A program absent from this list is one we have not identified. That is not a statement that it launches nothing, and a mint from such a program is checked against the published test instead.
Programs that create launches
4 identifiedTwo of these are engines rather than launchpads: shared bonding-curve programs that many front-ends build on, so one entry covers many brands. The brand names those front-ends register are permissionless and self-asserted - some claim to be pump.fun, which does not run on either - so they are recorded as behaviour and never published as identity.
| Program | How we know | Confirmed |
|---|---|---|
| pump.fun 6EF8rrecthR5Dkzon8Nwu78hRvfCKubJ14M5uBEwF6P |
Watched. The collector holds a subscription to this program and this archive contains its launches. The venue this archive began with. Its events are decoded directly, not inferred, and every launch recorded before 2026-09-11 came from it. source | 2026-09-11 |
| Raydium LaunchLab LanMV9sAd7wArD4vJFi2qDdfnVhFxYSUg6eADduJ3uj |
Watched. The collector holds a subscription to this program and this archive contains its launches. Named in Raydium's own program-address documentation and shipped as `raydium_launchpad` in their IDL repository. Multi-tenant: 2,231 PlatformConfig accounts are registered against it, each a front-end with its own brand and fee split, so one entry covers letsbonk.fun, cook.meme, StonkFun and the rest. Those names are permissionless self-asserted strings and are deliberately not published as identity - some configs claim to be pump.fun, which does not run on this program. boop.fun was named here until 2026-09-12 and does not belong: it runs its own program, boop8hVGQGqehUK2iVEMEnMrL5RbjywRzHKBmBE7ry4, declared as the address in its own IDL repository and verified executable on chain. It launched nothing in any window we sampled, so the error cost no coverage - but a front-end attributed to the wrong program is a claim about identity, which is the one thing this page exists to get right. source | 2026-09-11 |
| time.fun BcyCjbQYxE2m2xTZ5tTZXDEz8Up7avTmPqhzCrASRKiQ |
Identified, not watched. This archive holds no launch from this program: it is listed because we know what it is, not because we cover it. Its own Anchor program, established on chain rather than from documentation - there is no published IDL anywhere, and the on-chain IDL account is absent, checked against pump.fun and Meteora DBC as controls. Not a front-end on either engine: it ran its own curve and graduated into a Raydium CPMM pool, and that pool's `pool_creator` is time.fun's own admin wallet. Quoted in USDC with a 37,500 USDC curve target, so no SOL figure applies to any launch on it. A companion program sits at CvejZauwmDWzNqwhPhPDUetP1ZwCPPpSQ5we2KVf6o3e. DEAD: shutdown announced 2025-11-05, no launch after 2025-11-17, last successful program transaction 2026-03-13, front end no longer resolving as of 2026-09-12. 893 markets over its life. This archive never watched it, so it holds no launch from it - which is what an absence on this list would otherwise have implied the opposite of. | 2026-09-12 |
| Meteora Dynamic Bonding Curve dbcij3LWUppWqq96dh6gJWwBifmcGfLSB5D4DuSMaqN |
Watched. Read out of every block by the chain scanner, whose events for this program exist only inside its transactions' inner instructions, and this archive contains its launches. Declared as the mainnet program id in MeteoraAg's own Anchor.toml. Infrastructure rather than a launchpad - Meteora ships no consumer front-end on it - with 494,724 PoolConfig accounts and 574 partner records. Emits no `Program data:` logs at all, using Anchor emit_cpi! exclusively, so a log-reading collector sees nothing from it. source | 2026-09-11 |
Programs that create token mints that are not launches
7 identifiedListed because naming them is what stops them being re-investigated every time an unfamiliar address appears at the top of a ranking. One of these led a 596-block sample at 49.3% of all token creations and launches nothing whatsoever.
| Program | How we know | Confirmed |
|---|---|---|
| unidentified outcome-market program BopTVfs428fBBX2vf28FgdAjzX5F8vAhsaG3SrCs4rHm |
Identified by behaviour, not by name. Its deployed code names binary_option markets, with maker, market, direction, outcome_mint and quote_vault fields. Measured 2026-09-15: 3,000 of its transactions in 65 minutes, and every one of 30 sampled across them was paid by the same wallet. Each market creates Token-2022 outcome mints with supply 0, a permanent delegate and a close authority beside a USDC vault, and closes them about 16 minutes later (42 timed: median 946 s, longest 966 s). Each of those mints appeared in exactly two transactions, its creation and its closing, so none was minted or traded while it existed. It led one 596-block sample at 49.3% of all token creations and launches nothing. Not a verified build, no security.txt or IDL in the deployed program, and not named in any public source we found. An earlier version of this note said the mints were closed in the same transactions that created them; timing them showed otherwise. We record what it does and do not name the product. | 2026-09-15 |
| prediction market prediCtPZCttYMvm2W3PtxmMxLmT1dtN7riU6Cxh6tM |
Mints outcome tokens, which are positions in a market rather than launched tokens. Every mint sampled carried supply 0. | 2026-09-11 |
| Meteora CP-AMM cpamdpZCGKUy5JxQXB4dcpGPiikHawvSWAd6mEn1sGG |
Mints liquidity-pool tokens at 0 decimals. A pool is created because a launch graduated into it; the pool token is not itself a launch. | 2026-09-11 |
| Raydium CLMM CAMMCzo5YL8w4VFF8KVHrK22GGUsp5VTaW7grrKgrWqK |
Mints position NFTs at 0 decimals, one per liquidity position. | 2026-09-11 |
| Orca Whirlpools whirLbMiicVdio4qvUfM5KAg6Ct8VwpYzGff3uctyCc |
Mints position NFTs at 0 decimals, one per liquidity position. | 2026-09-11 |
| PumpSwap AMM pAMMBay6oceH9fJKBRHGP5D4bD4sWpmSwMn52FMfXEA |
pump.fun's own AMM. Mints pool tokens for launches that have graduated off the curve. | 2026-09-11 |
| Metaplex Token Metadata metaqbxxUerdq28cj1RbAWkYQm3ybzjb6a8bt518x1s |
Not a venue at all. It appears as the outermost program in some creation transactions and is an attribution artefact rather than a launchpad - the reason this archive labels the creating program and never treats that label as identity. source | 2026-09-11 |
Why the label is never an identity claim
A mint is attributed to the outermost program in its creation transaction that is not infrastructure. That is a useful label and a bad identity: trading terminals and routers wrap other programs and appear outermost, and this archive has been wrong that way twice - once on a terminal's vanity address in the funder tracer, and once on a router mistaken for a launchpad's own instruction set. So the program is recorded as a fact about the transaction, this page records what we have since identified, and neither is presented as a claim about who operated a launch.