Uniswap v4 pool IDs are not normal pair addresses

Uniswap v4 changes the setup model for Telegram buy alerts. Instead of every pool behaving like a separate ordinary pair contract, v4 activity is organized around PoolManager, pool IDs, pool keys, fees, tick spacing, and hooks. PoolScout and Bitquery's Base v4 docs show the same pool-ID shape from a developer-data angle. That is why a normal pair-address buybot setup can feel fine for v2 and v3 but miss the v4 market.

Invite @BAESBuyBot to the Telegram group and start with guided setup:

/watch

For a direct Base Uniswap v4 setup:

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

For Clanker-style hook launches:

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

Use pool IDs or full pool keys when known

If you already know the pool ID:

/pool
/pool base 0xV4PoolId 0xTargetToken <firstMintBlock>

For a full pool key:

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

Confirm the saved market

Run:

/pools
/settings
/topic here

Do not treat v4 silence like a normal threshold problem until the pool ID or pool key is correct.

When this works best

Use this path when the group has a concrete market to verify. The strongest Uniswap v4 pool ID setup starts from public details the moderator can paste into Telegram: chain, token contract, first-mint block, DEX route, pool address when known, and the topic where alerts should land. That keeps the setup grounded in the market buyers actually use instead of a ticker, screenshot, or vague chart title.

It also helps when a token has more than one pool. A community might talk about the token as if there is only one market, while the chain has an old pair, a newer concentrated-liquidity pool, and a separate route the launch team actually wants to promote. In that situation, the clean setup is not the broadest setup. It is the setup that matches the pinned chart and the route admins expect to see in every alert.

What can still block alerts

The common trap is trying to treat PoolManager markets like ordinary pair contracts. Check that before declaring the bot broken. A Telegram group can also block posts through topic permissions, missing admin rights, or a media setting that Telegram refuses to send. Those issues are easier to solve after the saved market is correct.

If your chain or DEX is not listed, 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. Specific market details make setup help much faster than a broad request for a buybot.

Summary

For Uniswap v4 pool ID buy alerts, use a v4-aware baes scan setup. Start with /watch ... uniswap v4, use /pool for known pool IDs or full pool keys, and confirm with /pools.