XRP · Closed candles only
XRP: Wyckoff markup — accumulation, distribution and phases
XRP now: 1H — distribution, phase A; 4H — no range; 1D — no range.
Scanner snapshot: . Latest event: .
Latest available closed candles: 1H: ; 4H: ; 1D: .
Instrument panel
Event history over 30 days
Instrument rows: 5. Candle close time in MSK; UTC is available in the tooltip.
| When | TF | Event | Phase | Outcome |
|---|---|---|---|---|
| 1H | Range closed | C | invalidation | |
| 1H | Test | C | no result | |
| 1H | UTAD | C | invalidation | |
| 1H | Range closed | B | invalidation | |
| 1H | Spring | C | cancelled |
Two-year statistics
Event types and timeframes are counted separately. n includes completed outcomes only; cancelled and waiting events are excluded. Shares are withheld when n < 20.
2024-10-01 — 2026-10-01. Using available scanner history; no observations does not mean zero probability.
| TF | Type | n | Target | Invalidation | No result | Cancelled / waiting |
|---|---|---|---|---|---|---|
| 1H | Spring | 22 | 31.8% | 50.0% | 18.2% | 17 / 0 |
| 1H | UTAD | 24 | 16.7% | 79.2% | 4.2% | 6 / 0 |
| 1H | Test | 36 | 27.8% | 0.0% | 72.2% | 3 / 0 |
| 1H | LPS | 14 | Insufficient data | 9 / 0 | ||
| 1H | LPSY | 4 | Insufficient data | 1 / 0 | ||
| 1H | SOS | 5 | Insufficient data | 8 / 0 | ||
| 1H | SOW | 3 | Insufficient data | 1 / 0 | ||
| 4H | Spring | 2 | Insufficient data | 4 / 0 | ||
| 4H | UTAD | 3 | Insufficient data | 2 / 0 | ||
| 4H | Test | 1 | Insufficient data | 0 / 0 | ||
| 4H | LPS | 4 | Insufficient data | 0 / 0 | ||
| 4H | LPSY | 2 | Insufficient data | 0 / 0 | ||
| 4H | SOS | 1 | Insufficient data | 0 / 0 | ||
| 4H | SOW | 1 | Insufficient data | 0 / 0 | ||
| 1D | Spring | 1 | Insufficient data | 0 / 0 | ||
| 1D | UTAD | 0 | Insufficient data | 0 / 0 | ||
| 1D | Test | 0 | Insufficient data | 0 / 0 | ||
| 1D | LPS | 0 | Insufficient data | 0 / 0 | ||
| 1D | LPSY | 0 | Insufficient data | 0 / 0 | ||
| 1D | SOS | 0 | Insufficient data | 0 / 0 | ||
| 1D | SOW | 0 | Insufficient data | 0 / 0 | ||
Reading XRP markup
For XRP, the exact level of a return is more useful than the size of a coloured candle body alone. Prices are displayed at the instrument’s own precision, so a small absolute move can occupy a substantial part of its current corridor. The scanner does not compare these distances with Bitcoin’s dollar distances. XRP uses completed hours, four-hour blocks and daily candles. Each scale has its own events, boundaries and separate outcome sample.
The XRP sequence can be investigated as a check of an area’s resilience: initial departure, return, another approach and the state machine’s decision after the close. A Spring label without a later test is not equivalent to an entire completed cycle. Cryptocurrency scheduling keeps weekend observations in history. Candle volume belongs to the XRP market feed and does not measure transfers between every address. If a new working area develops on the chart, old events are not transferred into it. When comparing two periods, inspect the range identifier and final outcome: waiting, invalidation and no result mean different things. The number of completed cases matters more than the visual resemblance of two drawings. The separate daily panel helps retain this distinction when a short-lived hourly corridor disappears.
The server view for XRP: 1H — distribution, phase A; 4H — no range; 1D — no range. Available instrument history contains 5 rows over 30 days; 123 completions across separate two-year samples. The opening line records the snapshot state rather than a forecast. Compare its time with the latest event time: an old label does not become current merely because no newer event exists. Each XRP scale keeps an independent phase, and no range does not mean distribution. Numbers can change after another close, so retain the observation date when reviewing an example.
The XRP chart lets you check the text directly against XRP candles. It uses the scanner’s existing panel rather than a separate SEO model. Buttons change only the observation scale. A long wick and a close outside a boundary describe different price behaviour, while the event code depends on the full sequence. Parent cancellation remains relevant to dependent labels. Schematics explain the notation without inserting their fictional levels into the market chart.
XRP statistics have a separate n for each code and scale. The three shares distinguish target completion, invalidation and completion without a result. Waiting observations are not yet included in the denominator; cancellation stays in history but is excluded as well. Below twenty XRP completions, insufficient data replaces percentages. Another market’s sample does not enlarge this one. Several dependent events must not be read as independent promises of a return.
XRP has real market volume from this feed, not the sum of arbitrary external venues. Related surfaces for XRP include the full scanner, schematics, method, chart and Magnitude. Each answers a different question. The atlas explains XRP events, the chart exposes prices, and impulse size does not automatically establish accumulation. Retain the time and final outcome of an example so that you can compare the same case later. The sequence of facts matters more than the resemblance of two unrelated chart fragments.
FAQ
Why does the XRP phase differ between scales?
Each XRP timeframe is marked independently using closed candles. Available scales are 1H, 4H, 1D. A missing structure is not copied from another scale.
What does XRP volume mean?
This is real market volume from XRP feed candles, not the combined activity of every external venue or network operation.
Why are XRP event percentages missing?
Each event type and timeframe requires at least 20 completed outcomes. Waiting and cancelled observations are excluded from n; a smaller sample is labelled insufficient data.