A wrong pool can look like a broken bot

If a Telegram buybot is quiet while a chart shows buys, the bot may not be broken. It may be watching the wrong market. Tokens often have more than one pool: a launch pair, a v3 pool with a different fee, an old Sushi pair, a v4 pool ID, or a Curve or Balancer pool where the target token matters.

To use baes scan, invite @BAESBuyBot to the Telegram group, give it permission to post, and run setup from the group or alert topic.

Start with the guided command

Run:

/watch

Choose the chain, paste the token contract, and use the first-mint block help when the deployer has not already sent it. Power users can use the direct command:

/watch base 0xToken any <firstMintBlock> all

If the route is known, name it:

/watch base 0xToken any <firstMintBlock> uniswap v4 all
/watch base 0xToken any <firstMintBlock> aerodrome all

Use exact pool entry when the market is known

Run:

/pool
/pool base 0xPoolAddress 0xTargetToken

Use the pool the community shares in its pinned chart or deployer note. If that pool is old, unusual, or pool-shaped, exact entry is usually calmer than guessing.

Confirm before tuning

After setup, run:

/pools
/settings
/topic here

/pools is the checkpoint. If the saved market is wrong, fix the pool or route before changing media, minimum buy size, or topic settings.

When this works best

Use this path when the group has a concrete market to verify. The strongest wrong-pool recovery starts from public details the moderator can paste into Telegram: chain, token contract, first-mint block, DEX route, pool address when known, and the topic where alerts should land. That keeps the setup grounded in the market buyers actually use instead of a ticker, screenshot, or vague chart title.

It also helps when a token has more than one pool. A community might talk about the token as if there is only one market, while the chain has an old pair, a newer concentrated-liquidity pool, and a separate route the launch team actually wants to promote. In that situation, the clean setup is not the broadest setup. It is the setup that matches the pinned chart and the route admins expect to see in every alert.

What can still block alerts

The common trap is treating a quiet feed as a threshold problem before checking the saved market. Check that before declaring the bot broken. A Telegram group can also block posts through topic permissions, missing admin rights, or a media setting that Telegram refuses to send. Those issues are easier to solve after the saved market is correct.

If your chain or DEX is not listed, message @mrtdlgc on Twitter/X or Telegram with the chain, DEX, token address, first-mint block, pool address if available, and the Telegram group where alerts should post. Specific market details make setup help much faster than a broad request for a buybot.

Summary

A Telegram buybot watching the wrong pool can look silent for the wrong reason. With baes scan, check /pools, add the exact market with /pool, and tune only after the saved pool matches the community chart.