Hop Tracking Explained

Hop tracking starts from a wallet you already track (the root) and follows native and stablecoin transfers outward — when funds move from your root to a new wallet, the bot automatically subscribes you to that wallet too. Repeat the process, and you build a tree of related wallets several hops deep. When funds hit a known centralized exchange, you get a “CEX deposit detected” alert and the trail ends there.

It’s a power-user feature for tracing fund flows, finding the ultimate destination of a sale, or mapping out a smart-money network.

The two modes

/hop <address>          → start a session in 'all' mode
/onlyhop <address>      → start a session in 'hops_only' mode
/hops                   → list active sessions
/unhop <address>        → stop a session and clean up auto-tracked wallets

Both /hop and /onlyhop require the address to already be tracked manually first.

Mode	What you get
`all` (via `/hop`)	Discovery alerts when new wallets appear, CEX detection alerts, plus every full alert for every discovered wallet (treats them like normal tracked wallets).
`hops_only` (via `/onlyhop`)	Discovery alerts and CEX detection only. Regular activity on the root wallet and discovered wallets is suppressed. Use this when you want to map the graph without drowning in trade alerts.

What gets followed

Hop discovery only triggers on native currency or stablecoin transfers — ETH, BNB, AVAX, SOL, USDT, USDC, DAI, and similar. This is intentional: tracking every random shitcoin transfer would explode the graph in seconds.

So if your root wallet:

Sends 5 ETH to a new wallet → discovery alert, new wallet auto-tracked
Sends 1,000 USDC to a new wallet → discovery alert, new wallet auto-tracked
Sends an obscure memecoin to a new wallet → ignored (not a hop trigger)
Sends ETH to Binance hot wallet → CEX detection alert, trail ends (no auto-track)

Once auto-tracked, a hop wallet’s own outgoing native/stablecoin transfers feed back into the discovery loop — that’s how the tree grows beyond depth 1.

The discovery alert

When a hop fires, you get a Telegram message that looks roughly like:

🔗 Hop Detected — Depth 2/5
From: Smart-Money-3
To: 0xa9c…f4b1 (auto-tracked)
Amount: 12.5 ETH
Chain: Ethereum
Tx: 0xabc…
Root: Smart-Money-3
Session: 7/20 wallets

The header tells you which depth in the chain (2 of your max 5), what was sent, and how full the session is.

CEX detection

The bot maintains a registry of known centralized-exchange deposit addresses. When a hop wallet sends funds to an address in that registry, instead of auto-tracking the CEX (you don’t want to subscribe to Binance’s hot wallet), you get this:

🏦 CEX Deposit Detected — Chain Ended
From: Smart-Money-3 → 0xa9c…f4b1
To: Binance (0xf977…b88a)
Amount: 12.5 ETH
Chain: Ethereum
Tx: 0xabc…
⚠️ Funds moved to exchange. Not auto-tracking.
Root: Smart-Money-3

That branch of the graph is closed — the bot won’t follow the funds further (no point — they’re commingled inside the exchange).

Tier limits

Hop tracking is not available on the free tier. Limits per tier:

Tier	Max active sessions	Max depth (hops)	Max wallets per session
Free	—	—	—
Pro	1	3	20
Elite	3	5	50
Exclusive	5	7	100
Early Adopter	3	5	50

The depth cap is inclusive of the root — at depth 3, the chain is root → hop1 → hop2 → hop3 (CEX deposits also count as a hop endpoint).

The “wallets per session” cap protects you from runaway graphs — once a session hits 20 (Pro) / 50 (Elite) / 100 (Exclusive) discovered wallets, no new wallets are added (existing ones still get activity alerts in all mode; the graph just stops growing).

Stopping a session

/unhop <address> ends the session and cleans up:

Discovered hop wallets that you don’t otherwise track manually are fully unsubscribed
Discovered hop wallets that you also tracked manually stay subscribed (your manual subscription survives independently)
The session records and auto-discovered tree are removed from the database
You’ll see a summary message: Session ended. Removed: 14 · Kept: 3

Practical use cases

Some patterns we see users running:

Where did the rug go? — track the deployer, /onlyhop it, watch the funds get bridged or deposited to an exchange.
Smart-money network mapping — track 10 known smart wallets, /hop them all, build a graph of who funds whom. Activity alerts on hop wallets surface coordinated entries you’d otherwise miss.
Cross-checking with cluster alerts — if a hop-discovered wallet later shows up in one of your personal cluster alerts, you’ve got a strong signal that the funding source is feeding into a coordinated entry on a token.

What’s next

Groups vs Private Sharing a wallet list with a Telegram group.

Hop Tracking settings Configuring depth, session limits, and modes.