Unit 4 · Level 2 · Tools of the trade
Alerts that matter
Staring at dashboards all day is a job; well-designed alerts do the staring for you. The craft is in the thresholds. Alert on 'any transfer from the team wallet' and you'll drown in payroll noise. Alert on 'team wallet sends more than 1% of supply to an exchange' and silence itself becomes information, because you know exactly what a ping would mean. Every alert should complete the sentence: 'if this fires, I will…'
Free to play. No ads, no token, no account needed to start.
What you get asked
What separates a useful alert from a noisy one?
The test is action-linkage: 'if this fires, I do X.' If no X exists, the alert is decoration, and decoration costs attention.
Why do too many alerts eventually make you MISS the big one?
Alert fatigue is a human failure mode, not a technical one. The hundredth harmless ping teaches your thumb a reflex that the one crucial ping will die by.
Order the steps for designing one good alert
Decision first, threshold second, action third, review forever. An alert without a pre-written response just outsources your panic to a push notification.
Good alerts are event-driven with meaningful thresholds: 'team wallet moves over 1% of supply' beats 'team wallet moves ___'.
Thresholds encode judgment. 'Anything' delegates the filtering to your tired evening brain; '1% of supply' does the filtering before the ping.
Which alert is best designed, per this lesson?
Rare event, clear meaning, obvious follow-up: investigate before the market digests it. The others fire constantly and demand nothing but your attention. 🐜
The rest of this unit
Explorers, watchlists, alerts and a daily loop: build your own on-chain radar.