Curve alerts are pool alerts, not ordinary pair alerts

Curve on Avalanche needs a slightly different buybot mindset. A Curve pool can contain multiple assets, and the alert the group cares about is usually a target-token movement inside that pool. If the Telegram bot treats it like a simple v2 pair, the output can become confusing.

baes scan supports Curve as a named Avalanche route so the group can save the right pool intent and keep alerts understandable. This is useful for tokens that trade through a Curve pool where the venue name matters to buyers.

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

Add Avalanche Curve buy alerts

Use the Curve route:

/watch avalanche <token> any <first_mint_block> curve

Then confirm:

/pools

If the group uses topics:

/topic here

Use /settings to control how much activity appears in the room. Pool routes can produce activity that belongs on-chain but is not always worth posting into the Telegram feed.

Choosing the target token

For Curve, the question is not just "what pool exists?" It is "which asset in this pool should count as the token the community is tracking?" Use the token address that matches the project, not the quote asset or a pool helper token.

If there are multiple Curve pools, choose the one the community links in chat. If the group is really watching a different DEX for price action and Curve only has secondary liquidity, do not force Curve into the main alert feed.

Support notes

Curve setup questions are easiest to answer with a pool link. Send the token, Curve pool link, target token if there is any ambiguity, and Telegram group to @mrtdlgc on Twitter/X or Telegram.

Summary

For Avalanche Curve Telegram buy alerts, use /watch avalanche <token> any <first_mint_block> curve, verify with /pools, and tune with /settings. Curve alerts are best when the pool and target token are clear from the beginning.