Curve alerts on Arbitrum need target-token clarity

Curve routes are not ordinary pair routes. On Arbitrum, a Curve pool can include multiple assets, and the Telegram group usually wants alerts around one target token. Without that context, a buy alert can become confusing instead of useful.

baes scan supports Curve as a named Arbitrum route so teams can put pool-aware alerts into Telegram while keeping setup manageable.

Add @BAESBuyBot, make sure it can post, and run setup in the group or alert topic.

Add Curve buy alerts

Use:

/watch arbitrum <token> any <first_mint_block> curve

Then confirm:

/pools

For Telegram topics:

/topic here

Use /settings to decide how much pool activity deserves a Telegram post.

What to identify before setup

Use the project token address as the watched token. Confirm the Curve pool the group wants to show. If there are multiple pools or the token is only secondary in the pool, include that context when asking for support.

Curve-specific alerts are useful because they name the venue and make the pool intent explicit. A generic Arbitrum feed does not do that.

Support notes

Send the token, Curve pool link, target-token note if needed, first mint block if known, and Telegram group to @mrtdlgc on Twitter/X or Telegram.

Summary

For Arbitrum Curve Telegram buy alerts, use /watch arbitrum <token> any <first_mint_block> curve, verify with /pools, and tune with /settings. The key is making the pool and target token clear before alerts become public.