Noxa v3 setup is a route decision

Noxa v3 on MegaETH should be saved as Noxa, not hidden behind a generic token watch. The whole point of a Telegram buybot is that the community sees the market it already recognizes. If the DEX link says Noxa, the command should say Noxa too.

Invite @BAESBuyBot, give it permission to post, and run setup from the group or the alert topic.

Use this command when discovery is needed:

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

The first-mint block keeps setup practical. It should be the exact block where the token first existed or a block close enough to the pool creation.

Save the Noxa pool directly when possible

If the pool address is known, use:

/pool megaeth 0xNoxaPool 0xTargetToken

This is the cleanest pre-launch setup. It gives the team a specific market to confirm and avoids broad route guesswork while the room is already watching.

Confirm, then polish

After setup:

/pools
/settings
/topic here

Check /pools before telling the group that alerts are live. In /settings, choose the minimum buy size and alert style. If the group uses Telegram topics, run /topic here from the topic where buys should post.

For early MegaETH launches, it is often worth keeping the message style short. People want to see the buy size, transaction link, and chart link without a wall of decoration.

Keep the setup note concrete

A good Noxa setup note includes token address, first-mint block, Noxa pool address if known, target token, Telegram group, and alert topic. If the route changes later, update the saved pool instead of letting old alerts quietly continue.

If you need help with a Noxa route, send the pool address and a recent transaction. That gives support something real to check instead of guessing from a ticker.

Summary

For MegaETH Noxa v3, use /watch megaeth ... noxa v3 with the token's first-mint block, or save the known pool with /pool. Confirm the saved market with /pools before treating the alert feed as live.