The Clanker-shaped problem

Clanker-style launches on Base made the usual "paste token, wait for buys" flow feel old very quickly. The pool can be a Uniswap v4 route, the launch can involve a hook, and the community still expects Telegram to light up when the first real buys arrive. That mismatch is exactly where a generic buybot can feel unreliable.

When you are ready to add alerts, invite @BAESBuyBot to the Telegram group, give it permission to post, and run the route command from that group or topic.

baes scan has a Clanker-focused command path so teams can tell the bot what kind of v4 route to watch. This keeps setup practical: you do not need to turn the group into a lecture about pool mechanics, but you do need to use the right filter.

Start with the Clanker filter

Invite @BAESBuyBot, make sure it can post, and run /watch with the exact first-mint block or a block very close to it:

/watch base 0xToken any <firstMintBlock> uniswap v4 clanker

If the token has more than one route, the Clanker filter helps keep the alert setup pointed at the launch path people are actually watching.

If the pool ID is already known

Known pool details are better than guessing. If the deployer has the pool ID, add it:

/pool base 0xV4PoolId 0xTargetToken <firstMintBlock>

For a full pool key:

/pool base 0xCurrency0 0xCurrency1 3000 60 0xHooks 0xTargetToken

This is the route to use when you want the Telegram group ready before launch traffic begins.

Telegram launch polish

Run the settings panel:

/settings

Set a minimum buy size, add media, and choose short alert text. If the group uses topics, open the alert topic and run:

/topic here

Keep the message style simple. Clanker launches can move fast, and people mainly want to see that buys are happening, how much was bought, and where the chart is.

A calmer launch routine

The best Clanker setup is done before the first flood of messages. Add @BAESBuyBot, route the topic, run /watch, and save the pool while only the team is paying attention. Then post one short note in the group telling people that buy alerts are ready. That is much cleaner than debugging in public after the first buys.

If the token has a pre-announced pool ID or launch link, save it. Exact pool details make setup faster than asking the bot to infer intent from a token address during launch traffic. If the route changes, remove the old pool and add the new one rather than leaving the group with duplicate alert sources.

This is also the setup to send users who are looking for a Clanker buybot and only know that normal alerts are not showing up.

Need this outside Base?

This setup is intentionally Base-specific. If you have a Clanker-style or v4-style route on another chain, send the chain, token, pool ID or pool address, and DEX name to @mrtdlgc on Twitter/X or Telegram.

Summary

For Clanker-style Base launches, use the uniswap v4 clanker command path with the token's first-mint block. Use /pool when you already have exact pool details. The win is clarity: the bot watches the launch route instead of guessing from a broad token address.