Why PancakeSwap v3 gets its own guide

PancakeSwap v3 on Base can look similar to other concentrated-liquidity routes from a user's point of view, but the setup should still name the DEX. If a token also trades on Uniswap v3 or Aerodrome, a broad setup can point at the wrong market. A Telegram alert feed is only useful when it follows the pool people actually buy from.

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 supports a PancakeSwap v3 filter so teams can target that route clearly.

Enable PancakeSwap v3 alerts

After adding @BAESBuyBot to Telegram, start with /watch and use the exact first-mint block or a block very close to it:

/watch base 0xToken any <firstMintBlock> pancakeswap v3 all

If the token is known to trade against USDC:

/watch base 0xToken usdc <firstMintBlock> pancakeswap v3 all

For a known pool:

/pool base 0xPoolAddress 0xTargetToken

Known pool entry is helpful with v3-style liquidity because there can be more than one viable pool. The Telegram group does not care how many routes exist; it cares whether the buy posts match the chart everyone is using.

Make the alerts fit the room

Open settings:

/settings

Then choose media, minimum buy size, alert text, and emoji. If the group is using topics, route alerts:

/topic here

You can pause and resume alerts around maintenance or migrations:

/pause
/resume

Reading the saved pool

For PancakeSwap v3, a good setup is not just "something was found." It should be the pool that matches the chart, quote token, and liquidity your team plans to promote. If the token has multiple v3-style markets, save the exact pool address instead of hoping the broad route stays correct.

This is also a good place to decide how many alerts the group should see. Very early launches may benefit from a low threshold because every buy reassures the room. Established pools usually need a higher minimum so the feed highlights meaningful trades. Use /settings as part of launch prep, not as an afterthought.

If the group uses several topics, run /topic here from the final alert topic after the pool is saved. That avoids buy posts landing in a moderation, raid, or announcements thread by accident.

When in doubt, ask the team for the pool link they plan to share in chat. The alert setup should follow that link, not a guess about where liquidity might be.

Use the first-mint block as the setup anchor even when the pool is created later. It gives the bot a clean starting point for the token lifecycle and keeps the command consistent across v2, v3, and v4 routes.

If your launch is not on Base

PancakeSwap v3 appears on multiple chains. If the chain you need is not listed yet, message @mrtdlgc on Twitter/X or Telegram. Include the chain, DEX, token, and pool address if possible.

Summary

For Base PancakeSwap v3, use the pancakeswap v3 filter so alerts do not drift into a different route. Use /watch with a precise first-mint block, confirm with /pools, and prefer /pool when the exact pool is already known.