The Green Candle Trap

Video: THE GREEN CANDLE TRAP MOST TRADERS FALL FOR
Creator: Oliver Velez Trading
Original Video: Watch the original video
Difficulty: Intermediate

The Big Idea

A candle’s color describes one interval, not the entire opportunity. The source asks when a rising candle is a countertrend rebound beneath overhead references, then waits for completed bearish evidence. The learning task is to define that context and the event that would challenge it, without turning a simple pattern into a guaranteed short.

The Color Is Local; the Context Is Broader

The creator studies a two-minute chart with a 20-period SMA and a 200-period SMA. The bearish example trades beneath prior-day data, a declining 20, and an overhead 200. A small green candle can therefore be a rebound inside a broader decline rather than evidence that the whole structure has reversed.

The phrase under everything refers to those particular references. It does not mean every possible timeframe or participant agrees. The source explicitly allows exceptions in which an early long could work; its argument is about a preferred recurring context, not certainty about every green candle.

The transcript describes a gap-down example and monetary outcomes for large share counts. Those are source illustrations without a complete audited ledger here. The claim that seventy-two percent of new highs fail is also not accompanied by a definition, market sample, period, or reproducible test. It should not be imported as a general probability.

Specify What Prior-Day Data Means

A previous day contains many prices and several possible references. To make a narrow research version reproducible, the code interprets all prior-day data overhead as a completed close below the previous daily low. That is a stronger, more specific proxy than merely being below some yesterday price.

The daily low depends on the provider and session convention. A regular-session daily candle and an extended-session view may differ. Save the symbol, feed, and session setting when comparing examples, rather than assuming an identical prior-day ceiling across charts.

The three-bar slope lookback and adjacency rule are ours. They make a smaller, testable subset of the source idea. They do not prove that every rejected case was a good long or that every accepted case was a successful short.

Wait for the Red Candle to Finish

The source’s core execution observation is a red candle closing below the relevant low of a green candle. For most learners, it favors waiting until the red candle completes. A developing candle can cross the reference and then recover before its close.

The presentation allows using body boundaries instead of tails for a more aggressive interpretation. The code exposes that choice: Body uses the prior green candle’s lower body edge; Wick uses its low. These select different events and should be compared separately.

For clarity, the proxy requires both the prior green close and the current red close to satisfy its overhead context. The marker appears on the completed red candle, never before its final close is available. That marker remains distinct from an actual entry on the next available executable price.

Tie Invalidation to the Evidence You Used

The creator explains protecting above the red candle because a move beyond it removes the immediate reason for the short. A nearby reference can make planned price-distance risk small. It does not make a loss harmless regardless of size, slippage, gaps, or available liquidity.

The source discusses intrabar movement inside two-minute candles, but a historical candle does not preserve the full path by itself. A finished red candle cannot retrospectively authorize an earlier fill at its high. Keep signal time, order time, and fill price separate in any manual comparison.

What Would Make the Bearish Context Less Persuasive?

The presentation looks beyond a mere cross of the 20 SMA and describes a green candle removing two red candles as a warning that buyers are gaining influence. It also discusses the number of downward legs and whether a move is extended. Those are additional observations, not a promise of an immediate bottom.

The indicator implements only the adjacent-two-red warning: a completed green close exceeds both selected red upper references after bearish context. It does not count legs or decide whether a full reversal has begun. The warning is a reason to reassess the short hypothesis, not an automatic long entry.

The source also mentions retracement fractions for a larger downward move. The exact move anchor and execution variation are discretionary in the excerpt. That location model is not silently combined with the adjacent-candle baseline, because doing so would add another unmeasured selection rule.

Compare the Body and Wick Conventions Honestly

A body break can qualify sooner or with a smaller movement than a wick break, but that does not necessarily provide better execution. A larger signal candle may increase stop distance. A more selective wick definition may avoid some failures while omitting profitable continuations.

Record all eligible green rebounds before seeing what happens. If the source’s warning condition appears, preserve the earlier short outcome rather than treating the warning as if it had been known at entry. This keeps context revision from becoming hindsight.

