PancakeSwap v3 needs a pool-aware alert feed

PancakeSwap v3 on Monad is not the same setup problem as an old constant-product pair. There can be more than one pool around the same token, and the active market may be defined by the route the team shares during launch. A Telegram buybot should follow that market, not just any pool with the token in it.

Add @BAESBuyBot to the Telegram group, make sure it can post, and run setup from the group or the topic where buys should appear.

For a PancakeSwap v3 route, use:

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

Use the token's exact first-mint block or a block very close to it. That keeps setup focused on the token's real launch history.

When the pool exists, use it

If the team already knows the PancakeSwap v3 pool, direct entry is cleaner than discovery:

/pool monad 0xPoolAddress 0xTargetToken

This is the better setup for a launch checklist. The moderator can save the pool, confirm it, set the topic, and avoid route guesswork while the community is already watching.

Make the alert style fit the room

After the route is saved, run:

/pools
/settings
/topic here

For a small early Monad group, low minimum buys can help the room feel active. For a louder group, a higher minimum keeps the feed from turning into noise. Set this before the first public push if possible.

Use /topic here from the alert topic in a Telegram forum group. That lets the main chat stay conversational while buys still remain visible.

What to verify before calling it done

The pool should match the PancakeSwap v3 link the team is using. If a second pool appears later, decide whether to add it as another tracked pool or remove the old one. Do not leave an accidental pool active just because it was discovered first.

If alerts are quiet, check /pools before assuming the bot is broken. On a new chain, the most common mistake is not that the route is impossible. It is that the setup watched a broader route than the team intended.

Summary

For Monad PancakeSwap v3, use /watch monad ... pancakeswap v3 with the token's first-mint block. If the exact pool is known, use /pool monad 0xPoolAddress 0xTargetToken, confirm it with /pools, and tune the group with /settings.