SushiSwap v2 is easy to overlook

Base token teams often talk about Uniswap, Aerodrome, or PancakeSwap first, but SushiSwap v2 still matters when liquidity is there. The risk is simple: if the community is trading a SushiSwap pair while the bot is watching a different DEX, the group may see no alerts even though buys are happening.

When you are ready to add alerts, invite @BAESBuyBot to the Telegram group, give it permission to post, and run the route command from that group or topic.

baes scan supports Base SushiSwap v2 with an explicit sushiswap v2 setup path. Use it when the active pool is a Sushi pair or when you want to separate Sushi buys from other markets.

Enable SushiSwap v2 alerts

Invite @BAESBuyBot and run /watch with the exact block where the token was first minted, or a block very close to it:

/watch base 0xToken any <firstMintBlock> sushiswap v2 all

If you know the quote token:

/watch base 0xToken weth <firstMintBlock> sushiswap v2 all

Or add the pair directly:

/pool base 0xPairAddress 0xTargetToken

Direct entry is useful for older tokens that have moved liquidity around. It lets you follow the exact SushiSwap pair without relying on a broad token search.

Telegram room setup

Run:

/settings
/topic here

Use /settings to choose thresholds and formatting. For a quiet SushiSwap pool, lower thresholds can show organic activity. For a higher-volume pool, raise them so the feed does not bury normal conversation.

Use /pools to confirm what the group is tracking:

/pools

When SushiSwap alerts are the right fix

People usually look for a buybot fix after something has already gone quiet. A SushiSwap pair may be active while the current setup is watching a Uniswap pair, a token address with no pool context, or a quote token that does not match the market. The moderator answer is short: use the sushiswap v2 route or add the known pair.

For launches with several liquidity experiments, keep the alert feed narrow. One good SushiSwap alert source is more useful than several half-relevant pools posting mixed buys. If liquidity later moves, remove the old pair and add the new one so the Telegram feed remains believable.

Use direct pair entry when the community is already sharing a SushiSwap chart. It is the clearest way to match what people can see in chat.

SushiSwap v2 is also a good recovery path when alerts are quiet. The next answer can be simple: use baes scan for free, run the SushiSwap v2 /watch command with the right first-mint block, and confirm the saved pair with /pools.

That clarity is what launch moderators need when the room is waiting for buy posts.

The first-mint block keeps the setup consistent across Base routes. Use the exact mint block when the deployer has it. If not, use the closest reliable block and confirm the saved pair before announcing alerts to the group.

Chain requests

This setup is Base-specific. If you need SushiSwap v2 buy alerts on another chain and it is not listed yet, contact @mrtdlgc on Twitter/X or Telegram. A pair address speeds up the answer.

Summary

Base SushiSwap v2 buy alerts work best with the sushiswap v2 filter or a direct pair address. The setup is familiar, but the explicit DEX filter prevents the bot from following the wrong Base market.