Pine Script Indicator

//@version=6
// Guide: https://candlechasers.com/green-candle-overhead-context/
// Original adjacent-candle interpretation. No orders, fills or failure-rate estimate.
indicator("CC Green Candle Overhead Context", overlay=true)
method = input.string("Body", "Green/red reference boundary", options=["Body", "Wick"])
slopeBars = input.int(3, "SMA 20 decline lookback: original default", minval=1)
life = input.int(15, "Latest red-high display lifetime", minval=1)
sessionInput = input.session("0930-1200", "Observation session")
zone = input.string("America/New_York", "Session timezone")
valid = chart.is_standard and timeframe.isintraday
inSession = not na(time(timeframe.period, sessionInput, zone))
m20 = ta.sma(close, 20)
m200 = ta.sma(close, 200)
priorLow = request.security(syminfo.tickerid, "1D", low[1], lookahead=barmerge.lookahead_on)
underAll = close < priorLow and close < m20 and close < m200 and m20 < m20[slopeBars]
green = close > open
red = close < open
greenFloor = method == "Body" ? math.min(open[1], close[1]) : low[1]
signal = valid and inSession and barstate.isconfirmed and underAll and underAll[1] and green[1] and red and close < greenFloor
upper1 = method == "Body" ? math.max(open[1], close[1]) : high[1]
upper2 = method == "Body" ? math.max(open[2], close[2]) : high[2]
warning = valid and inSession and barstate.isconfirmed and underAll[1] and red[1] and red[2] and green and close > math.max(upper1, upper2)
var float lastRedHigh = na
var int born = na
if barstate.isconfirmed
    if warning
        born := na
    if signal
        lastRedHigh := high
        born := bar_index
plot(m20, "SMA 20", color=color.blue, linewidth=2)
plot(m200, "SMA 200", color=color.red, linewidth=2)
plot(valid ? priorLow : na, "Prior completed day low: overhead-data proxy", color=color.orange, style=plot.style_stepline)
plot(not na(born) and bar_index - born <= life ? lastRedHigh : na, "Latest signal red high: visual invalidation reference, not order", color=color.fuchsia, style=plot.style_linebr)
bgcolor(valid and inSession and underAll and barstate.isconfirmed ? color.new(color.red, 94) : na)
plotshape(signal, "Completed red removes preceding green", shape.triangledown, location.abovebar, color.red, size=size.small)
plotshape(warning, "Green removes two adjacent reds: caution, not long entry", shape.diamond, location.belowbar, color.aqua, size=size.small)
alertcondition(signal, "Red eliminates green context", "CC: completed red closes below prior green reference under overhead-context proxy. Check risk, liquidity and execution.")
alertcondition(warning, "Two-red recovery warning", "CC: completed green removes two adjacent red references. Reassess bearish context; not an automatic long.")
var table status = table.new(position.top_right, 1, 2, bgcolor=color.new(color.black, 10))
if barstate.islast
    table.cell(status, 0, 0, not valid ? "Use STANDARD intraday chart (source: 2 minutes)" : na(m200) ? "Load at least 200 chart bars" : underAll ? "Under prior day + declining 20 + 200" : "Overhead conditions not all present", text_color=color.white, text_size=size.small)
    table.cell(status, 0, 1, method + " boundary | " + sessionInput + " | " + zone + " | no leg counting", text_color=color.white, text_size=size.small)

What This Indicator Shows

The script plots SMA 20, SMA 200, and the prior completed daily low. Red triangles identify completed adjacent green/red observations under the stated overhead proxy. A magenta line displays the latest signal red candle’s high for fifteen bars by default; a newer signal replaces it. A two-red recovery warning clears that displayed reference. It is a visual map, not a broker stop or position tracker.

Use a standard intraday chart, preferably two minutes to study the source’s example. The default observation window is 09:30–12:00 America/New_York. The status panel explains missing 200-bar history or absent context. Aqua diamonds identify the separate two-red warning. Both the decline lookback and session are editable original research choices.

What This Indicator Does Not Show

