XHuntr logo
XHuntr

13 Signals From The Social Layer

XHuntr watches what the accounts you track do on X — the communities they build, rename and post contract addresses inside — and pushes every change to Telegram. Here is each signal, what triggers it, and what to do when it lands.

Address before the public tweetCommunity layer

CA in Community

What it detects
A contract address posted inside an X community you're watching, rather than on the public timeline.
When it fires
The moment the address appears in the community — which is routinely before the announcement tweet.
Why it matters
Devs hand the CA to their own room first. That gap between the community post and the public tweet is the whole edge.

In the alert

  • Token name and full contract address
  • Live DexScreener market data
  • Trojan quick-buy link
  • Which community it was posted in
What you do next: Check the DexScreener data in the alert, then buy from the alert if the chart supports it.

How often: Fires whenever a tracked community gets a CA — bursty, tied to launch activity.

XHuntr

CA in Community

Contract address posted inside a tracked community


🔒 Inside: tracked community

🪙 $TICKER

📋 7xKX…9fQa

💰 mcap and 1h volume from DexScreener


DexScreener ↗ | Trojan ↗ | Copy CA

Alert format · placeholder token details
Caught at mintCommunity layer

Launching

What it detects
A brand-new coin whose metadata links back to a community you already track.
When it fires
At mint — the link between the fresh token and the tracked community is caught as the coin is created.
Why it matters
This is the earliest point a launch is attributable to a group you're already watching, before it has a chart or a following.

In the alert

  • Token name, ticker and contract address
  • The tracked community it links back to
  • Quick-buy link
  • Detection timestamp
What you do next: Decide fast — this fires while the token is still at its opening market cap.

How often: Rare and high-signal. A few hundred have fired since launch.

XHuntr

Launching

🚀 LAUNCHING


Fresh coin linked to a community you track

🪙 $TICKER

📋 7xKX…9fQa

🏘 linked community: tracked


Caught at mint

Alert format · placeholder token details
Two hunters, one roomCross-account

Convergence

What it detects
Two or more of the accounts you track landing in the same X community inside a short window.
When it fires
As soon as the second tracked account joins.
Why it matters
Independent accounts converging on one room is coordination you can see before anything is said publicly.

In the alert

  • Which of your tracked accounts triggered it
  • The shared community and member count
  • Time window between the joins
  • Link to the community
What you do next: Open the community and look at what's being discussed — convergence tells you where, not what.

How often: Genuinely rare — it needs two of YOUR accounts in one room. Tracking more accounts makes it fire more.

XHuntr

Convergence

2 tracked accounts joined the same community


👥 @ixlabel + @cache100x

📛 Away From Keyboard

👤 143 members


Both tracked · view community ↗

Real alert that fired · account and community as recorded
Contract address with contextAccount layer

CA Tweet

What it detects
A contract address tweeted by an account you track — Solana, and Robinhood Chain addresses too.
When it fires
As the tweet is picked up — tracked accounts' tweets are fetched continuously.
Why it matters
A CA on the public timeline is already a race. Getting it pushed to Telegram with the market data attached decides it.

In the alert

  • Token name and symbol
  • Contract address, tap to copy
  • Live DexScreener market data
  • Trojan quick-buy link
  • Chain resolved automatically — Solana or Robinhood Chain
What you do next: Read the mcap and volume in the alert before you act — most of these are not worth taking.

How often: The highest-volume signal by a wide margin.

XHuntr

CA Tweet

A tracked account tweeted a contract address


🪙 $TICKER

📋 7xKX…9fQa

💰 live mcap · 📈 24h volume


DexScreener ↗ | Trojan ↗ | Copy CA

Alert format · placeholder token details
New name, new narrativeCommunity layer

Community Rename

What it detects
A tracked community changing its name.
When it fires
On the next community poll after the change.
Why it matters
A generic room renaming itself to a ticker is a group telling its members what's next without announcing it.

In the alert

  • Old name and new name
  • Member count at the time of the rename
  • Link to the community
  • Timestamp of the change
What you do next: A rename into a ticker is worth acting on. A cosmetic rename usually isn't.

How often: One of the most frequent community signals.

XHuntr

Community Rename

@feinixsol renamed their community


📝 → $Shillcoin

👥 428 members


Rename detected · view community ↗

Real alert that fired · account and community as recorded
The room's pitch changedCommunity layer

Description Changed

What it detects
The description of a tracked community being rewritten.
When it fires
On the next community poll after the edit.
Why it matters
Descriptions get rewritten right before a room starts being used for something — often with the ticker or the thesis in it.

In the alert

  • Old and new description text
  • The community and its member count
  • Link to the community
  • Timestamp of the change
What you do next: Read the new text — the change itself is usually less interesting than what it now says.

How often: Fires frequently across a normal watchlist.

XHuntr

Description Changed

@cryptoboxreal changed a community description


📛 $UPCAT

📋 old and new text included in the alert


Description updated · view community ↗

Real alert that fired · account and community as recorded
Where their attention wentAccount layer

Community Joined

What it detects
An account you track joining an X community.
When it fires
On the next poll after the join is visible on their profile.
Why it matters
Who someone joins is a better read on conviction than what they post, because joining isn't performative.

In the alert

  • Community name and member count
  • Join policy — open or request
  • Link to the community
  • Detection timestamp
What you do next: Watch for a second tracked account to follow them in — that's Convergence.

How often: Steady — one of the reliable everyday signals.

XHuntr

Community Joined

@kylebands1 joined a community


📛 Nothing Just Happens

👥 73 members

🌐 Open


View community ↗

Real alert that fired · account and community as recorded
What they're pushing nowAccount layer

Pinned Tweet Changed

What it detects
A tracked account changing its pinned tweet.
When it fires
On the next profile poll after the change.
Why it matters
A pin is the one slot an account controls permanently. Changing it is a deliberate statement of current focus.

In the alert

  • Preview of the new pinned tweet
  • Direct link to the tweet
  • Timestamp of the change
What you do next: If the new pin contains a CA, that's the account putting its name on it.

How often: Regular, across an active watchlist.

XHuntr

Pinned Tweet Changed

@mrnovaaaa changed their pinned tweet


📝 preview of the new pinned tweet


New pinned · view tweet ↗

Real alert that fired · account and community as recorded
A coin attached itself to themAccount layer

Coin Mentions

What it detects
A newly created coin whose metadata points at a tracked account's profile or tweet.
When it fires
As the coin is picked up.
Why it matters
It surfaces tokens being launched off someone's name — sometimes by them, often not. Either way you see it early.

In the alert

  • The coin and its contract address
  • Which tracked account it links to
  • Quick-buy link
  • Detection timestamp
What you do next: Check whether the account has actually acknowledged it before assuming they're involved.

How often: Varies with how much a tracked account is being used as a launch hook.

XHuntr

Coin Mentions

👁 COIN MENTION


A new coin links a tracked account’s profile

🪙 $TICKER

📋 7xKX…9fQa


Not necessarily launched by them

Alert format · placeholder token details
A new room appearsCommunity layer

Community Created

What it detects
A tracked account creating a brand-new X community.
When it fires
On detection of the new community on their profile.
Why it matters
A room created before there is anything to put in it is the earliest structural sign of something being organised.

In the alert

  • Community name and id
  • Member count at creation
  • Join policy
  • Link to the community
What you do next: Note it and watch for the rename — creation alone rarely tells you what it's for.

How often: Dependent on X surfacing new communities on a profile; currently the least frequent community signal.

XHuntr

Community Created

@zeeoffone created a new X community


📛 1 agent can change your life

👥 1 member

🔓 Open


View community ↗

Real alert that fired · account and community as recorded
The room closedCommunity layer

Community Deleted

What it detects
A tracked account deleting or leaving a community you were alerted about.
When it fires
On the next poll after the community disappears from their profile.
Why it matters
It closes the loop. A room that appears and then vanishes tells you the play is over or was abandoned.

In the alert

  • Which community ended
  • Threaded as a reply to your original alert
  • The tracked account involved
  • Timestamp
What you do next: Use it to stop watching something that's finished, rather than to trade.

How often: Follows whatever your tracked accounts abandon.

XHuntr

Community Deleted

🗑 A tracked community was deleted or left


📛 the community from your earlier alert

↩️ threaded as a reply to that alert


Closes the loop on the play

Alert format · placeholder token details
They went liveAccount layer

Dev Live on pump.fun

What it detects
A developer you track starting a live stream on pump.fun.
When it fires
As the stream goes live.
Why it matters
Streams pull attention and volume onto a token in real time. Being in early is a different trade than joining a trending stream.

In the alert

  • Token name, market cap and bonding curve progress
  • All-time-high market cap and time since the stream started
  • Viewer count plus Trojan and Axiom quick-buy links
  • Dev quality filters — graduated tokens, no-rug history, custom
What you do next: Check the bonding curve percentage in the alert before deciding.

How often: Tied to how many streaming devs you track.

XHuntr

Dev Live on pump.fun

🎯 TRACKED DEV LIVE


🪙 $TICKER

💰 live mcap · ATH mcap

📈 bonding curve % · 🟢 dev quality filter

👥 viewer count · ⏱ time since live


Trojan ↗ | Axiom ↗ | DexScreener ↗

Alert format · placeholder token details

// how they combine

Community layer

Signals about the rooms themselves — created, renamed, redescribed, rebranded, used to share an address, or shut down.

Account layer

Signals about the people you track — what they tweet, what they pin, what they join, and what gets launched off their name.

Cross-account

Signals that only exist because you track several accounts at once. Convergence is the reason roster size matters.

// platform

Alert History

Every alert you have received is stored. Run /history to browse the full log and see what fired while you were away.

