Skip to content

Add XHuntr — X community sniper for pump.fun launch detection#15

Open
nxsdevv wants to merge 1 commit into
PotLock:mainfrom
nxsdevv:main
Open

Add XHuntr — X community sniper for pump.fun launch detection#15
nxsdevv wants to merge 1 commit into
PotLock:mainfrom
nxsdevv:main

Conversation

@nxsdevv
Copy link
Copy Markdown

@nxsdevv nxsdevv commented Mar 19, 2026

What is XHuntr?

XHuntr is a Telegram bot that monitors X (Twitter) accounts for community activity and fires instant alerts when tracked KOLs create or join X communities, post contract addresses inside communities before tweeting publicly, or when multiple tracked accounts converge on the same community.

Why it belongs in the pump.fun ecosystem list

Most pump.fun launches follow the same pattern before any token is deployed:

  • Developer creates a private X community
  • KOLs are invited and join privately
  • CA is shared inside the community before the public tweet
  • Token deploys on pump.fun

XHuntr monitors this preparation phase — detecting community creates, joins, convergence, and CA posts at the social layer, before any pump.fun transaction exists.

Details

@vercel
Copy link
Copy Markdown

vercel Bot commented Mar 19, 2026

@nxsdevv is attempting to deploy a commit to the POTLOCK Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Mar 19, 2026

📝 Walkthrough

Walkthrough

The app/data/tools.json file was updated to add a new tool entry named XHuntr with associated metadata (Twitter handle, description, URL, chat link, profile image, tags, and blockchain fields). Additionally, existing JSON array fields were reformatted from single-line to multi-line format for consistency.

Changes

Cohort / File(s) Summary
Tool Data Update
app/data/tools.json
Reformatted existing tags and blockchain arrays from single-line to multi-line format; added new XHuntr tool object with complete metadata including twitter handle, URLs, description, tags, and blockchain designations.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Poem

🐰 A new tool hops into the fold,
XHuntr joins the ranks so bold,
Arrays stretch across the page,
Formatting marks a cleaner stage,
Data grows with every bound! 🎯

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change: adding XHuntr, a tool for detecting pump.fun launches through X community monitoring.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
📝 Coding Plan
  • Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Tip

Migrating from UI to YAML configuration.

Use the @coderabbitai configuration command in a PR comment to get a dump of all your UI settings in YAML format. You can then edit this YAML file and upload it to the root of your repository to configure CodeRabbit programmatically.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@app/data/tools.json`:
- Around line 181-182: The file ends with a closing JSON array bracket ("]") but
lacks a trailing newline; update app/data/tools.json by adding a single newline
character at EOF so the file ends with a newline after the closing array to
satisfy POSIX conventions and avoid diff/tool warnings.
- Around line 162-180: Replace the broken profile image URL for the "XHuntr"
entry by updating the "profileImage" field to point to a valid reachable image
(e.g., from the site's assets or a working CDN) so the JSON entry for "XHuntr"
has a non-404 image URL; locate the object with name "XHuntr" and change the
profileImage value accordingly, keeping the rest of the entry (tags,
description, url, chatLink, blockchain, relation) intact.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 75c773b0-ae73-49b2-880c-3c00a893405e

📥 Commits

Reviewing files that changed from the base of the PR and between 6506402 and 9ec63aa.

📒 Files selected for processing (1)
  • app/data/tools.json

Comment thread app/data/tools.json
Comment on lines +162 to +180
{
"name": "XHuntr",
"twitter": "XHuntrbot",
"description": "Real-time X (Twitter) community monitoring bot that fires Telegram alerts when tracked KOLs create or join X communities, post contract addresses inside communities, or when multiple tracked accounts converge. Fires 24-48 hours before wallet trackers.",
"url": "https://xhuntr.com",
"chatLink": "https://t.me/XHuntrbot",
"profileImage": "https://pbs.twimg.com/profile_images/1855659556888432640/wWxsIZna_400x400.jpg",
"tags": [
"bot",
"telegram",
"analytics",
"social-monitoring",
"alpha",
"trading"
],
"blockchain": [
"Solana"
],
"relation": "Monitors X community activity to detect pump.fun launches before they go public \u2014 fires when developers create X communities and invite KOLs, 24-48 hours before any pump.fun token is deployed"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify external URLs for XHuntr entry are reachable

echo "Checking xhuntr.com website..."
curl -sL -o /dev/null -w "%{http_code}" https://xhuntr.com

echo -e "\n\nChecking profileImage URL..."
curl -sL -o /dev/null -w "%{http_code}" "https://pbs.twimg.com/profile_images/1855659556888432640/wWxsIZna_400x400.jpg"

echo -e "\n\nChecking Telegram bot link..."
curl -sL -o /dev/null -w "%{http_code}" https://t.me/XHuntrbot

Repository: PotLock/awesome-pump

Length of output: 167


Replace the broken profileImage URL before merging.

The XHuntr entry structure is correct and follows existing patterns, with all required fields properly included. The new tags will be automatically collected by ToolsSection.tsx.

However, the profileImage URL (https://pbs.twimg.com/profile_images/1855659556888432640/wWxsIZna_400x400.jpg) returns a 404 error and must be replaced with a valid image URL. The main xhuntr.com website and Telegram bot link are both reachable and working.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@app/data/tools.json` around lines 162 - 180, Replace the broken profile image
URL for the "XHuntr" entry by updating the "profileImage" field to point to a
valid reachable image (e.g., from the site's assets or a working CDN) so the
JSON entry for "XHuntr" has a non-404 image URL; locate the object with name
"XHuntr" and change the profileImage value accordingly, keeping the rest of the
entry (tags, description, url, chatLink, blockchain, relation) intact.

Comment thread app/data/tools.json
Comment on lines 181 to +182
}
]

] No newline at end of file
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Add trailing newline at end of file.

The file is missing a trailing newline after the closing ]. POSIX-compliant files should end with a newline to avoid diff noise and tool warnings.

Proposed fix
     "relation": "Monitors X community activity to detect pump.fun launches before they go public \u2014 fires when developers create X communities and invite KOLs, 24-48 hours before any pump.fun token is deployed"
   }
-]
+]
+
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@app/data/tools.json` around lines 181 - 182, The file ends with a closing
JSON array bracket ("]") but lacks a trailing newline; update
app/data/tools.json by adding a single newline character at EOF so the file ends
with a newline after the closing array to satisfy POSIX conventions and avoid
diff/tool warnings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant