Convergence Tracker — by Xanguard

Detect Coordinated Moves
Before the CA Drops

Track multiple Twitter accounts. When they cluster in the same community, you get alerted — before anyone tweets about it.

~30s
Detection Speed
Tunable
Thresholds
500
Max Accounts
24/7
Monitoring

Three steps to convergence detection

Subscribe, add targets, get alerts. The system does the correlation for you.

1

Subscribe

Open @T_Xanguard_bot on Telegram and choose a plan. Pay with SOL.

2

Add Targets

Add Twitter handles to monitor. These are accounts whose community activity you want to track.

3

Get Alerts

When 2+ of your targets join the same community, you get an instant convergence alert.

One signal. Maximum alpha.

When devs cluster in a community, something is about to launch. Convergence Tracker turns community overlap into actionable intelligence.

Clustering Detection

When multiple tracked accounts join the same community within your time window, it’s not coincidence. It’s coordination.

Configurable Thresholds

Set min convergence count (2–100 accounts), time window (6–48h), and community size filters. Tune the signal-to-noise ratio.

Powered by Community Watch

Built on the same polling engine as Community Watch. Zero additional API calls. Maximum efficiency.

Precision controls for serious traders

Fine-tune every parameter. Get exactly the signals you need.

Time Window Control

Configure how far back to look for convergence: 6h, 12h, 24h, or 48h. Shorter windows catch fast coordination. Longer windows catch slow buildups.

Min Convergence

Set the threshold — how many accounts must cluster before you are alerted. From 2 (early signal) to 5 (high conviction). Default is 2.

Community Size Filter

Only get alerts for communities above a minimum member count. Filter out spam communities and personal test groups. Focus on real activity.

Webhook & API

JSON webhook delivery with HMAC-SHA256 signing for payload verification, plus a full REST API for target management and configuration.

What you receive

A single JSON payload with everything you need to act.

POST https://your-server.com/ct-hook
// 3 accounts you track are in the same community. Something is about to launch.
{
  "event_type": "convergence_detected",
  "community_id": "1892345678901234567",
  "community_name": "$MOONCAT Community",
  "member_count": 3,
  "converging_handles": ["@SerialDev_", "@CryptoWhale", "@AlphaHunter"],
  "convergence_count": 3,
  "time_window_hours": 24,
  "detected_at": "2026-03-03T12:34:56Z"
}

Simple, scalable pricing.

Pay monthly in SOL. All plans include webhook delivery, API access, and all configuration options.

Starter
20 accounts
$100
per month
$5.00 / account
  • 20 monitored accounts
  • Telegram alerts
  • REST API access
  • Convergence settings
Subscribe
Growth
50 accounts
$250
per month
$5.00 / account
  • 50 monitored accounts
  • Telegram alerts
  • REST API access
  • Convergence settings
Subscribe
Business
200 accounts
$800
per month
$4.00 / account
  • 200 monitored accounts
  • Telegram + webhooks
  • REST API access
  • All convergence settings
  • Priority support
Subscribe
Enterprise
500 accounts
$1,500
per month
$3.00 / account
  • 500 monitored accounts
  • Telegram + webhooks
  • REST API access
  • All convergence settings
  • Dedicated support
Subscribe

Frequently asked questions

Convergence is when multiple accounts you track are found in the same Twitter community within your configured time window. It indicates coordinated activity — often a sign that a token launch is being prepared.
Approximately 30 seconds. Convergence Tracker is powered by the Community Watch polling engine, which checks each target account on a regular cycle with per-account proxy isolation.
Community Watch tells you when one account joins, leaves, or creates a community. Convergence Tracker tells you when multiple accounts converge in the same community — a much stronger signal that indicates coordinated activity. CW is about individual events; CT is about cross-account correlation.
The minimum number of tracked accounts that must be in the same community to trigger an alert. Default is 2. You can set it anywhere from 2 to 5 — higher values mean fewer but higher-conviction signals.
Yes. Both delivery methods work simultaneously. You receive convergence alerts in your Telegram chat via the bot, and structured JSON payloads at your webhook endpoint for programmatic processing.
Pay in SOL via the Telegram bot (@T_Xanguard_bot). Plans are billed monthly (30 days). The bot generates a payment address and confirms receipt automatically.

Detect the signal. Act before the crowd.

Act before the CA drops. When devs cluster in a community, something is about to launch.