Renko trading scalping strategy: signals and fill limits

How a Renko brick forms

Renko adds bricks after sufficient price movement instead of creating one candle per time interval. A continuation and a reversal have different thresholds because bricks cannot overlap in the same column. TradingView builds its Renko history from interval price data, so the selected chart interval still matters even though bricks are not evenly spaced in time.

• Illustrative fixed-size example: the last upward brick opens at 100 and closes at 101, with a box size of 1 price unit.
• The next upward brick needs a qualifying price at 102. A downward reversal needs 99, two box sizes below the last close.
• A price of 100.4 produces neither of those bricks. A fast move can produce several bricks within one source interval.
• These are construction thresholds. They do not establish when a broker could have filled an order.

Fixed size versus ATR size

Traditional sizing holds the chosen price increment constant. ATR sizing derives the increment from volatility measured on regular price bars. Neither establishes an optimal scalping setting. Start with one method, preserve its configuration, and change one assumption at a time.

Why historical bricks can differ from live signals

TradingView does not reconstruct the entire Renko history from complete tick data. When finer history runs out, older bricks can use higher-timeframe data; the boundary moves over time and may change past bricks. During an unfinished source interval, projection bricks can change or disappear. Their live sequence is not preserved after a reload. A clean historical staircase is therefore insufficient evidence that the same signals were available live.

• Record the symbol, exchange, session, source interval, close or OHLC source, sizing method, and test date.
• Log signals during a forward simulation, then compare their timestamps and direction with the chart after reloading.
• Keep projections out of a close-confirmed test. Waiting for a close does not prevent later historical reconstruction.

An illustrative scalping rule to investigate

The following long-only specification is a research example, not a tested or recommended strategy. It samples Renko direction at standard candle closes. It does not pretend that each host candle represents one brick or recover every brick formed inside that candle.

• Use a standard one-minute chart and fixed box size B, selected before the test and expressed as a valid multiple of the minimum tick. Keep symbol, data source, and dates fixed.
• At each closed standard candle, compare the requested Renko close with its open. When the sampled direction changes from down to up and the strategy is flat, submit one market entry. Skip missing or equal open/close values.
• Use a fixed simulation quantity, no pyramiding, and default next-tick market fills. Do not assign the entry to the earlier Renko threshold.
• Place a stop 2B below the simulated entry and a target 2B above it. Close on the first sampled downward direction or after five completed standard candles following entry, whichever occurs first; a stop or target can close the trade sooner.
• Choose a session window before testing. Accept entries only inside it, and submit a close at its final standard candle. Record any fill outside that window under the execution model.

Separate the Renko signal from the fill price

TradingView warns that a strategy running directly on a Renko chart uses synthetic prices for its fills. Its Pine documentation demonstrates requesting Renko values while the strategy runs on a standard chart instead. That arrangement separates the signal feed from the price series used by the broker emulator. Merely requesting standard prices inside a strategy still attached to a Renko chart does not change the emulator into a standard-chart test.

• Keep the execution chart on standard candles. Request Renko data for signal calculation and inspect the returned series and its timing.
• Under default strategy settings, market orders fill on the next available tick, usually the next standard bar open in a historical test. A threshold reached inside the previous bar is not an available retrospective entry.
• The standard-OHLC fill option documented for Heikin Ashi is not a general switch that repairs Renko backtests.
• Standard bars still simulate execution. They do not restore missing tick paths, remove Renko reconstruction, or prove that a live order would fill at the simulated price.

Audit small targets before optimizing brick size

Scalping leaves less room for execution costs. In a hypothetical trade with a gross gain of 0.50 price units and total entry-plus-exit costs of 0.10 per unit, costs consume 20% of that gross gain. This arithmetic is not a performance estimate. Use the instrument contract value and position size when translating price movement into money.

• Compare standard-price trade timestamps and fills with the signal log. Reject results that rely on entry before the signal was observable.
• Include commission, slippage, and a stated spread assumption without charging the same cost twice. Repeat with higher costs.
• Inspect bars that touch both stop and target. Their order can be ambiguous without finer data; document the emulator assumption and available intrabar coverage.
• Report trade count, net average trade, drawdown, and holding time. If a small cost increase reverses the conclusion, more parameter searching does not resolve that execution sensitivity.
• Only after those checks, compare nearby box sizes on development data, freeze the rule, and evaluate an untouched period followed by a forward simulation.