Per-Signal Controls

Toggle each of the 13 signals on or off in /settings, globally or per tracked account. Add a member-count filter and a per-account poll speed.

Community Lookup

Run /communities @username to see the X communities an account belongs to without adding them to your roster.

Multi-Language Bot

The bot interface is available in English, Russian, Chinese and Portuguese, detected from your Telegram language and switchable with /language.

// what XHuntr does not do

It does not trade for you

XHuntr detects and notifies. Execution happens in your own terminal — alerts carry Trojan and Axiom links, but no order is ever placed on your behalf.

It does not read private accounts

Only public X accounts can be tracked. If an account is protected, its activity is not visible to XHuntr any more than it is to you.

It polls, it does not receive a firehose

Detection is bounded by poll cadence — roughly 12s for accounts and 60s for community state. It is fast, but it is not instantaneous and no tool watching X from outside can be.

A signal is not a recommendation

Every alert is an observation about behaviour on X, not advice. Most signals do not lead to a trade worth taking, and reading the market data in the alert is on you.

// in development

soon

KOL Scout

Surface accounts worth tracking from the patterns XHuntr already sees — who joined communities before a move, who posted a CA early — and add them in one tap.

soon

Alpha Score

A per-account score built from that account's own signal history, so you can tell whose community joins have led somewhere and whose are noise.

soon

Wallet Crossref

When a CA alert fires, check whether known whale wallets are already in — on-chain confirmation attached to the social signal.

soon

Watchlist Groups

Sort tracked accounts into tiers such as insiders, devs and callers, and run separate convergence rules for each.

soon

Web Dashboard

Alert history, signal analytics and roster management in a browser, for the times Telegram is the wrong place to review things.

These are not available yet and are not included in any plan. Nothing above is required for the 13 signals that ship today.

// faq

Frequently Asked Questions

What is XHuntr?

XHuntr is a Telegram bot that watches the X (Twitter) accounts you choose and alerts you when something moves on the social layer — a contract address posted inside a community, a community renamed, two tracked accounts landing in the same room, a pinned tweet swapped. It covers 13 distinct signals.

What is an X community sniper?

It's a tool that monitors X community activity rather than the public timeline — who creates communities, who joins them, and what gets posted inside them. XHuntr is built around that layer specifically for Solana traders.

What is a convergence alert?

Convergence fires when two or more accounts you track join the same X community within a short window. Because it requires two of your own tracked accounts to overlap, it is rare — tracking more accounts makes it fire more often.

How quickly does XHuntr detect things?

XHuntr polls rather than receiving a push from X, so timing depends on the signal. Tracked accounts are polled about every 12 seconds by default (about every 8 seconds for accounts you mark Fast), and community state — names, descriptions, banners — about every 60 seconds. Delivery to Telegram is immediate once a change is detected.

How is XHuntr different from wallet trackers like Cielo or BullX?

Wallet trackers report on-chain activity — by the time a buy settles, the price has usually moved. XHuntr watches what happens on X beforehand: communities being set up, renamed, and used to share a contract address. They answer different questions, and plenty of traders run both.

How is XHuntr different from KOL trackers like DexCheck or KolScan?

KOL trackers rank historical trading performance — who has been good. XHuntr is a live feed of what tracked accounts are doing right now on X. Leaderboard versus live monitor.

How many X accounts can I track?

Weekly: 15 accounts. Monthly: 20. Yearly: 25. Every paid plan includes all 13 signals and full alert history. Extra slot packs can be added to any plan.

What blockchains does XHuntr support?

XHuntr is built for Solana — contract address detection, DexScreener data and Trojan quick-buy links are all Solana-native. The bot also resolves Robinhood Chain addresses, and community monitoring itself works for any X account regardless of which chain it focuses on.

What is a CA in community alert?

Developers frequently post the contract address inside their own X community before tweeting it publicly. XHuntr watches community timelines and fires the moment an address appears there, rather than waiting for the public tweet.

Does XHuntr require any technical setup?

No. Send /start to the bot, add accounts with /add @username, and adjust alerts in /settings. No API keys, no wallet connection, no config files.

Is there a free plan?

Yes. A 5-day trial starts as soon as you run /start — track 5 accounts with all 13 signals, no SOL and no card. After the trial you keep 2 tracked accounts free, renewed weekly with one tap. Paid plans start at 0.40 SOL per week.

How do I pay?

Run /upgrade in the bot. XHuntr generates a fresh SOL wallet for your payment, confirms it on-chain, and extends your access. Weekly 0.40 SOL, Monthly 1.15 SOL, Yearly 8.00 SOL. There is no auto-renewal and no card on file.

Start Tracking

5-day trial, 5 accounts, all 13 signals. No SOL and no card to begin — up to 25 accounts on the yearly plan.

Start Tracking →

Want to see how each signal is used in practice? Read the strategy guides →

Signal list verified against the live bot, August 2026.