Buy alerts should not need wallet access

A Telegram buybot for community alerts should not need private keys, seed phrases, or trading permission. The job is to watch public market activity and post formatted alerts into a group.

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

Telegram posting permission is different from wallet access. The bot may need permission to post messages, especially in strict groups, but it should not need private keys to show buy alerts.

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 safe read-only alert setup 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 confusing Telegram posting permissions with wallet or trading access. 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

For Telegram buy alerts, keep the setup read-only. Add @BAESBuyBot, provide public token and pool details, never share private keys, and confirm the saved market with /pools.