Elder SafeZone Stop: trail beyond directional market noise
The Elder SafeZone Stop estimates directional market noise from recent counter-trend penetrations, multiplies the average penetration by a factor, and places a trailing stop beyond that distance. The stop moves only in the direction that tightens the trade. Implementations differ, so the exact trend filter, lookback, reference price, and factor must be stated.
- Trend gate
- Common implementations use an EMA direction
- Noise input
- Average counter-trend high or low penetration
- Main limit
- A stop trigger does not guarantee the fill price
Key Takeaways
- Long and short calculations use different counter-trend penetrations.
- The lookback and factor control how far the candidate stop sits from price.
- The trailing rule prevents the stop from loosening while the trend condition remains active.
- Pineify does not currently list Elder SafeZone as a built-in core indicator.
Measure directional penetration
For a long-trend implementation, collect bars where the current low extends below the previous low and average those downside penetrations. For a short-trend implementation, collect bars where the current high extends above the previous high and average those upside penetrations. Bars without the relevant penetration do not add a positive distance.
Conceptual rule
longNoise = average(max(previousLow - currentLow, 0))
shortNoise = average(max(currentHigh - previousHigh, 0))
longCandidate = referencePrice - factor × longNoise
shortCandidate = referencePrice + factor × shortNoiseApply the one-way trailing rule
A long stop should not move down while the long trend state remains active. A short stop should not move up while the short trend state remains active. Reset behavior after a trend change or a new position must be explicit because different published implementations handle state differently.
- Long trail: use the tighter of the previous stop and current candidate
- Short trail: use the tighter of the previous stop and current candidate
- Define the first valid value when the lookback has insufficient data
- Define whether the stop uses close, low, high, or another reference price
Parameters do not remove execution risk
A larger factor normally places the candidate farther from price; a shorter lookback reacts to fewer observations. Neither setting determines an appropriate loss for an account. A stop-market order can fill beyond the trigger during gaps or fast markets, while a stop-limit order can remain unfilled.
Generate a custom implementation, not a built-in claim
Pineify can generate a custom Pine Script or MQL5 implementation from a stated variant. The request should include the trend filter, lookback, factor, penetration definition, reference price, reset behavior, plot style, and alert conditions. Generated code still needs platform review and testing.
Generate the exact SafeZone variant you intend to test
Specify EMA or another trend gate, lookback, factor, penetration rule, candidate reference, one-way trail, reset behavior, plots, and alerts. Pineify can produce editable Pine Script and run its syntax-check workflow. You remain responsible for strategy and order testing.
This page is educational and does not provide investment advice. A trailing-stop formula does not determine suitable risk, prevent losses, or guarantee execution at the trigger price. Review and test any generated code before use.