Skip to content

Catch a launch at mint

An alert is a head start, not an answer. This is how to spend it.

A typical launch arrives as a chain of alerts, not one.

How a launch usually unfolds in XHuntr alerts1. Joined: a tracked KOL joins a fresh community; nothing is on-chain yet. 2. Convergence: more accounts you track arrive. 3. CA alert: the contract goes live. 4. Follow-ups: multiples and rugs arrive as replies to the original alert. The time between steps 1 and 3 is your head start. 1 πŸ‘€ Joined A KOL joins a fresh community. Nothing on-chain yet. T+0 2 πŸ”₯ Convergence More of your KOLs arrive in the same community. minutes β†’ hours 3 πŸ“‘ CA alert The contract goes live. Now there is something to check. the contract drops 4 πŸ† Follow-ups 2Γ—, 5Γ—, 10Γ— or a rug, as replies in the same thread. after the call Your head start: hours, sometimes days Since April 2026 X no longer lets accounts create communities, so most community signals are joins. How a launch usually unfolds in XHuntr alerts1. Joined: a tracked KOL joins a fresh community; nothing is on-chain yet. 2. Convergence: more accounts you track arrive. 3. CA alert: the contract goes live. 4. Follow-ups: multiples and rugs arrive as replies to the original alert. The time between steps 1 and 3 is your head start. 1 πŸ‘€ Joined A KOL joins a fresh community. Nothing on-chain yet. T+0 2 πŸ”₯ Convergence More of your KOLs arrive in the same community. minutes β†’ hours 3 πŸ“‘ CA alert The contract goes live. Now there is something to check. the contract drops 4 πŸ† Follow-ups 2Γ—, 5Γ—, 10Γ— or a rug, as replies in the same thread. after the call Steps 1 β†’ 3 are your head start: hours, sometimes days. Since April 2026 most community signals are joins.

1. 🏠 Joined: a KOL walks into a community. Nothing exists on-chain yet. This is the earliest point you can be involved. Open the community and watch it.

🏠 KOL JOINED A COMMUNITY   πŸ‘€ @somedev πŸ“› Pippin Insiders πŸ§‘β€πŸ’» by @pippindev πŸ‘₯ 12 Β· 🟒 Open πŸ’¬ the ticker is coming ⏱ Created Oct 4 at 14:02 UTC (detected 6s later) βœ… Verified in member list   πŸ”— Community14:02
βš™οΈ Alert settings for @somedev

2. πŸ”₯ Convergence: others arrive. More accounts you track join the same community. The more accounts and the tighter the window, the stronger the signal.

3. πŸ“‘ CA: the contract goes live. Now there is something to check.

πŸ“‘ @somedev posted a CA in the community   πŸ’¬ πŸ’¬ Pippin Insiders   πŸͺ™ Pippin (PIPPIN) Β· $52K mcap 0.0000520 Β· pump.fun   FWuimB9mNPQCYKeKjtH11Wwqx5vKwVuz4FjVCAfNpump   πŸ”— View Tweet Β· πŸ“Š DexScreener   ⚑ Trojan Β· 🟣 Axiom Β· 🐸 GMGN Β· πŸ”₯ Pump.fun Β· πŸ”” Updates16:41

These are the bot’s real layouts with made-up accounts. While a coin is fresh, its CA alert refreshes in place with the change since the alert, Dex Paid status, holder quality and a πŸ”΄ LIVE line when the data exists. See Coin alerts.

  1. Check which alert you got. πŸš€ Launch traces to a community they own. πŸ‘ Coin Mention is only their name on a coin and is usually a copycat. They deserve very different levels of trust. See Alert types.
  2. Open the contract, not the name. Names and tickers are copied constantly. The contract address is the only thing that identifies the token.
  3. Read liquidity and holders, not just price. A market cap with almost no liquidity behind it cannot be exited. One wallet holding most of the supply is the standard shape of a rug. CA alerts include a holder-quality line (dev %, top 10, snipers, bundlers) when the data is available.
  4. Confirm the link back to the KOL. Does the community belong to the account that alerted you? Did they post the CA, or did a random member? A CA posted in someone’s community by a stranger is not their launch.

If the coin was called by a KOL you track, XHuntr keeps following it with πŸ“ˆ Coin updates: one reply when it hits 2Γ—, 3Γ—, 5×… from the call, and one when it collapses from its peak. These arrive as replies to the original alert. See Coin alerts.

Often a KOL joins a community well before the contract exists. Use that gap: research the dev, check their previous launches, and decide in advance what you would do if a CA drops, so you are not deciding under time pressure.

For launches from accounts you are not tracking, see EarlyHunt.