Guard 1. Arm grace kills quote lag phantoms
Fresh alarms ignore the first 60 seconds of evaluation. That window absorbs late quotes, reconnect gaps, and backfill after websocket drops. Without it, a stale print that looks like a break triggers instantly. With it, only live sustained trading can fire.
Guard 2. Distance floors block thin wicks
Crypto needs a hard floor near 0.2 percent with a warning band near 1.5 percent. Alarms set too close to spot warn before arming, since normal noise would wake you hourly. This single rule prevents most midnight complaints seen on generic alarm apps, where any wick near the level sounds.
Guard 3. Stale quarantine never fires on old data
If venue data goes stale beyond 60 seconds, evaluation holds instead of firing. After reconnect, HTTP backfill resyncs before arming resumes. Stale prices are never replayed as fresh breaks. That is how the system survives exchange outages without waking the entire user base incorrectly.
Guard 4. Cooldowns and caps contain volatility
After firing, an alarm cools down for 30 minutes, fires at most once per day per target, and each user caps at 10 alarms per day. One volatile night cannot spam you or degrade delivery for others. Combined with single venue focus from venue exact design, the surface for false wakes shrinks to sustained venue specific moves only.
What this means for your sleep
Set one level that matters on wakever.com on Binance or OKX spot or perp. If the alarm sounds, the move held on your venue. If it stays quiet, chop stayed chop. That contract is the product. More background is in what Wakever Crypto Alarms is and FAQ.