Uniswap v4 does not behave like a normal pair

If a Uniswap v4 buybot is not working, the setup may be treating v4 like an older pair-address market. That is the wrong mental model. Uniswap v4 uses PoolManager, pool IDs, pool keys, and sometimes hooks. A Telegram alert feed needs enough v4 detail to follow the market the group is actually trading.

baes scan supports v4-aware setup so token teams can use @BAESBuyBot without forcing the group to understand every pool detail.

Start with a v4 route

After inviting @BAESBuyBot, use the token's first-mint block or a block very close to it:

/watch base 0xToken any <firstMintBlock> uniswap v4 all

For Clanker-style v4 launches:

/watch base 0xToken any <firstMintBlock> uniswap v4 clanker

Then confirm:

/pools

If the saved pool does not match the v4 market the group is using, fix that before tuning settings.

Use direct pool entry when the pool is known

If you already have the v4 pool ID, use it:

/pool base 0xV4PoolId 0xTargetToken <firstMintBlock>

If the team has the full pool key, use the full setup shape:

/pool base 0xCurrency0 0xCurrency1 3000 60 0xHooks 0xTargetToken

Direct entry is usually calmer than trying to discover the route while the launch room is watching. It gives admins something concrete to verify with /pools.

Common v4 mistakes

The most common mistake is using a generic pair-address habit on a v4 market. The second is forgetting that hooks can matter. The third is saving a broad token route when the group already has an exact pool ID.

If the chart link says Uniswap v4, the Telegram feed should not quietly fall back to another route. If the launch is hook-based, the setup should respect that route from the start.

Topic and threshold checks

Once the pool is correct, check the Telegram side:

/topic here
/settings

Use /topic here in the alert topic if the group has forum topics. Use /settings to choose the minimum buy size and message style. These are important, but they cannot fix a wrong v4 route.

What to send for support

Send the token address, first-mint block, v4 pool ID if known, hook address if relevant, chart or pool link, and Telegram group to @mrtdlgc on Twitter/X or Telegram.

Summary

For a Uniswap v4 buybot that is not posting, use v4-aware setup. Start with /watch ... uniswap v4, use /pool for known pool IDs or full pool keys, confirm with /pools, and only then tune topics and settings.