Curve buy alerts require pool context from the start

Curve on Ethereum is not a simple pair market. Pools can include multiple assets, and the community usually cares about a particular target token moving inside that pool. A Telegram buybot needs that intent, otherwise alerts can become hard to interpret.

baes scan supports Ethereum Curve as a named route so teams can put pool-aware buy alerts into Telegram with a clear venue label.

Invite @BAESBuyBot, give it permission to post, and run setup from the group or topic where alerts should appear.

Add Ethereum Curve alerts

Use:

/watch ethereum <token> any <first_mint_block> curve

Then confirm:

/pools

For Telegram topics:

/topic here

Use /settings to control how noisy the feed becomes.

Identify the target token

For Curve, setup should answer two questions: which pool, and which token inside the pool should count as the asset being bought? Use the project token address, not a quote asset or pool token. If there are several Curve pools, use the one the community actually links.

This is why Curve-specific alerts matter. A generic Ethereum feed can make a pool route look confusing. A named Curve feed makes the venue and intent visible.

When to ask for help

Send the token, Curve pool link, target token if there is ambiguity, first mint block if known, and Telegram group to @mrtdlgc on Twitter/X or Telegram. Curve support is much faster when the pool is named directly.

Summary

For Ethereum Curve Telegram buy alerts, use /watch ethereum <token> any <first_mint_block> curve, verify with /pools, and tune with /settings. Curve alerts work best when the pool and target-token intent are clear before the first post.