RING-HUNTER AI
✦ Read-only CLI · Robinhood Chain

Track insider rings.Before you buy in.

RING-HUNTER AI reads a token's on-chain data — who launched it, who bought first, and where their funds came from — then flags wallets that move together. Everything runs from your own terminal.

  • 11 stagesreal progress, not fake animation
  • 0–100deterministic, auditable score
  • Zero keysno private keys, no transactions

Ready inone minute.

Install once, use it from any folder — Windows, macOS, or Linux. Run these in your terminal. Click to copy.

  1. Have Node.js 22.13 or newerGet it from nodejs.org if node -v shows an older version.
  2. Install RING-HUNTERAdds the ring-hunter command globally.
  3. Create your configWrites ~/.ring-hunter/.env with the public RPC + chain ID 4663. Never overwrites an existing file.
  4. Check the connectionConfirms the RPC really is Robinhood Chain (4663).
  5. Scan your first tokenThe PXT1 test token — safe for a first try.

One command.Eleven stages.

Open the interactive menu with ring-hunter, or scan a token directly. Each stage lights up only when it has actually finished: connection, network check, token contract, creator, pools, early buyers, holders, funding graph, clusters, contract, score.

The address above is the PXT1 test token — safe for a first try.

--no-aiuse local analysis, no AI provider
--savesave the report to ~/.ring-hunter/reports
--jsonprint the JSON report to stdout

Wallets thatmove together.

Early buyers are linked by a shared funding source, direct transfers, ties to the deployer, and closely timed buys. Exchanges, bridges, and hot wallets are excluded to avoid false positives.

  • STRONG_CORRELATIONseveral strong indicators at once — often includes the deployer
  • POSSIBLE_CLUSTERfunding indicators worth checking
  • OBSERVED_LINKone observed connection
  • UNVERIFIEDtiming coincidence only

Every cluster comes with tx-hash evidence and alternative explanations. On-chain correlation is not proof of shared ownership.

A score youcan audit.

Six components with fixed weights. Missing data is never treated as safe — the component is excluded and coverage drops.

70+HIGH OBSERVED RISK
40+MODERATE RISK
<40LOWER OBSERVED RISK
<50%coverage → INSUFFICIENT DATA

AI writes.The engine counts.

Gemini or Groq only drafts the summary. Every address, score, and percentage the AI writes is checked against the engine's data — if anything doesn't match, the summary is rejected and the local analysis is used. The app runs fully even without an API key.

# ~/.ring-hunter/.env  — fill in one of them (optional)
AI_PROVIDER=groq
GROQ_API_KEY=…your key…
GROQ_MODEL=…a model name from your account…

# strongly recommended: ETH funding sources between wallets
BLOCK_EXPLORER_API_KEY=…free at dev.blockscout.com…

API keys are never printed and never sent to the AI.

Connect a wallet.Get the commands.

Connecting only reads your address — no transactions. The page then builds CLI commands ready to copy.

Link your CLI.Optional.

Tie the ring-hunter command on your computer to your wallet. Every scan works without it — the account only identifies you.

  1. Connect & sign inOn the account page your wallet signs one plain-text message (Sign-In with Ethereum). Not a transaction, no gas, no token approval.Open the account page →
  2. Create your API keyThe dashboard shows it once — store it like a password. You can rotate or revoke it any time.
  3. Log in from the terminalPaste the key when asked; it is saved in ~/.ring-hunter.

Check it with ring-hunter whoami; remove it with ring-hunter logout. The site never asks for your seed phrase or private key.

Launch on Pons.Scan before you buy.

Tokens launched on the Robinhood side of the launchpad use Pons v2 — the same factory 0x7eD5…EC7e that RING-HUNTER reads. So you can check any Pons token before you buy it.

  1. Find a token on the launchpadSwitch the launchpad to the Robinhood network to see Pons tokens.
  2. Copy its addressThe 0x… address on the token's page.
  3. Scan itPaste the address after scan.

Different roles: RING-HUNTER only reads. The launchpad signs transactions through your wallet (launch, buy, sell, claim) — review every confirmation in your wallet. Solana tokens (base58 addresses) can't be scanned by RING-HUNTER.

Every command,in one place.

Interactive menu: scan, wallet clusters, developer wallet, reports, export, config check
Non-interactive scan (add --save, --json, --no-ai)
Create the config file in ~/.ring-hunter
Check config & RPC connection, and show where the config file is
Link the CLI to your account with the API key from the dashboard (optional)
Show which wallet the CLI is linked to
Remove the API key from this computer (revoke it on the dashboard to disable it everywhere)
Update to the latest version (your config and reports are kept)
Remove the command (~/.ring-hunter stays; delete it yourself if you want)
“RPC connection failed: fetch failed”

Check your internet, then run ring-hunter check. The public RPC is sometimes busy — try again shortly, or set a private RPC in ROBINHOOD_CHAIN_RPC. Some internet providers block the RPC domain through their DNS — and they intercept plain DNS too, so only changing the DNS numbers to 1.1.1.1 often isn't enough. Turn on encrypted DNS instead. Windows 11: Settings → Network & internet → your connection → DNS server assignment → Edit → Manual → 1.1.1.1 / 1.0.0.1 with DNS over HTTPS: On. macOS/Linux/phones: install Cloudflare's 1.1.1.1 app or use a VPN. A private RPC (Alchemy, Chainstack) on another domain also works.

“ring-hunter” is not recognized

Close and reopen the terminal after installing. If it still fails, check that npm's global folder is on your PATH: npm prefix -g shows where it is.

ETH funding source shows NONE

Native ETH transfers aren't recorded in logs. Set BLOCK_EXPLORER_API_KEY (free) for a complete funding graph; without it, confidence is capped at MEDIUM.

Menu doesn't appear / “requires a terminal (TTY)”

Run ring-hunter from a regular terminal, not with redirected output. For automation, use ring-hunter scan <address> --json.

AI summary isn't used

Set AI_PROVIDER, the API key, and the model name in ~/.ring-hunter/.env. If the quota runs out or the answer fails validation, the local analysis is used automatically.