Every new SPL and Token-2022 mint on Solana, the moment it lands

Two token programs run on Solana mainnet. The original SPL Token program at TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA carries the bulk of supply and the bulk of new mints. Token-2022 at TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb is the newer standard. Same shape at the surface, deeper feature set underneath.

From the InitializeMint perspective they look almost identical. Both take decimals, mint authority, freeze authority, and produce a fresh mint account. The differences live in the extensions Token-2022 supports:

• Transfer fees. The mint can skim a percentage on every transfer. The fee accumulates in a withheld balance the authority can withdraw later.
• Transfer hooks. Every transfer routes through a separate program, which can run arbitrary logic. The most common use case is compliance gating.
• Confidential transfers. Amounts are encrypted on chain. Useful for institutional flow, harder for indexers.
• Immutable owner. ATAs can't change owner. Removes a class of phishing attacks.
• Default account state. New accounts can start frozen by default and require explicit unfreeze.

For real-time tracking, that means a Token-2022 init is rarely a single instruction. It's an InitializeMint plus one InitializeXxxExtension instruction per active feature, all in the same transaction. The stream surfaces each, and the parsed event includes a flat extensions array so you don't have to walk the inner instructions yourself.

A mint is a number. A token, in the human sense, is a mint plus a name. The two come from different programs.

InitializeMint creates the on-chain account at a fixed PDA-derived address with a decimals byte and two authority pubkeys. That fires constantly. Many of those mints are program PDAs, ATAs that got their authority transferred, vault tokens, or other internal plumbing that never goes anywhere. Filtering on InitializeMint alone gives you a noisy firehose with a high false-positive rate if your goal is “new tradable tokens.”

The cleaner signal is CreateMetadataAccountV3 on the Metaplex Token Metadata program metaqbxxUerdq28cj1RbAWkYQm3ybzjb6a8bt518x1s. When someone pays the rent for a metadata account that names a token, they're telling you they want humans to find it. That single instruction carries name, symbol, URI (off-chain JSON with image and description), sellerFeeBps, the creators array, and an isMutable flag.

The combination is what you want. Subscribe to InitializeMint across both token programs, then within the same transaction or the next few slots, look for a CreateMetadataAccountV3 referencing the same mint. We do that correlation on our side and emit one merged event per token launch, so the stream you consume is clean by default. If you specifically want the unnamed-mints firehose (e.g. for detecting program-internal token issuance), filter to mints without a metadata sibling.

Pump.fun pioneered the “everything in one transaction” token launch on Solana. Their create instruction on 6EF8rrecthR5Dkzon8Nwu78hRvfCKubJ14M5uBEwF6P does an InitializeMint, a CreateMetadataAccountV3, and seeds a bonding-curve account. One signature, one slot, one ready-to-trade token.

That packaging matters because it changes what filters work. If you only watch SPL InitializeMint, you'll see Pump.fun launches but you won't know they're Pump.fun launches without checking signers. If you only watch Pump.fun, you miss everything else. We surface Pump.fun creates as their own event variant tagged source: "pumpfun" so the routing is trivial.

The bonding curve itself is interesting after the create. It moves token price along a deterministic function of supply, capped at a market-cap threshold (~$69k SOL-denominated at the time of writing) at which point Pump.fun graduates the token by burning the bonding curve and creating a real pool, usually on PumpSwap. For the full lifecycle, pair this stream with the dedicated Pump.fun Enhanced Stream and the Pool Creations stream.

Most new tokens are bad. That's the baseline. Useful risk detection isn't a single metric, it's a vector you build off the create event and the wallet behavior around it.

We don't score risk for you; we ship the raw signals. What you do with them is the difference between a useful product and a generic one.

The stream is a building block. Five places we see it land in production:

Sniper bots. Especially Pump.fun-only bots. Filter on the Pump.fun program, decode the create, place a buy in the same slot. The fastest entries we observe clock under 30ms from create to buy submitted.

Wallet apps. Phantom, Solflare, and Bull all need to label new tokens in real time so users see “BONK” instead of a base58 mint string. The combined SPL + Metaplex feed is the cleanest way to populate that label cache.

Risk-scoring services. Birdeye, DexScreener, and a handful of internal team tooling all consume similar streams to flag rugs before users buy. Mint authority, freeze authority, mutable metadata, and creator history are the inputs.

Indexers and analytics. Bitquery, Helius, and the rest of the analytics tier index every new mint into searchable tables. If you're building your own analytics product downstream, the stream is the ingestion source you want.

Memecoin trackers. Discord bots, Telegram alerts, and X automations posting every new launch with a quick risk summary. The stream firehoses cleanly into a low-latency message queue.