BB_RPB_TSL_RNG_2 Strategy: Pullback Sniper
Nickname: Pullback Sniper
Profession: Bollinger Bands Worker + Trailing Stop Expert
Timeframe: 5 minutes (1 hour auxiliary)
I. What Is This Strategy?β
Simply put, BB_RPB_TSL_RNG_2 is a strategy that:
- Specializes in picking up bargains when prices pull back
- Uses Bollinger Bands to judge "has it fallen enough?"
- Comes with a "protect profits after earning" trailing stop system
It's like waiting for a sale at the supermarket. When the price drops to a certain level and a bunch of indicators all say "good to buy," you jump in. Then as profits climb, you gradually raise your stop-loss line to lock in what you've earned π―
II. Core Configuration: Basically "Set Your Escape Route First"β
Take Profit Rules (ROI Table)β
Run at 10% profit (but trailing stop will trigger first)
Translation: This ROI is basically decorative; the real exit logic relies on trailing stops and sell signals.
Stop Loss Rulesβ
Hard Stop: -17.8% (initial protection)
After Profit:
Above 1.9% profit β Stop-loss line starts moving up
Above 6.5% profit β Stop-loss line follows the profit
Translation:
- When you first enter, maximum loss is 17.8%
- After earning 1.9%, the stop-loss line starts moving toward your cost basis
- After earning 6.5%, the stop-loss line climbs with your profits, truly achieving "let profits run"
III. 7 Buy Conditions: I've Categorized Them for Youβ
This strategy's buy conditions are a bit complex, so I've grouped them into 4 categories:
π Category 1: Bollinger Bands Oversold Combination (1 condition)β
Core Logic: Price breaks below Bollinger Bands lower band while momentum indicators are oversold
Plain English:
"Price has fallen to the floor, various oversold indicators are at their limits, time for a rebound right?"
Representative Condition: BB_checked
Detailed Conditions:
- RMI < 49 (relative momentum is low enough)
- CCI <= -116 (Commodity Channel Index severely oversold)
- Stochastic RSI fast line < 32 (hasn't turned up yet)
- Bollinger Bands width is wide enough (high volatility)
- Price breaks below 3 standard deviation lower band
π― Category 2: Trend Pullback Category (1 condition)β
Core Logic: Buy the pullback within an uptrend
Plain English:
"The trend is still upward, but price has temporarily pulled back near the Bollinger Bands lower bandβζεΊ opportunity is here!"
Representative Condition: local_uptrend
Classic Lines:
- EMA(26) > EMA(12), and the gap is large enough
- Price temporarily drops to Bollinger Bands lower band
- This is the classic "trend pullback buy" case
π Category 3: Elliott Wave Series (2 conditions)β
Core Logic: Pullback signals based on Elliott Wave theory
Plain English:
"Wave theory says the pullback is done, time to get on board!"
Representative Conditions: ewo, ewo2
Condition Comparison:
| Condition | EWO Threshold | Feature |
|---|---|---|
| ewo | EWO > -5.585 | Negative value, indicates oversold |
| ewo2 | EWO > 4.179 | Positive value, indicates upward momentum |
β‘ Category 4: NFI Fast/Extreme Series (3 conditions)β
Core Logic: Rebound opportunities during extreme oversold conditions
Plain English:
"It's fallen this much, someone should be bottom-fishing right?"
Representative Conditions: cofi, nfi_32, nfi_33
Condition Details:
- cofi: Stochastic golden cross confirmation, ADX shows there's a trend
- nfi_32: Deep pullback, CTI extremely low
- nfi_33: Extreme oversold, Williams %R < -98, RSI < 32
IV. Protection Mechanism: 3-Layer "Life-Saving Locks"β
Each buy condition comes with a set of protection parameters, like strapping on three layers of seatbelts:
| Protection Level | Trigger Condition | Stop Loss Position | Plain English |
|---|---|---|---|
| Hard Stop | Active upon entry | -17.8% | "Run when loss hits this, game over" |
| Level 1 | Profit > 1.9% | Start breaking even | "Starting to make money, protect cost first" |
| Level 2 | Profit > 6.5% | Follow the profit | "Made big money, follow it upward" |
This design is pretty smartβgive enough room when first entering, then tighten up as you profit π€£
V. Sell Logic: Simpler Than Buyingβ
5.1 Sell Signals (Two Groups with OR Relationship)β
First Group:
Price > SMA(9)
Price > Sell MA * 1.02
RSI > 50 (enters bullish zone)
Fast RSI > Slow RSI
Plain English:
"Price is above the MA, RSI shows bullish, fast line crossed above slow line, time to go"
Second Group:
SMA(9) is rising
Price < HMA(50) (more conservative)
Price > Sell MA * 1.051
Fast RSI > Slow RSI
Plain English:
"Although HMA suggests a possible pullback, price is already high enough, better to cash out early"
VI. This Strategy's "Personality Traits"β
β Strengths (Praise Session)β
- Multiple Signals Working Together: 7 buy conditions aren't just for show, each requires multi-indicator confirmation, reducing false signals
- Smart Trailing Stop: Tiered protection, lets profits run
- Reasonable Indicator Combination: Bollinger Bands + RSI + CCI + EWO, multi-dimensional verification
- Clear Code: Each condition has a buy_tag, easy debugging
- Hyperopt-Friendly: Tons of parameters to optimize, lots of room for adjustment
β οΈ Weaknesses (Complaint Session)β
- Too Many Parameters Can Be Confusing: Dozens of parameters, beginners read code like reading ancient scripture π€―
- BTC Protection Not Enabled: Written in code but commented out, need to enable yourself
- 5-Minute Level Fees Hurt: High-frequency trading, fees add up
- Overfitting Risk: So many parameters, great historical backtest doesn't guarantee future profits
VII. Applicable Scenarios: When to Use It?β
| Market Environment | Recommended Action | Reason |
|---|---|---|
| Oscillating Upward | π’ Recommended | Strategy design target, pullback buying works well |
| Sideways Oscillation | π‘ Use with Caution | May enter/exit frequently, fees eat into profits |
| One-Sided Decline | π΄ Not Recommended | Bottom-fishing halfway down the mountain, frequent stops |
| Extreme Volatility | π΄ Not Recommended | Too many false breakouts, signals may fail |
VIII. Summary: How Is This Strategy Really?β
One-Sentence Evaluationβ
"A carefully designed trend pullback sniper, chasing profits, but so many parameters it makes you question life"
Who Should Use It?β
- β Traders with some quantitative experience
- β People who understand principles of Bollinger Bands, RSI and other indicators
- β Players willing to spend time optimizing parameters
- β Traders who can monitor 5-minute charts
Who Should NOT Use It?β
- β Complete beginners
- β People who want to earn while lying down
- β Blind followers who don't understand indicator principles
- β Users on exchanges with high fees
My Suggestionsβ
- Run Simulation First: Use dry-run mode for at least a week
- Understand the Conditions: Figure out what triggers each buy condition
- Enable BTC Protection: Turn on the BTC protection logic commented out in code
- Adjust Stop Loss: -17.8% hard stop might be too wide or too narrow for you
IX. What Markets Can This Strategy Make Money In?β
9.1 Core Logic: Building a "Defense Net" with Complexityβ
BB_RPB_TSL_RNG_2 is a trend pullback strategy. Code volume 400+ lines, what does that mean? Equivalent to writing a long article with 7 buy conditions, each like a checkpoint.
Its profit philosophy: Wait for price to pull back to "cheap enough" before entering, then use trailing stops to protect profits.
- Bollinger Bands: Judge whether price has fallen enough
- Multi-Indicator Confirmation: RSI, CCI, EWO all say "yes" at the same time
- Trailing Stop: Automatically raises stop-loss line after making money
9.2 Performance in Different Markets (Plain English Version)β
| Market Type | Performance Rating | Plain English Explanation |
|---|---|---|
| π Oscillating Rise | βββββ | This is the strategy's heaven, pullback buying works great |
| π Sideways Oscillation | βββββ | Okay, but fees will eat some profits |
| π One-Sided Decline | βββββ | Bottom-fishing halfway down, stops constantly trigger |
| β‘οΈ Extreme Volatility | βββββ | Too many false breakouts, strategy gets confused |
One-Sentence Summary: This strategy loves "trending but with pullbacks" markets, hates "continuous plunge" and "jumping up and down."
X. Want to Run This Strategy? Check These Configurations Firstβ
10.1 Trading Pair Configurationβ
| Configuration Item | Recommended Value | Commentary |
|---|---|---|
| Timeframe | 5 minutes | Design framework, don't change randomly |
| Trading Pairs | Major coins (BTC/ETH etc.) | Good liquidity, low slippage |
| Max Trading Pairs | 5-10 | Too many and CPU can't keep up |
10.2 Key Configuration File Settingsβ
# config.json Key Settings
"max_open_trades": 3, # Max 3 trades simultaneously
"stake_currency": "USDT",
"stake_amount": "unlimited", # Or fixed amount
"dry_run": true, # Run simulation first!
10.3 Hardware Requirements (Important!)β
This strategy has medium computational load, memory requirements:
| Trading Pairs | Minimum Memory | Recommended Memory | Experience |
|---|---|---|---|
| 1-5 pairs | 4GB | 8GB | Smooth |
| 5-20 pairs | 8GB | 16GB | Okay |
| 20+ pairs | 16GB | 32GB | Don't bother |
Warning: If you're using a Raspberry Pi or old computer, it might not run π
10.4 Backtest vs Live Tradingβ
Great backtest performance doesn't guarantee live trading profits!
Sources of Difference:
- Slippage: Backtest assumes execution at ideal prices
- Latency: Exchange API latency may miss best entry points
- Liquidity: May not be able to buy or sell during extreme conditions
Recommended Process:
- Backtest first, see parameter effects
- Run dry-run mode simulation for at least a week
- Small capital live test
- Add capital after confirming stability
Don't go all-in immediately, even good strategies need磨ε!
XI. Easter Eggs: The Strategy Author's "Little Thoughts"β
Look carefully at the code and you'll find some interesting things:
-
BTC Protection is Commented Out: BTC crash protection logic is written but turned off by default
"Worried BTC crash will drag down altcoins? Just remove the comments"
-
Buy Tags Are Thoughtful: Each buy condition has a buy_tag for easy analysis
"Which condition got you in? Check and you'll know"
-
Hyperopt Parameters Have Switches: is_optimize_xxx controls which parameters participate in optimization
"Don't want to optimize certain parameters? Set to False"
XII. Last But Not Leastβ
One-Sentence Evaluationβ
"A parameter-rich, thoughtfully designed trend pullback strategy, suitable for traders willing to dig deep"
Who Should Use It?β
- β Players with 1+ years of quantitative experience
- β People who understand technical indicator principles
- β Data enthusiasts who love researching parameter optimization
- β Traders who can handle 5-minute level monitoring
Who Should NOT Use It?β
- β Quantitative newbies
- β People who want passive income
- β Users on exchanges with high fees
- β People who only want results without studying principles
Manual Trader Recommendationsβ
Don't even think about manually executing this strategy. 7 buy conditions, a dozen indicators, impossible to judge manually in real-time. Trailing stop is even more impossible to execute manually.
XIII. β οΈ Risk Reminder Again (Must Read This Section)β
Backtest Is Beautiful, Live Trading Requires Cautionβ
BB_RPB_TSL_RNG_2 historical backtest performance is often pretty goodβbut there's a trap:
Because there are so many parameters, the strategy can easily "fit" the optimal solution of pastθ‘ζ , but this doesn't mean it will definitely profit in the future.
Simply put: Historical optimal parameters β Future optimal parameters
Hidden Risks of Complex Strategiesβ
In live trading, complex logic can lead to:
- Signal Delay: Multiple indicators need confirmation, may miss best entry point
- Overtrading: All 7 conditions can trigger, fees add up
- False Breakouts: Bollinger Bands lower band breakout could also be a real decline
My Suggestions (Honest Truth)β
1. Run dry-run for at least two weeks first
2. Enable BTC protection mechanism (remove the comments)
3. Adjust hard stop loss parameters to what you can accept
4. Control simultaneous position count (recommend β€3)
5. Choose major coins with good liquidity
Remember: No matter how good the strategy, the market won't greet you before teaching you a lesson. Light position testing, staying alive is most important! π