SushiSwap v2 alerts are for Avalanche pairs that still matter

SushiSwap is not always the loudest Avalanche venue, but some tokens still use a Sushi v2 pair as the market the community watches. When that is the case, the Telegram buybot should not bury the route under a broad Avalanche label. It should tell the room that Sushi buys are coming through.

baes scan supports Avalanche SushiSwap v2 alerts through @BAESBuyBot. The setup is pair-oriented: save the token, point the route at SushiSwap v2, and confirm the watch before expecting posts.

Add SushiSwap v2 buy alerts

Use:

/watch avalanche <token> any <first_mint_block> sushiswap v2

Then run:

/pools

For Telegram topics:

/topic here

Use /settings after the feed starts. Sushi pairs can have bursts of tiny trades, especially around campaigns or old-community revivals. A good threshold makes the alerts feel intentional.

Why route naming helps

If a group is talking about Sushi, the alert should say Sushi. That sounds small, but it changes how new buyers interpret the feed. A route-specific alert connects the Telegram post to the chart link in the pinned message, which makes the group feel less chaotic.

It also makes debugging easier. If the token has an Avalanche Uniswap pool and a Sushi pool, /pools can show what the group saved. You do not have to guess which market the bot is reading.

Common setup mistakes

Do not use only the ticker. Do not assume all Avalanche liquidity routes are interchangeable. Do not keep lowering thresholds if the real issue is that the active pool is on a different DEX.

If the Sushi v2 pair is hard to set up, message @mrtdlgc on Twitter/X or Telegram with the token, pair link, first mint block, and Telegram group.

Summary

For Avalanche SushiSwap v2 buy alerts, run /watch avalanche <token> any <first_mint_block> sushiswap v2, confirm with /pools, and use /settings to keep the group feed readable. It is the right route when Sushi is the market your community actually uses.