| Warn within | Zone around a 58,000 mark | When you need it |
|---|---|---|
| 0% | — | You only want the crossing of 58,000 itself |
| 1% | 57 420 — 58 580 | A few minutes are enough to place an order |
| 2% | 56 840 — 59 160 | The level is far off and you want the approach in advance |
| 5% | 55 100 — 60 900 | The field maximum; on a volatile coin it fires long before the mark |
These are the same sets applied with one click in the screener settings. The values below are exactly what gets filled in.
BTC · nearest round levels above and below
Logic: two marks — the nearest round level above and below the current BTC price. The levels are computed from the market at the moment you apply the preset, not baked in, and they stay editable. Repeat off, at most 1 hit a day: a quiet heads-up that price has left the corridor.
BTC and ETH · one level above, one below
Logic: the nearest round level above and below the current price for BTC and for ETH — four marks, computed from the market when you apply the preset. Repeat off, up to 3 hits a day per coin.
BTC, ETH, SOL · level above only
Logic: one mark per coin — the nearest round level above the current price, direction set to upward only. Pullbacks stay silent, only the move up comes through. Up to 5 hits per 12 hours per coin.
BTC, ETH, SOL · level below only
Logic: the nearest round level below the current price on each of the three coins, direction set to downward only. Repeat is on: price revisits a round number several times, and every visit is worth a look. Up to 3 hits per 12 hours per coin.
Any set is a starting point, not a recommendation. Once applied the thresholds are yours: move them and the screener starts counting the new way immediately.
A mark fires on a crossing and has no tolerance band: the boundary runs through the exact figure you typed. Illustrative example: with price at 58,000 a mark at 58,050 fires on the first wobble, while 60,000 is an event. Judge by the coin’s usual daily range, not by how round the number looks.
The base ticker: BTC. The price is always in USDT. The screener picks one pair per coin, the most suitable one — otherwise BTCUSDT and BTCUSDC would produce two alerts for a single mark.
It is the width of a zone around the mark, as a percentage of its price, up to 5; an empty field means no warning. Illustrative example: 1% on a mark of 58,000 gives a zone of 57,420 — 58,580, and the alert arrives the minute price enters it. Set as much as you need to prepare an order; if you only want the crossing itself, leave it at 0.
Three common reasons: the list of marks is empty (such a save is accepted, and the screener runs with nothing to watch); the mark has already fired and gone quiet; the direction is the opposite of the side price approaches from. An incomplete mark cannot be saved: every row needs a coin and a price above zero.
No. A single-use mark fires once anyway, and the cap changes nothing. It matters with repeats on: the cap is then counted per mark, and the default period is 24 hours.
Up to 50 per account — on different coins, or several on one. At the limit the add button switches off and a line about the cap appears next to it.
A single alert listing the marks it went through, line after line. Each mark is recorded separately in the ledger, so only the ones that actually fired go quiet.