"It's on Uniswap" is three different setups on Robinhood Chain

Uniswap is the deepest venue on Robinhood Chain, and all three live versions are in active use at once. A v2 pair, a v3 pool at a specific fee tier, and a v4 pool ID are separate markets with separate addresses. The Telegram group only sees whether buys post, so the saved route has to match the market the team is actually pointing people at.

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

When the version is unknown, start with the broad Uniswap route and let discovery sort it out:

/watch robinhood 0xToken any <firstMintBlock> uniswap all

When the version is known, name it:

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

v3 fee tiers create more than one real pool

A Robinhood Chain token quoted in WETH often ends up with more than one v3 pool, because a 1% tier used at launch and a tighter tier added later can both hold liquidity. Both are genuine Uniswap v3 markets. If the team saves the tier that has been abandoned, the feed goes quiet while trading continues somewhere else.

The practical fix is to save the pool the chart link points at:

/pool robinhood 0xPoolAddress 0xTargetToken

Stablecoin-quoted markets behave the same way. Robinhood Chain has both USDG and USDC pools, so name the quote when you want discovery narrowed:

/watch robinhood 0xToken usdg <firstMintBlock> uniswap v3 all
/watch robinhood 0xToken usdc <firstMintBlock> uniswap v3 all

v4 is a pool ID, not a pair address

Uniswap v4 carries a large share of Robinhood Chain volume, and it does not work like the older versions. There is no per-pool contract address to paste. A v4 market is identified by a pool ID, and adding one needs the launch block alongside it:

/pool robinhood 0xV4PoolId 0xTargetToken <firstMintBlock>

If the team has the full pool key instead of a pool ID, send the two currency addresses, the fee, the tick spacing, the hook address, and the target token to whoever is configuring alerts. Handing over the exact key before launch day is far calmer than reconstructing it while the room is asking why nothing is posting.

Hook-based v4 markets are common on a new chain because launch tooling tends to deploy them by default. A hook does not block alerts, but it does mean the pool ID is the only reliable identifier. Do not substitute a token address for it.

Confirm before the room trusts the feed

After adding the route, run:

/pools
/settings
/topic here

/pools shows exactly which Uniswap market was saved, including the version. That is the moment to catch a v3 pool saved when the team meant the v4 pool ID. /settings controls minimum buy size, media, emoji, and transaction links. /topic here pins the feed into a dedicated alert topic instead of the main chat.

A good setup note

Keep it short and concrete: token address, first-mint block, Uniswap version, pool address or v4 pool ID, quote token, and the Telegram topic. On Robinhood Chain the first-mint block deserves extra care, because blocks arrive quickly and a rough guess covers far less real time than it would on Ethereum.

If your Robinhood Chain Uniswap route is not covered, message @mrtdlgc on Twitter/X or Telegram with the chain, DEX, token address, first-mint block, pool address if available, and the Telegram group where alerts should post.

Summary

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