Monitor a crypto range breakout.
The range-breakout scenario observes a recent price area and waits for your configured confirmation conditions. The settings remain visible in the builder.
Configure this alertThree steps to prepare it
Set the minimum breakout and relevant confirmations.
Check the market, rule and channels.
Your chosen delivery destinations
Choose Telegram, Discord or a compatible device with the app installed and notifications allowed. One rule counts as one active alert. Check the destinations selected for this rule. Your settings and message preview remain available in the app.
Before creating your alert
Does creating an alert mean a message was sent?
Creating an alert activates monitoring. A message is sent when your condition is met and the channel is available. The preview indicates which values will be measured at the trigger.
Can I change or pause the rule?
Find your alerts in the app. You can manage their status, channels and delivery settings.
How is the range defined?
The active calculation uses closed candles from the selected pair, exchange and interval. To build the reference window, it first sets aside the evaluated candle, excludes the configured number of recent candles from the remaining history, then takes the configured lookback window. The range high is the highest high in that window; the range low is its lowest low. These reference levels can change as the window advances.
The upward boundary is the range high × (1 + buffer percentage ÷ 100). The downward boundary is the range low × (1 − buffer percentage ÷ 100). The candle close must be strictly above the upward boundary or strictly below the downward boundary. Equality does not confirm a breakout.
What confirms the breakout?
The configured number of latest closed candles must all close beyond the same boundary, in an allowed direction. A high or low that briefly crosses the boundary is insufficient if the close does not confirm it. When volume confirmation is selected, the latest evaluated candle volume must also reach the requested multiple of the average volume in the reference window. A missing or zero reference average does not confirm that volume check.
Fictional cases: two confirming closes
The following cases are independent and fictional. Each uses a 20-candle reference window with a high of 100 and a low of 90, one recent historical candle excluded, a 1% buffer, an upward direction, two confirming closes and no volume filter. The upward boundary is therefore 101; the downward boundary would be 89.1. All prices are fictional quote-currency units.
| Fictional situation | Current condition | New crossing |
|---|---|---|
| Closes 102 then 103; previous condition false | True: two closes strictly above 101 | Yes: false → true |
| Closes 102 then 103; previous condition true | True: two closes strictly above 101 | No: condition stays true |
| Closes 102 then 101 | False: equality at the boundary | No |
| Closes 100 then 102 | False: only one confirming close | No |
For a downward breakout with these same fictional levels, closes of 89 then 88 are both below 89.1. A close exactly at 89.1 fails the strict comparison. If a fictional volume filter requires 1.5 times an average of 10, a latest volume of 15 satisfies it and 14 does not; the closing-price confirmations remain necessary.
Boundaries, data and delivery
The active breakout calculation excludes unfinished candles and refuses missing, invalid, discontinuous or overly old candle data. Candle interval, lookback length, excluded candles and confirmation count have different roles; none is an exact delivery delay. A condition may already be true when first checked. A condition that stays true creates no new crossing by itself; reminders are a separate setting. A confirmed breakout can later fail or reverse, and detection does not prove a notification was received.
Choose your crypto alert
Ready to configure your alert?
Choose your market, review the condition and check your notification channel before activating your rule.

