Catch a launch at mint
An alert is a head start, not an answer. This is how to spend it.
The sequence
Section titled βThe sequenceβA typical launch arrives as a chain of alerts, not one.
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.
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.
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.
Your sixty seconds
Section titled βYour sixty secondsβ- 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.
- Open the contract, not the name. Names and tickers are copied constantly. The contract address is the only thing that identifies the token.
- 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.
- 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.
After you are in
Section titled βAfter you are inβ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.
When there is no CA yet
Section titled βWhen there is no CA yetβ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.

