cRyPtO sMaRtValue and trend together
The default value EMA is 21 and the trend EMA is 50; both lengths are configurable.
01 / 06Setup overview
Read the value and trend EMAs with the configured higher-timeframe context. Let price return toward value instead of chasing an extended move.
Rules illustration · Not a TradingView screenshot or performance record
- Signal
- A setup qualified under the configured rules.
- Entry
- The setup’s reference entry level.
- Stop
- The displayed invalidation reference.
- TP1 / TP2
- Partial and final target references; execution is not guaranteed.
TradingView indicator · Trend continuation
Oracle
Read the trend. Wait for the reclaim.
Bring patience to a trending chart. Oracle follows a pullback toward value, checks the reclaim and displays the setup’s entry, stop and target levels.
- Pine v6
- Readable source
- 14-page setup guide
Checking price…
Personal digital licence · Price confirmed before payment
Explore the setup, step by step ↓Have a question?
A considered choice
Made for your way of working.
For traders who prefer pullbacks within a trend and want to review value, confirmation and invalidation in one chart workflow.
A selective setup
Trend separation, setup quality, cost and risk-distance filters can reduce qualifying signals.
Visible risk context
Optional TP/SL zone boxes, live bands and a dashboard help explain a chart setup.
Your alert workflow
Use the script’s Buy, Sell or Any signal condition when creating an alert in TradingView.
The process
One clear step at a time.
Establish the trend
Read the value and trend EMAs with the configured higher-timeframe context.
Wait for the pullback
Let price return toward value instead of chasing an extended move.
Review the reclaim
Check confirmation and the displayed risk levels before deciding whether to act.
Understand the trade levels
From setup to the first target.
An educational sequence informed by the supplied script. Play it or choose a step.
Illustrative long setup
- Entry
- 100.00
- Original SL
- 96.00
- TP1
- 104.00
- TP2
- 108.00
After TP1: simulated stop → 100.00. Execution costs still apply.
Open full-size trade chart ↗Step 1 of 3
Read the setup
Review pullback and reclaim context. The curves use synthetic prices, not market data.
Motion starts only when you press Play.
Explore the rules
Read the setup before the signal.
The diagrams use synthetic candles to explain a workflow; they do not show actual trades or tested performance.
Guided explanation
Establish the trend
Read the value and trend EMAs with the configured higher-timeframe context.
Your chart, your settings
Know the controls before you buy.
- Value EMA
- 21 by default
- Trend EMA
- 50 by default
- Minimum reward:risk filter
- 2.0 by default
- Max stop distance
- 2.5 × ATR by default
- Max signals per day
- 3 by default
- Display controls
- EMAs, TP/SL zones, bands, stamps, dashboard
Defaults describe the supplied source, not a recommendation for a particular market.
What the dashboard shows
Field preview based on the supplied script. Values depend on the chart and settings; no example performance numbers are invented here.
- Trend
- Higher-timeframe directional context
- Status
- The current engine state
- Strength
- Trend separation measured against ATR
- Trade / Next target
- Shown when a simulated trade is open
- Trades
- The supplied dashboard’s trade-count label
- Win rate
- Simulated proportion of winning closed trades
- Result
- Accumulated simulated R result
- Advanced statistics
- Includes expectancy and average win/loss when enabled
Signal behaviour
Know what is confirmed.
Checked against the supplied Oracle Pine v6 source.
Signal confirmation
The engine evaluates the pullback/reclaim and trend filters only when the chart bar is confirmed.
While the candle is open
The current candle and calculations using its changing prices can move. Treat them as developing context rather than a newly confirmed entry.
Higher-timeframe context
Both supplied scripts request previous-bar higher-timeframe close/EMA values. The chart history, selected timeframe and feed still matter.
Historical versus live
Historical OHLC bars do not reveal the full sequence of prices within a candle. Dashboard results are simulated and are not evidence of broker fills.
Your purchase
Exactly what arrives.
ORACLE.pine
Readable Pine v6 source; the supplied release is v3.5.
ORACLE-Setup-Guide.pdf
14-page guide covering installation, inputs and signal interpretation.
Personal licence
Use the delivered source on your own TradingView account; no redistribution.
After checkout
From payment to your first session.
- Complete checkout
Use your purchase email; payment is verified on the server.
- Open your access links
Files unlock after captured payment is confirmed. Keep the confirmation page available.
- Get started
Download your source and guide, then follow the TradingView setup instructions.
Download link: 3 days, with free re-issue through Recover access.
Digital educational products. No physical delivery or guaranteed trading outcome. Purchase terms · Disclaimer
Choose the workflow
Falcon or Oracle?
| Focus | Falcon | Oracle |
|---|---|---|
| Core setup | Range breakout, retest or sweep | Trend pullback and reclaim |
| Main reference | Watched range high / low | Value and trend EMAs |
| Included | Pine v6 source + 12-page guide | Pine v6 source + 14-page guide |
| Execution | You decide and place trades; neither product is an exchange-connected bot. | |
Supplied release
Oracle v3.5
The supplied v3.5 changelog records corrected partial-profit accounting, a consecutive-loss pause that persists across the daily boundary, and a dashboard label changed from Signals to Trades. No verified release date was supplied.
Before you decide
Your questions, answered.
What do I need?
A TradingView account with access to Pine scripts. Available alert counts, notification channels and historical data depend on your TradingView plan.
Is this an automated trading bot?
No. It runs on the chart you open in TradingView. It does not connect to your exchange or execute orders.
When do signals appear?
The supplied source gates entry decisions on confirmed chart bars. Higher-timeframe calculations and data history can affect behaviour; the “non-repainting” claim has not been independently certified here.
Why can historical and live results differ?
Historical candles do not contain the full sequence of intrabar prices. Data revisions, settings, chart history and execution can change the result. Dashboard statistics are simulated, not a broker account record.
Why did changing settings not change my alert?
TradingView saves the script, inputs, symbol and timeframe when you create an alert. Delete and recreate the alert for relevant changes to take effect.
What happens after purchase?
Once the server confirms captured payment, your licensed files become available. The ZIP download link lasts 3 days and can be re-issued through Recover access.
What does the licence permit?
Personal use on your own account and devices. Resale or redistribution is not included; see the existing store terms for the purchase conditions.
A little guidance
Find your starting point.
Three quick choices. A clear reason for the recommendation.
Ready when you are