Skip to content

Hop Tracking

For what hop tracking does conceptually, see Hop Tracking Explained. This page is the command-by-command operational walkthrough.

Hop tracking is bot-only — there’s no dashboard view for hop sessions. Everything happens through Telegram commands.

CommandWhat it does
/hop <address>Start a session in all mode. The root wallet’s regular activity continues to alert; newly discovered downstream wallets get auto-tracked and emit full alerts.
/onlyhop <address>Start a session in hops_only mode. The root wallet’s regular activity is suppressed — you only see the hop-discovery alerts and CEX detections.
/hopsList your active sessions, with a tree view of discovered wallets per session.
/unhop <address>Stop a session. Auto-discovered wallets are removed; manually-tracked wallets are kept.

Both /hop and /onlyhop require the address to already be tracked manually first (with /track).

/hop 0xd8da6bf26964af9d7eed9e03e53415d37aa96045

The bot replies:

📡 Hop Tracking Started
Root: vitalik.eth
Mode: All alerts
Max depth: 5 hops
Max wallets: 50
Outgoing native & stablecoin transfers will be auto-tracked.
CEX deposits will be detected and flagged.
Use /unhop to stop | /hops to view sessions

Substitute /onlyhop to get Mode: Hops + deployments only.

SituationMessage
You haven’t tracked the root wallet firstYou must be tracking this wallet first. Use /track to add it.
You’re already running a session for this rootAlready hop-tracking this wallet.
You’re at your max active sessionsMax active sessions reached (X/Y). Use /unhop to stop a session first.
You’re on free tierHop tracking is not available for your tier.

When funds move from a hop wallet (root or any auto-discovered child) to a new address, you get:

🔗 Hop Detected — Depth 2/5
From: AlphaWallet
To: 0x5678...efgh (auto-tracked)
Amount: 5.2 ETH
Chain: Ethereum
Tx: View
Root: MainWallet
Session: 3/50 wallets

The header shows current depth out of your tier’s max, and the session count out of your tier’s wallet cap. Discovery only triggers on native or stablecoin transfers — see the concept page for the filter list.

When funds move to a known centralized-exchange deposit address, instead of auto-tracking the CEX, you get:

🏦 CEX Deposit Detected — Chain Ended
From: IntermediateWallet
To: Kraken (0x2910...5d2c)
Amount: 10.5 ETH
Chain: Ethereum
Tx: View
⚠️ Funds moved to exchange. Not auto-tracking.
Root: MainWallet

The chain stops there — the bot doesn’t follow funds further into the exchange’s hot wallets (no point — they’re commingled inside the exchange). The wallet is recorded in the session as is_cex=TRUE with the exchange name.

/hops
📡 Hop Tracking — 2 active session(s)
━━━━━━━━━━━━━━━━━━
🎯 vitalik.eth (all alerts)
Wallets: 7 | Started: 2026-04-15
└─ 0x1234...abcd
└─ 0x5678...efgh
└─ 0x9abc...ijkl 🏦 Kraken
━━━━━━━━━━━━━━━━━━
🎯 SmartMoney3 (hops only)
Wallets: 3 | Started: 2026-04-22
└─ 0xa9c1...0e5d
└─ 0xb734...c2f1

Indentation reflects depth. CEX endpoints get a 🏦 tag with the exchange name. Manually-tracked wallets that also show up in your hop tree are not specially marked here — /list is the canonical place for your manual subscriptions.

/unhop 0xd8da6bf26964af9d7eed9e03e53415d37aa96045
🛑 Hop Tracking Stopped
Root: vitalik.eth
Removed: 14 auto-tracked wallets
Kept: 3 manually tracked wallets

Auto-discovered wallets are removed from your tracking list; wallets you also tracked manually (via /track) survive — your manual subscription is independent of the hop session and continues alerting after /unhop.

The session record is marked inactive but kept for historical reference.

Hop tracking is not available on the free tier.

TierActive sessionsMax depthWallets per session
Free
Pro1320
Elite3550
Exclusive57100
Early Adopter3550

The “wallets per session” cap stops the graph from growing once a session reaches its limit — existing wallets in all mode keep alerting, but no new wallets are auto-tracked even if more funds flow outward. To explore deeper, end the session and start a new one (or upgrade tier).

Auto-discovered hop wallets count against your tier’s wallet quota the same as manually tracked wallets. A 50-wallet hop session uses 50 slots from your EVM (or Solana) pool.

TierEVM poolSolana pool
Pro25025
Elite1,00075
Exclusive5,000200

So a Pro user with 200 EVM wallets manually tracked plus a 20-wallet hop session = 220/250 — fine. The same Pro user trying a second 20-wallet session after 200 manual would fail (240/250 from existing + 20 new = over). Plan accordingly.