The timeframe field decides which candle interval the strategy is
checked on. Every indicator computes on closed bars of this interval.
Entry and exit conditions evaluate once per closed bar - unless a
condition opts into on-tick evaluation.
Supported intervals
| Timeframe | Closed bar cadence | Typical use |
|---|---|---|
1m | every minute | scalping, fakeout patterns, killzones |
5m | every 5 min | intraday scalp/swing hybrid |
15m | every 15 min | intraday trend following |
1h | hourly | swing entries, session bias |
4h | every 4 hours | multi-day positions |
1d | once a day | weekly swing, regime detection |
Trade-offs
Higher timeframes mean fewer signals, more lag in reacting to moves, but cleaner indicator readings. Lower timeframes mean more signals, faster reaction, but more chop.
Per-trade costs are constant but per-unit-of-return they scale inversely with how long you hold. A 1m strategy that pays 5bps round- trip and targets 0.3% per trade burns 33% of edge on fees alone. A 4h strategy targeting 2% per trade burns 5%. Pick the timeframe whose trade size dwarfs your cost stack.
Backtest sample size
Pick a timeframe that gives you at least a few hundred trades over the backtest window. A 1d strategy with five trades a year produces a sample that's almost meaningless. Trade count is one of the headline metrics on the backtest detail page - check it.
Aligning timeframes across exchanges
Binance Futures candles drive signals for every crypto strategy in LucraX. The timeframe in the strategy is honored on every supported venue; you pick the timeframe per strategy and it stays.
Every indicator in a strategy computes on the strategy's base timeframe. Mixed timeframes inside one strategy are not supported.