Prism v3 alerts should follow the pool people recognize

Prism v3 on MegaETH is a specific route, and the Telegram buy feed should reflect that specificity. If the community is sharing a Prism pool, the bot should not be left to watch a vague MegaETH token route unless discovery is still the goal.

Add @BAESBuyBot to the group, give it posting permission, and run setup where the alerts should appear.

For a Prism v3 launch:

/watch megaeth 0xToken any <firstMintBlock> prism v3 all

Use a first-mint block that is exact or very close. This keeps setup close to the token's real launch history.

Known pool beats launch-day guesswork

If the Prism pool exists already, save it directly:

/pool megaeth 0xPrismPool 0xTargetToken

Direct pool entry is especially useful when the team wants alerts ready before the public announcement. You can save the pool, confirm it, set the topic, and test the alert style before the room starts asking questions.

Tune the Telegram surface

After saving the route:

/pools
/settings
/topic here

Use /pools to confirm the Prism pool. Use /settings to control the alert threshold, media, emoji, and link display. In a forum-style Telegram group, use /topic here inside the dedicated buy-alert topic.

The goal is not just "alerts work." The goal is that the first alert looks like it belongs in the launch room. A messy feed can make even a working bot feel unfinished.

If the market changes

If liquidity moves from one Prism pool to another, do not leave the old route hanging around because it was first. Remove or replace stale pools so the feed stays aligned with the market the group recognizes.

When asking for support, send the Prism pool address, token address, first-mint block, and a recent transaction if one exists. That lets the route be checked directly.

Summary

For MegaETH Prism v3, use /watch megaeth ... prism v3 with the token's first-mint block, or use /pool when the exact Prism market is known. Confirm the saved route before announcing that Telegram alerts are ready.