MegaETH alerts are about being early and precise

MegaETH is not a chain where a token team should wait until the chat is already asking why buys are not posting. The opportunity is early visibility. If a new MegaETH community can show buys in Telegram while the ecosystem is still forming, the bot becomes part of the launch habit.

To set it up, invite @BAESBuyBot to the Telegram group, give it permission to post, and run the setup command from the group or from the alert topic.

baes scan currently covers Kumbaya v3, Prism v3, and Noxa v3 on MegaETH. These are route-specific v3 setups. If the team is sharing one exact pool, save that pool. If the route is still being discovered, use /watch with the DEX name and the token's first-mint block.

The MegaETH setup flow

Start broad only when you need discovery. New admins can run /watch without arguments and follow the chain, token, and first-mint block prompts:

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

Prefer a DEX-specific command when the launch venue is known:

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

If the pool is known, use direct entry:

/pool
/pool megaeth 0xPoolAddress 0xTargetToken

Then confirm:

/pools
/settings
/topic here

Why the exact pool matters

On new chains, the first few DEX routes can become part of the community story. If the chart link says Kumbaya but the alert feed is watching a different route, the group will notice. Good setup prevents that mismatch.

The best setup note is small and concrete: token address, first-mint block, DEX name, pool address if available, target token, and the Telegram group or topic. That gives the person configuring alerts enough information to save the right market without improvising.

Keep the alert feed intentional

MegaETH groups may want every early buy visible, especially while the community is small. Later, the same group may prefer a higher minimum buy so the feed feels more curated. Open /settings before launch and choose the style deliberately.

If your MegaETH route is not Kumbaya, Prism, or Noxa, message @mrtdlgc on Twitter/X or Telegram with the route and pool details. New routes are much easier to review when the DEX and pool shape are clear.

MegaETH route guides

Use the route page that matches the active v3 pool:

Summary

For MegaETH, baes scan supports Kumbaya v3, Prism v3, and Noxa v3. Use /watch megaeth ... <dex> v3 with the first-mint block, or /pool megaeth 0xPoolAddress 0xTargetToken when the exact market is known.