Kumbaya v3 should be named, not guessed
If a MegaETH token is launching on Kumbaya, the Telegram setup should say Kumbaya. That sounds obvious, but launch rooms often start with a token address, a chart link, and a lot of urgency. The cleaner habit is to save the actual route before the first public wave.
Invite @BAESBuyBot, allow it to post, and run setup from the group or alert topic.
For discovery around a new token, use:
/watch megaeth 0xToken any <firstMintBlock> kumbaya v3 all
The first-mint block should be exact or close. It keeps setup focused around the token's own launch history.
Use direct pool entry when you can
If the Kumbaya pool address is already known, direct setup is better:
/pool megaeth 0xKumbayaPool 0xTargetToken
This avoids a noisy launch-day search and gives moderators something concrete to verify later. Direct pool entry is also the easiest setup to repeat if the group moves alerts to another topic or launches a second token.
Make the first alert look deliberate
After the pool is saved:
/pools
/settings
/topic here
Use /pools to confirm Kumbaya is the saved route. Use /settings to choose minimum buy size and alert style. Use /topic here in the exact topic where buys should post.
Early MegaETH groups are often smaller, so lower thresholds can help show life in the room. If the group is already busy, raise the minimum so the feed does not bury conversation.
What to put in the team note
A good Kumbaya setup note includes token address, first-mint block, Kumbaya pool address if available, target token, Telegram group, and desired alert topic. That is enough for a moderator to check the setup without asking the deployer to dig through chat history.
If alerts are quiet, check /pools first. The most useful question is not "is the bot on?" but "is the saved pool the Kumbaya pool everyone is trading?"
Summary
For MegaETH Kumbaya v3, use /watch megaeth ... kumbaya v3 with the first-mint block, or save the exact Kumbaya pool with /pool. Confirm the route before the group treats the feed as live.