Alerts and watchlists
Let each user define their own trading-risk alerts
TokenSentry should not decide what matters to every trader. The product should let users choose the thresholds, channels, and monitoring cadence that match their own strategy.
Private access
Each user gets their own alert workspace
This should feel like a private control room, not a public calculator. Users sign in, keep their watched tokens, and adjust notification rules over time without rebuilding everything from scratch.
Saved presets
4
Watched tokens
12
Alert channels
3 active
Workspace preview
What the user sees after login
PEPE
Ethereum
Notify on risk jump > 10 pts
BONK
Solana
Telegram alerts for liquidity drops
WIF
Solana
Muted until volatility settles
Account model
Access
Email + password or magic link
Private area contents
Watchlists, channels, billing, alert history
Best v1 auth
Clerk or Supabase Auth
Alert builder
Users choose what counts as meaningful
Different traders use different risk rules. TokenSentry should let each user define their own triggers, save the watch settings, and update them over time as their strategy evolves.
Delivery channels
Trigger types
Thresholds
Preview
Fast monitoring
Check watched tokens every 5m. Notify via email when the risk category changes, when the score changes by 10+ points, or when any selected custom trigger fires.
Delivery
Cadence
Every 5m
Liquidity floor
$50000
Workspace nav
Credit balance
1,420
Enough for roughly 23 days at current monitoring settings.
Active watches
12
9 active, 3 paused across 4 chains.
Alerts today
7
2 high-severity triggers need review.
Monitoring burn
26/day
780 credits estimated over 30 days.
Monitoring overview
Continuous monitoring dashboard
Recent alerts
BONK
12 min agoLiquidity dropped below the user-defined floor and risk score increased by 15 points.
AERO
1 h agoRisk category moved from Low to Medium after a holder concentration change.
PEPE
YesterdayPrice movement triggered monitoring, but no custom risk thresholds were breached.
Next scheduled checks
Why users pay
Credits fund continuous checks, not one-off pings. Faster cadence and more monitored tokens increase usage in a way the user can understand and control.
Monitoring economics
Charging model
Credits pay for continuous monitoring, not per alert sent
Current cadence
Every 5m across 4 saved tokens
Cost drivers
More tokens, faster checks, more channels, richer rules
User database
Saved tokens and configured alert sets
The private area should store the user's token universe, their active alert presets, and the history of what actually fired, so they can refine the rules over time.
Risk worsens fast
Scope
All watched tokens
Channel
Email + Browser push
Rule
Send when score worsens by 10+ points in one refresh.
Liquidity danger floor
Scope
PEPE, BONK, WIF
Channel
Telegram
Rule
Alert if liquidity falls below $50,000 or drops sharply.
Contract-event monitor
Scope
Ethereum and Base
Channel
Webhook
Rule
Notify on honeypot flips, mintability changes, or proxy/owner risk flags.
Alert history
Triggered events feed
BONK
12 min agoLiquidity dropped below the user-defined floor and risk score increased by 15 points.
AERO
1 h agoRisk category moved from Low to Medium after a holder concentration change.
PEPE
YesterdayPrice movement triggered monitoring, but no custom risk thresholds were breached.
Future execution layer
Telegram bot can sit on top of the alert engine later
The user space should already anticipate bot-based execution, even if we do not activate it yet. The immediate job is to build a solid watchlist, alert-rule, and alert-history foundation.
Phase 1
Notification-only
Email, push, Telegram, Discord, webhook. No trading actions.
Phase 2
Telegram bot control
Users subscribe their bot, receive alerts, and acknowledge or mute rules.
Phase 3
Trade execution layer
Only after permissions, auditability, and user controls are fully designed.
Telegram readiness
Bot status
Disabled for now
Needed later
Bot token, user chat mapping, permissioned commands, audit log
Current focus
Database-backed workspace, saved tokens, alert rules, triggered-event history
How users receive alerts
Start with email, then expand
- Email is the lowest-friction v1 and easiest to monetize.
- Browser push is useful for active desktop users but requires permission and subscription state.
- Telegram, Discord, and webhooks are strong paid-tier channels for more advanced users.
What real-time means
Near real-time is realistic, true instant is expensive
- For v1, poll watched tokens every 1 to 5 minutes and compare the new report to the previous snapshot.
- That is fast enough for most users and much cheaper than maintaining full chain-level live streams.
- Only move to true streaming when you know which events users actually pay for.
Proposed backend
Watchlist + scheduler + notifier
- Store user watchlists, trigger preferences, and previous report snapshots in a real database.
- Run scheduled checks, generate diffs, then send alerts only when a user-defined rule is matched.
- Use per-user API or channel credentials only for delivery, not for the core risk computation.