Notifications & Delivery
The Notifications dashboard page handles two layers of filtering that aren’t covered by the Alert Types or Chain Filter pages: a USD-value threshold (silence dust) and a per-event type toggle (mute approvals while still seeing swaps, etc.).
The dashboard page
Section titled “The dashboard page”Open the dashboard with /web, navigate to Notifications.
Minimum USD threshold
Section titled “Minimum USD threshold”Filter out transactions below a value you set. Two ways to choose:
- Preset chips — All ($0) · $100 · $500 · $1,000 · $5,000 · $10,000
- Custom input — type any number for finer control
EVM and Solana have independent thresholds. Set EVM to $1,000 (filtering noise from busy wallets) while leaving Solana at $0 (catching every memecoin scrape) — common for users who run different strategies on each chain.
The threshold is checked against the transaction’s USD value at the moment of the alert. Anything below it silently drops without consuming your hourly alert quota.
Per-event type toggles
Section titled “Per-event type toggles”Per-chain, per-event-type on/off:
- Buys · Sells · Transfers · Approvals (EVM) · Bridges (EVM) · Failed TXs (EVM) · Contract Interactions (EVM)
These are the same toggles available on the Alert Types dashboard page — both pages can flip them. The Notifications page is the quicker place to bulk-disable noisy types; the Alert Types page is where you go when you want to also customize the visual format.
Toggle off → no alerts of that type for that chain.
Per-chain notification filter (separate page)
Section titled “Per-chain notification filter (separate page)”For chain-level on/off, use Dashboard → Chain Filter. That toggles whether you receive any alerts from that chain, regardless of event type. Useful when (e.g.) you want to silence Avalanche entirely while keeping Ethereum and Base on.
Per-wallet notification toggle
Section titled “Per-wallet notification toggle”Mute a single wallet without removing it from your tracking list. Dashboard → My Wallets → click into the wallet → notification toggle. The wallet stays in your /list and the analytics view continues to update; just the Telegram alerts are silenced.
Alert usage and the rate limit
Section titled “Alert usage and the rate limit”Every tier has an hourly alert cap (Free 100/hr, Pro 1000/hr, Elite 2000/hr, Exclusive 3000/hr). Track your usage on the Dashboard page’s Alert Usage card:
- Big number:
current / limit(e.g.45/100) - Progress bar that turns orange at 80% and red at 100%
- Countdown to the next reset (
Resets in 23m) - Polled every 30 seconds
When you hit 80%, the bot sends you a Telegram heads-up so you can react before alerts start dropping. At 100%, it sends a “limit reached” notice and silently drops further alerts until the hour rolls over.
Inside the delivery layer (a quick mental model)
Section titled “Inside the delivery layer (a quick mental model)”You don’t need to know how it works to use it, but a one-paragraph summary helps you trust the system when you see something unexpected:
When the bot decides to send an alert, the message is queued in a Redis-backed BullMQ message queue (or an in-memory fallback if Redis is briefly unavailable). A small pool of workers pulls messages off the queue and sends them through Telegraf to Telegram. Per-chat rate limiters smooth out bursts (max ~20 messages/minute per private chat, 15 per group, with a 500ms minimum gap between messages to the same chat). When Telegram itself returns a 429 (rate-limit) error, the bot’s adaptive throttle halves that chat’s per-minute cap for the next 12 hours and queues the message for retry. Severe 429 bans (multi-hour) cause the affected message to drop rather than retry hours later (it’d be stale data by then).
Net result: short bursts of high activity delay slightly but don’t drop. Sustained over-volume eventually drops. You’re not expected to think about this — but if you’re seeing missing alerts, see I’m Not Getting Alerts for the diagnostic flow that maps each drop reason to a user-facing fix.
What’s not in the product (yet)
Section titled “What’s not in the product (yet)”A few things some users ask about — knowing they don’t exist saves you searching:
- Quiet hours / time-based muting — there’s no “silence between 11pm and 7am” feature yet
- Silent (no-sound) alerts — every alert is sent with Telegram’s default notification sound; there’s no
disable_notificationtoggle - Notification log in the dashboard — there’s no UI surface listing recent alerts you received (though Telegram itself is the log of record, and the Wallet Feed page is a live equivalent)
- Per-wallet alert customization — different alerts for “Vitalik” vs “RandomWallet” — alert formatting is global per chain, not per wallet