Chains & Networks
The bot tracks wallets on five chains — four EVM-compatible plus Solana. Coverage is the same in spirit across all five (real-time alerts for every event type), but the underlying detection is different on Solana.
Supported chains
Section titled “Supported chains”| Chain | Native | Block time | Detection |
|---|---|---|---|
| Ethereum | ETH | 12 s | Block scanner |
| BSC | BNB | 3 s | Block scanner |
| Base | ETH | 2 s | Block scanner |
| Avalanche (C-Chain) | AVAX | 2 s | Block scanner |
| Solana | SOL | 0.4 s | Helius webhook |
See How Tracking Works for the technical model behind each.
EVM addresses are tracked across all four EVM chains
Section titled “EVM addresses are tracked across all four EVM chains”This is the part new users miss. When you /track an EVM address, the bot watches it on Ethereum + BSC + Base + Avalanche simultaneously — the same wallet on all four chains, one tracked entry, one wallet-quota slot.
If 0xabc… swaps on Ethereum, you get an alert. If the same wallet bridges to Base and trades there an hour later, you get another alert. If it shows up on BSC tomorrow, alert. No need to track the same address four times.
The chain is auto-detected on each transaction — every alert is labeled with its source chain.
Solana addresses are different (different format — base58, 32-44 chars) and tracked on Solana only.
DEX coverage
Section titled “DEX coverage”The bot recognizes activity on the major DEXs and routers on every chain:
Ethereum / Base / Avalanche / BSC
Uniswap (V2/V3/Universal), PancakeSwap (V2/V3), SushiSwap, BaseSwap, Aerodrome, TraderJoe, Pangolin, plus aggregators 1inch, 0x Protocol, ParaSwap. Solver/intent protocols including Relay, CoW, UniswapX, and 1inch Fusion are detected via event-log scanning, so transactions you’d miss watching tx.from/tx.to directly are still classified correctly.
Solana (surfaced by name from Helius)
Pump.fun (PUMP_FUN, PUMP_AMM, PUMP_SWAP), Raydium (V4, AMM, CLMM, CPMM), Jupiter (incl. Jupiter Aggregator), Orca (incl. Whirlpools), Meteora (DLMM), Lifinity, Phoenix, OpenBook, OKX DEX Router. NFT marketplaces Tensor and Magic Eden surface as their own labeled events.
Bridge coverage
Section titled “Bridge coverage”Cross-chain bridges are detected and labeled in alerts. The bot recognizes 25+ protocols including:
- Native bridges — Stargate / LayerZero, DeBridge, Across, Synapse, Hop, Celer cBridge, Wormhole, Axelar, Multichain, Connext, Orbiter Finance
- Aggregators — LI.FI, Socket / Bungee, Relay, XY Finance, Rubic
- Official rollup bridges — Arbitrum, Optimism, Base, Polygon, Avalanche, zkSync, Linea
Bridge alerts include the protocol name, source and destination chains, and (for protocols with on-chain order data like DeBridge) the order completion status.
What’s different on Solana
Section titled “What’s different on Solana”A few user-facing differences worth knowing:
- Faster alerts. Sub-second to ~1 second, vs ~5–20 seconds for EVM. Helius pushes parsed transactions immediately.
- DEX names are explicit. Alerts label the protocol (
PUMP_FUN,RAYDIUM, etc.) so you immediately see whether a buy was on a fresh-launch pump or a deeper-liquidity Raydium pool. - Compressed NFTs supported. Solana’s compressed-NFT mints are detected.
- Token-2022 supported. The newer Solana token standard is picked up alongside SPL.
- Separate wallet quota. Solana wallets count against a separate Solana-specific limit (3 on free, 25 on Pro, 75 on Elite, 200 on Exclusive) — not the EVM pool.
Disabling chains without un-tracking wallets
Section titled “Disabling chains without un-tracking wallets”You don’t have to remove a wallet to silence its alerts on a specific chain. The Chain Filter in the dashboard lets you toggle each of the five chains on/off independently.
Common patterns:
- EVM-only trader — disable Solana to silence webhook events
- Solana-only degen — disable all four EVM chains
- Avoid one chain — e.g. mute BSC if you’re tired of seeing rug copies of every token
This is a per-user setting (groups have their own chain filter, settable separately).