Hook-based launches need exact market setup

Uniswap v4 hooks are becoming launch language, not just developer language. A team might say the token is a "v4 hook" launch, a Chinese-language group might ask whether the buybot supports hooks, and the Telegram room still expects a simple result: buy alerts should post when people trade the token.

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

The important detail is that a hook is not the same thing as the token. In Uniswap v4, a hook contract can be attached to a pool and can run during pool actions such as swaps or liquidity changes. The Uniswap v4 hook docs explain that hooks are attached through the pool setup, and the Uniswap interface docs show that hook addresses now matter in normal pool creation and routing flows.

For a Telegram buybot, that changes the setup question. You are not only asking "what token is this?" You are asking which chain, which v4 pool, which hook address if known, and which target token should count as the buy.

Start with the v4 route

If the team knows this is a Base Uniswap v4 launch but does not have the pool ID yet, start with /watch and use the exact block where the token was first minted, or a block very close to it:

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

That tells baes scan to treat the market as a v4 route instead of guessing from a broad token address.

For a Clanker-style v4 launch, use the Clanker filter:

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

Use the filtered setup only when the launch route actually matches that shape. If the token is a normal Uniswap v4 pool with a different hook, use the broader v4 route or add the exact pool details with /pool.

Add the hook or pool when known

If you already have the v4 pool ID, add it directly:

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

If the team has the full pool key, use the full v4 path:

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

That command shape is especially useful for hook launches because the hook address is part of the pool identity. If the hook is known but the pool ID is not, ask the deployer for the two currencies, fee, tick spacing, hook address, target token, and first-mint block before the Telegram group starts asking why alerts are quiet.

Why a v4 hook buybot can look broken

A generic buybot can look healthy and still miss a hook-based route. The most common problem is not the minimum-buy setting or the alert text. It is that the saved market does not match the pool buyers are using.

That can happen when:

  • The group shares a v4 chart, but the bot saved an old v2 pair.
  • The token has more than one v4 pool.
  • The hook address was omitted from a full pool-key setup.
  • The pool ID is correct, but the wrong target token was selected.
  • Telegram topic permissions block posts after the pool is already correct.

Run this before changing alert style:

/pools
/settings
/topic here

Use /pools to confirm the saved market, /settings to tune the threshold and media, and /topic here from the alert topic if the group uses Telegram forum topics.

What to collect before launch

The cleanest v4 hook setup note has seven fields:

  • Chain, usually Base for the current v4 launch flow.
  • Token contract.
  • First-mint block.
  • Uniswap v4 pool ID, if available.
  • Hook address, if the route is hook-based.
  • Full pool key fields if there is no pool ID yet.
  • Telegram group or topic where alerts should post.

That may feel like more detail than an old pair-address buybot asks for, but it saves time during launch. A hook route is specific. If the bot is pointed at the exact pool, the group sees buys. If the bot is pointed at the wrong route, the group gets a quiet feed and everyone starts debugging the wrong thing.

Use these when the setup is more specific:

If your chain or DEX is not listed, 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, hook address if relevant, and the Telegram group where alerts should post.

Summary

For Uniswap v4 hooks buy alerts, do not treat the setup like a normal pair-address bot. Invite @BAESBuyBot, start with /watch ... uniswap v4, and use /pool when you know the pool ID or full pool key. For hook launches, the hook address is part of the market detail that keeps Telegram alerts pointed at the route people are actually trading.