It does not establish the quoted new-high failure rate, reproduce every nonadjacent green reference, count downward legs, detect a complete bottom, or implement the separate retracement-entry method. Repeated qualifying adjacent pairs can each mark; there is no pyramiding or account simulation. Moving averages can develop intrabar, but event markers require the completed chart candle. The prior-day request uses only the completed day.

Setup and Validation

Paste the complete code into TradingView’s Pine Editor, save it, and add it to the chart. Use the chart type, timeframe, and context described above, then inspect the status panel and reference plots before expecting a marker. Use Once Per Bar Close for the supplied alert conditions and recreate alerts after changing code or settings. No alert submits an order.

Validation status: Statically reviewed for completed-bar timing, source-versus-proxy distinctions, future-data use, state behavior, reference replacement and expiry, and visible output. This code has not been compiled or chart-tested in TradingView here. No historical performance or live-execution results are claimed. Use replay to check the described behavior and report any compiler or runtime message exactly.

Practice: Audit the Candle and Its Context

1. Prepare: record chart interval, session, yesterday reference convention, and the SMA slope rule before replay.
2. Classify: find ten green rebounds with outcomes hidden. Mark which satisfy each overhead condition, including failures of the checklist.
3. Choose: use Body or Wick before inspecting the next red candle. Record when its close completes.
4. Calculate: use a realistic hypothetical or recorded fill, the chosen invalidation, target, and share size. Keep price risk and money risk separate.
5. Challenge: timestamp any two-red recovery warning and explain whether it was known before or after the proposed entry.

Answer check

In the example, 99.80 to 101.20 is 1.40 of risk, so 500 shares represent $700 before costs. A later fill at 99.20 increases that risk to $1,000 for the same shares and reduces the ratio to 1.1R. A two-red warning is a later observation, not evidence that the preceding signal never existed.

Research and Comparison Lab

These are original proposed experiments, not results established by the source. Change one main feature at a time, retain failures and missing opportunities, and reserve later observations for evaluation rather than repeatedly selecting rules from the same outcomes.

Does overhead context change the event sample?

Compare all adjacent red-below-green closes with the subset meeting the prior-day and SMA rules. Keep boundary type, session, period, and independent exit convention fixed. Record removed winners and losers, costs, and the distance to the next opposing level.

Does Body versus Wick help?

Compare both definitions on the same pre-recorded green candles. Keep entry timing and invalidation methodology explicit. Measure qualification delay, actual risk distance, and untriggered opportunities rather than choosing the earlier price after seeing the outcome.

Does the two-red warning add usable information?

Predefine how a completed warning would change a still-open hypothetical position and compare against unchanged management. Use information available at the warning time. Record premature exits of later winners as well as avoided further losses.

Check Your Understanding

Does green automatically imply a long opportunity? No. It describes one candle, not the full context.

Is the seventy-two-percent claim established here? No. Its sample and definitions are not supplied.

Does the code interpret all prior-day data literally? No. It uses the previous daily low as an explicit proxy.

Can the signal close guarantee the next fill? No. Execution may differ.

Is a two-red warning an automatic long? No. It is a context-reassessment observation.

Final Takeaway

The source’s useful idea is to read a rebound against its overhead references and wait for completed evidence. Use the guide to distinguish a candle pattern, its context, a realistic fill, and a later warning—without turning a simple visual rule into a certainty claim.

Risk Disclosure

This material is educational and is not personalized financial, investment, or trading advice. Trading can cause substantial losses. Source-reported results, hypothetical examples, and probability illustrations do not establish future performance. Calculations depend on their assumptions and omit costs unless stated. Commissions, spread, slippage, gaps, leverage, liquidity, borrowing, financing, and changing market conditions can materially affect outcomes. Indicators do not simulate broker execution or establish profitability. Short exposure can involve losses beyond the initial sale value. Evaluate any approach with appropriate data, realistic costs, and explicit risk limits before considering live use.

This is an independent educational companion and is not affiliated with, sponsored by, endorsed by, or authorized by the source creator, channel, or TradingView.