Do not let "Uniswap on Monad" stay vague

Uniswap is a familiar name, but on Monad it still needs a precise alert setup. A v2 pair, a v3 pool, and a v4 pool ID are not the same thing. The Telegram group only cares that real buys appear on time, but the saved alert should still point at the right route.

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

If the team only knows that liquidity is on Uniswap, start with the broad Uniswap route:

/watch monad 0xToken any <firstMintBlock> uniswap all

If the version is known, name it:

/watch monad 0xToken any <firstMintBlock> uniswap v2 all
/watch monad 0xToken any <firstMintBlock> uniswap v3 all
/watch monad 0xToken any <firstMintBlock> uniswap v4 all

The first-mint block matters. It keeps setup focused around the token's actual launch history instead of treating the chain as one huge search space.

v4 deserves its own setup note

Monad Uniswap v4 setup should be treated as a v4 setup, not as a disguised pair address. If the team has a pool ID, use it directly:

/pool monad 0xV4PoolId 0xTargetToken <firstMintBlock>

If the team has the full pool key, send the currency addresses, fee, tick spacing, hook address, and target token to the person configuring alerts. Exact v4 details make pre-launch setup much calmer.

For v2 or v3 pools, direct pool setup is shorter:

/pool monad 0xPoolAddress 0xTargetToken

Confirm before the feed becomes a signal

After adding the route, run:

/pools
/settings
/topic here

/pools is the reality check. If the saved route is not the route being shared by the team, fix it before the Telegram room starts treating alerts as official. /settings is where you choose minimum buy size, media, emoji, and transaction links. /topic here keeps the feed in a dedicated alert topic.

A good Monad Uniswap setup note

Keep the setup note plain: token address, first-mint block, Uniswap version, pool address or v4 pool ID, quote token if known, and the Telegram topic. That small amount of detail prevents most launch-day confusion.

If multiple Uniswap routes exist, save the one the community will recognize. A silent alert feed is bad, but a feed posting from the wrong market can be worse because it makes people distrust the setup.

Summary

For Monad Uniswap, baes scan supports v2, v3, and v4 alert routes. Use /watch monad ... uniswap <version> with the first-mint block when discovering pools, and use /pool when the pair, pool, or v4 pool ID is already known.