Robinhood Chain moves fast, so the alert route has to be exact

Robinhood Chain is an Ethereum layer 2 with ETH as the gas token, and it produces blocks far faster than most chains a Telegram admin has set up before. That speed is good for traders and awkward for anyone guessing at setup, because a "recent" block range on Robinhood Chain covers a much shorter slice of real time than the same number of blocks on Ethereum or Base. Naming the exact route removes that problem entirely.

To start, invite @BAESBuyBot to the Telegram group, give it permission to post, and run the setup command from the group or from the alert topic.

baes scan covers Uniswap v2, v3, and v4, PancakeSwap v2 and v3, and SushiSwap v2 and v3 on Robinhood Chain. Most early liquidity sits in Uniswap markets quoted in WETH, with USDG and USDC pools next to them.

The Robinhood Chain setup flow

If the admin does not know the command shape yet, run /watch with no arguments and follow the chain, token, and first-mint block prompts:

/watch
/watch robinhood 0xToken any <firstMintBlock> all

Use the DEX name when the launch venue is already known:

/watch robinhood 0xToken any <firstMintBlock> uniswap all
/watch robinhood 0xToken any <firstMintBlock> pancakeswap all
/watch robinhood 0xToken any <firstMintBlock> sushiswap all

The first-mint block is the part worth getting right. Use the exact block where the token was first minted, or a block very close to it. On a chain this fast, a block number copied from memory can be an hour off the real launch.

Quote tokens on Robinhood Chain

Most Robinhood Chain markets quote in wrapped ETH, so weth is the common quote. Stablecoin markets are split between USDG and USDC, and both are accepted by name:

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

Use any when the team is not sure which side the pool was created against. It is the safer first pass, and /pools will show what was actually saved.

When the pool is already known

Direct entry is shorter and avoids discovery entirely:

/pool
/pool robinhood 0xPoolAddress 0xTargetToken

Uniswap v4 markets on Robinhood Chain are identified by a pool ID rather than a pair address, so those need the launch block as well:

/pool robinhood 0xV4PoolId 0xTargetToken <firstMintBlock>

Then confirm what is live:

/pools
/settings
/topic here

/pools is the check that matters before a launch. If the saved market is not the one the team is linking in the chat, fix it while the room is still small.

Keep the feed deliberate

New chains produce a lot of small trades, and Robinhood Chain is no exception. A brand-new community usually wants every buy visible so the room feels alive. A week later the same group often wants a higher minimum buy so the feed reads as signal instead of noise. Open /settings before launch and pick the style on purpose rather than discovering it during the busiest hour.

If a token has pools on more than one Robinhood Chain DEX, save the one the community will recognize from the chart link the team is sharing. A feed posting from a thin secondary pool is worse than a quiet feed, because it teaches the room to distrust the numbers.

Robinhood Chain route guides

Use the route page that matches the live market:

If your Robinhood Chain route is not one of these, that does not mean baes scan cannot support it. 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, baes scan supports Uniswap v2/v3/v4, PancakeSwap v2/v3, and SushiSwap v2/v3. Use /watch robinhood ... <dex> with the token's first-mint block when discovering pools, or /pool robinhood 0xPoolAddress 0xTargetToken when the exact market is already known.