Launch alerts

Launch alerts are the product. Every card you receive is one.

A token goes from "a transaction landed on-chain" to "a briefing in your Telegram" through five stages. Knowing them tells you what an alert can and cannot possibly know.

1. Detection

We subscribe directly to the creation events of every venue we cover — Uniswap V4 and V3, Aerodrome, Clanker, Zora, Virtuals, Flaunch and Base.fun on Base; Pons and LaunchHood on Robinhood Chain. No aggregator sits in between, so a launch is seen when the transaction lands.

At this point we know almost nothing: an address, a pool, a deployer.

2. Admission

A token enters the pipeline once it has a paid DexScreener profile. Someone connected to the project has to spend money first.

This is the gate that costs you most of your latency, and it is the reason a median alert lands 22–56 minutes after the pool exists rather than 22 seconds. It is a crude filter. It is also the only one we have found that reliably separates a token somebody cares about from the thousands of throwaway contracts deployed daily. Coverage sets out the trade honestly, including what it makes us miss.

3. Enrichment

Everything that costs time gets done here, in parallel:

• The nine-layer safety stack — including a live buy→sell simulation
• Deployer trace — wallet age, funding source, prior launches, prior rugs, prior winners
• Holder distribution, contract-versus-wallet classified
• Insider allocation and how much of it has already been sold
• Social read — who is posting, what reach they have, how coordinated it looks
• Product evidence — repository, whether it predates the token, docs, paper, audit

Anything that fails here stays empty. It does not get a default value. That matters downstream: an unmeasured round-trip earns no credit in the score, rather than the small benefit-of-the-doubt it used to get.

4. Scoring

Two independent scores, answering two different questions: the conviction score for substance, and the trade label for momentum. Neither is derived from the other.

5. Delivery

The card is rendered once by the pipeline and stored. Your filter runs separately, in a different process that shares no code with the pipeline — which is why changing your filters cannot change what gets detected or how anything is scored. It decides only whether the finished card reaches you.

New subscribers start on 🛡 Sellable only. See Filters.

What this is not

It is not sniping. We see the launch instantly and then deliberately wait, because the checks take time and the admission gate takes longer. You are early relative to the feed and the crowd — you are not racing anyone's mempool, and if that is what you need, we are the wrong tool.

It is not complete. Tokens nobody ever profiles never enter the pipeline. Some are real. That cost is stated on Coverage rather than hidden.

➡️ Next: Reading an alert