Community Watch — by Xanguard

Frontrun Token Launches
By Tracking the Devs

You know devs who repeat launches. Track them — get notified the moment they create a new community, before they even post the CA in there. Monitor joins, leaves, and creates via webhook and API.

Open @F_xanguard_bot View Pricing
~30s
Detection Speed
3
Event Types
500
Max Accounts
24/7
Continuous Polling
Event Types

Three signals. One edge.

Every community gate action is tracked and delivered to you in real-time. Know what devs and influencers are doing before they announce it.

Join Events

A dev you track just joined a new community. Are they scouting the next meta? Joining a collab group? You see it before anyone tweets about it.

Leave Events

A dev quietly leaves a project community. That’s a signal. Fading interest, rug incoming, or strategic pivot — you see it before the crowd does.

Create Events

This is the money signal. A serial dev creates a new community — you’re notified instantly. The CA hasn’t been posted yet. You’re early. That’s the whole point.

How It Works

Simple setup, continuous monitoring

Add the accounts you want to track. We handle the rest.

1

Subscribe

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

2

Add Targets

Add Twitter handles you want to monitor via the bot or REST API.

3

Configure

Set your webhook URL, event type filters, and minimum member count thresholds.

4

Receive Alerts

Get JSON webhook payloads within ~30 seconds of each community gate change.

Features

Built for speed and reliability

Enterprise-grade infrastructure behind a simple API.

Per-Account Proxy Isolation

Each polling account uses its own sticky proxy IP. No shared fingerprints, no cross-contamination between accounts.

Smart Filters

Filter by event type (join/leave/create), minimum community member count, and flap cooldown to suppress rapid join+leave noise.

Cold Start Suppression

First poll syncs state silently. You only get notified about real changes — no spam when a target is first added.

Target Deduplication

If multiple clients track the same account, we poll it once and fan out events to all watchers. Zero wasted requests.

Account Health Monitoring

Automatic error tracking per polling account. Auto-disable at 5 consecutive errors with admin alerts. Self-healing on recovery.

Dynamic Poll Intervals

Poll frequency auto-adjusts based on target count. More targets = faster cycle per account. Configurable base interval.

Webhook Payload

What you receive

Every event is delivered as a JSON POST to your webhook endpoint.

POST https://your-server.com/cw-hook 
// A dev you're tracking just created a new community
{
  "event_type": "CREATE",
  "twitter_user_id": "1234567890",
  "screen_name": "SerialDev_",
  "community": {
    "id": "1892345678901234567",
    "name": "$MOONCAT Community",
    "member_count": 1,
    "role": "Admin"
  },
  "detected_at": "2026-03-03T12:34:56Z"
}
// CA hasn't been posted yet. You're early.
Pricing

Scale with your needs

Pay monthly in SOL. All plans include webhook delivery, API access, and smart filters.

Starter
20 accounts
$100
per month
$5.00 / account
  • 20 monitored accounts
  • Webhook delivery
  • API access
  • All event types
  • Smart filters
Get Started
Most Popular
Pro
100 accounts
$500
per month
$5.00 / account
  • 100 monitored accounts
  • Webhook delivery
  • API access
  • All event types
  • Smart filters
  • Priority support
Subscribe
Enterprise
500 accounts
$1,500
per month
$3.00 / account
  • 500 monitored accounts
  • Webhook delivery
  • API access
  • All event types
  • Smart filters
  • Dedicated support
Subscribe
Also available: 50 accounts — $250/mo and 200 accounts — $800/mo. Contact via Telegram for details.
FAQ

Frequently asked questions

Twitter Communities are groups that accounts can join, similar to Discord servers or Telegram groups. The "community gate" is the state of which communities an account belongs to. Community Watch tracks changes to this state — when someone joins a new community, leaves one, or creates their own.
Community Watch uses a poll-based architecture where each target account is checked on a regular cycle. With the default configuration, changes are typically detected within ~30 seconds. The exact timing depends on the number of targets and the configured poll interval.
Flap protection suppresses rapid join-then-leave (or leave-then-join) sequences. If an account joins and leaves a community within the configured cooldown period (default: 5 minutes), the second event is suppressed. This filters out accidental clicks, testing behavior, and community gate spam. You can customize or disable this per client.
Three filter types: Event type — choose which events to receive (join, leave, create, or any combination). Minimum member count — only alert for communities above a size threshold (e.g., 1000+ members). Flap cooldown — suppress rapid join/leave sequences within a configurable time window.
Yes. Community Watch delivers events via webhook (HTTPS POST with JSON payload) and provides a REST API for target management. You can add/remove targets programmatically, receive events at your server endpoint, and integrate directly into your existing trading or alerting pipeline.
Community Watch is a separate product with its own subscription and bot (@F_xanguard_bot). Tweet alerts are handled by @Xanguard_bot. They complement each other — track what accounts tweet and which communities they join for complete social intelligence. Both accept SOL payments.

Stop being late. Start frontrunning.

Track the devs. Get the signal. Act before the CA drops. Set up in minutes, pay with SOL.

Open @F_xanguard_bot Back to Xanguard