XRP technical analysis: separate chart geometry from confirmation

Specify the chart before the pattern

Save exchange, XRP pair, spot or derivative, interval and timestamp. XRP/USD and XRP/USDT are not automatically interchangeable; neither is a derivative mark-price series and a spot last-trade chart. Use the volume units provided by that feed.

• Keep a chart snapshot and the original observations. Missing intervals can change how many hours a fixed number of observed bars represents.
• This guide does not infer whale activity, institutional positions or orders from round prices. It also does not assume that XRP follows a permanent consolidation cycle.

A triangle is a geometric hypothesis

Define the upper line from chosen declining highs and the lower line from chosen rising lows. Fix anchors and any pivot-confirmation delay before examining the breakout. Both lines change with time, so comparing every close with a constant old boundary describes a different rule.

A worked line example prevents a timing mistake

Use invented bar coordinates: an upper line passes through (0, 2.60) and (10, 2.40), while a lower line passes through (0, 2.00) and (10, 2.20). Their equations are upper = 2.60 − 0.02t and lower = 2.00 + 0.02t. They meet at bar 15 and price 2.30.

• At bar 12, the boundaries are 2.36 and 2.24. A completed close of 2.38 is above the upper line under a zero-buffer definition. It would not be above the old 2.40 value at bar 10.
• The initial 0.60 height projected from 2.36 gives 2.96. That arithmetic establishes neither the probability nor the time of reaching 2.96.
• After the lines intersect, this converging-region specification no longer describes a triangle interior. Define expiry rather than extending the signal indefinitely.

Read the cloud at the correct timestamp

Ichimoku combines rolling high/low midpoints and displaced plots. A cloud drawn ahead uses data already calculated; the forward drawing is not observed future prices. For a price-versus-cloud test, compare price with the cloud visible at the same chart timestamp.

• Record the exact displacement convention used by the implementation. A built-in setting labeled 26 can be implemented as an offset of displacement minus one; do not silently substitute an assumed shift when reproducing it.
• The lagging close is drawn backward. An apparent historical intersection must be dated when that close was actually known.
• A cloud color change and a price exit from the cloud are different events. Neither establishes that sideways trading has ended.

A golden cross is a moving-average event

Specify SMA or EMA and chart interval. A 50-period average on an hourly chart is not a 50-day average. An upward crossing occurs when the fast series moves from at or below the slow series to above it; remaining above is a state, not a new cross.

• A cross summarizes past prices. It does not identify institutions or establish a future return.
• If a comparison uses both a cloud and moving averages, remember that both transform overlapping price history. Agreement alone is not independent statistical confirmation.

A different example: completed-bar range and volume conditions

This Pine indicator compares the close with the preceding observed range and current volume with the preceding volume average. It excludes the current bar from both reference windows. It does not detect triangle geometry, Ichimoku or a golden cross.

• Apply it to the intended XRP chart; it uses chart data without forcing an XRP symbol. Lengths and multiplier are illustrative settings.
• A missing current volume or nonpositive/missing average prevents the condition. The warm-up guard does not prove every clock interval has data; built-in functions can handle missing observations differently.
• Every qualifying completed bar can produce a condition, including consecutive new highs. It is not a single alert per drawn pattern.
• Create the desired alert in TradingView and choose once per bar close. An alert stores the script and settings from creation; recreate it after relevant changes. Alerts do not execute trades, and delivery is not a guaranteed fill.

//@version=6
indicator("Completed-bar range and volume conditions", overlay=true)
int rangeLength = input.int(20, "Prior range bars", minval=1, maxval=500)
int volumeLength = input.int(20, "Prior volume bars", minval=1, maxval=500)
float multiplier = input.float(1.5, "Volume multiplier", minval=0.1)
float priorHigh = ta.highest(high[1], rangeLength)
float priorLow = ta.lowest(low[1], rangeLength)
float priorVolume = ta.sma(volume[1], volumeLength)
bool ready = bar_index >= math.max(rangeLength, volumeLength) and not na(priorHigh) and not na(priorLow) and not na(volume) and not na(priorVolume) and priorVolume > 0
bool volumePass = ready and volume > priorVolume * multiplier
bool above = barstate.isconfirmed and volumePass and close > priorHigh
bool below = barstate.isconfirmed and volumePass and close < priorLow
plot(priorHigh, "Prior observed high", color=color.red)
plot(priorLow, "Prior observed low", color=color.green)
plotshape(above, title="Above range", style=shape.triangleup, location=location.belowbar, color=color.teal, size=size.small)
plotshape(below, title="Below range", style=shape.triangledown, location=location.abovebar, color=color.orange, size=size.small)
alertcondition(above, "Completed bar above range", "{{ticker}} {{interval}}: completed bar above configured prior range with volume filter.")
alertcondition(below, "Completed bar below range", "{{ticker}} {{interval}}: completed bar below configured prior range with volume filter.")