PancakeSwap on Ethereum should be treated as an intentional route

When a token uses PancakeSwap on Ethereum, the group usually wants that venue named clearly. Otherwise the alert feed can look like a generic mainnet bot that happens to catch swaps. A PancakeSwap-specific setup gives admins the language they need when PancakeSwap is the market they are promoting.

baes scan supports Ethereum PancakeSwap alerts across v2 and v3-style routes. The token and first mint block help anchor alerts around the launch history, while the route tells the bot which venue the Telegram feed should represent.

Add Ethereum PancakeSwap alerts

Use:

/watch ethereum <token> any <first_mint_block> pancakeswap

Then verify:

/pools

For topic routing:

/topic here

Use /settings after the first buys arrive. Mainnet alerts usually benefit from a threshold that filters noise but still catches trades worth showing.

v2 or v3?

PancakeSwap v2 behaves like a pair route. PancakeSwap v3 behaves like an exact pool route. If the token has both, save the active one. If PancakeSwap is secondary and most volume is on Uniswap, decide whether PancakeSwap should be the main feed or a secondary venue.

The public feed should match the chart link in the group. If buyers are told to use PancakeSwap, the alert should say PancakeSwap. If not, use the route people actually use.

Support notes

Send the token, PancakeSwap pool or pair link, first mint block if known, and Telegram group to @mrtdlgc on Twitter/X or Telegram if setup needs help. Include whether the route is v2 or v3 if you know.

Summary

For Ethereum PancakeSwap buy alerts, use /watch ethereum <token> any <first_mint_block> pancakeswap, confirm with /pools, and tune with /settings. It is the right route when PancakeSwap is the venue the Ethereum group wants to display.