ClucFiatROI: The Cautious Trader with "Dual Bollinger Bands"
Nickname: The Two-Line Warrior
Profession: Quant world's "two-front warfare expert" — watches both 40-period BB and 20-period BB
Timeframe: 5 minutes (short-term player)
1. What's This Strategy?
Simply put, ClucFiatROI is:
- A strategy using 2 sets of Bollinger Bands (40-period + 20-period)
- A strategy that checks the order book (checks real-time prices)
- A strategy that cancels orders (runs if price is wrong)
Like a cautious buyer who asks all friends before purchasing: "What did the 40-period BB say? How about the 20-period BB? Does Fisher RSI agree? Only buy if all OK!" 🛡️
2. Core Settings: Simply "Double Confirmation + Quick Exit"
Profit-Taking Rules (ROI Table)
Make 4.35% right after buying? → RUN!
Hold 5 minutes and make 3.73%? → RUN!
Hold 8 minutes and make 2.57%? → RUN!
Hold 10 minutes and make 1.9%? → RUN!
Hold 76 minutes and make 1.28%? → RUN!
Hold 235 minutes and make 0.7%? → RUN!
Hold 415 minutes? → Run at breakeven! (Nearly 7 hours, really patient)
Translation: This strategy has 7-level take-profit, the longer you hold the lower the requirement — classic "time for space" 😅
Stoploss Rules
Hard stoploss: Cut at 34.299% loss (super loose!)
Trailing stop: Activates after 3.67% profit, run if pulls back 1.06%
Translation: -34.299% stoploss is really loose, gives price ample room to fluctuate — classic "avoid being shaken out" thinking 😅
3. Entry Conditions: Two Modes Available
This strategy has two entry modes, triggers if either is satisfied:
🎯 Mode 1: BinHV45 Variant
Core Logic:
- BB bandwidth > 0.642%
- Price change > 0.883%
- Lower shadow < 75.559% of bandwidth
- Price < previous BB lower band
- Price not higher than previous close
- Fisher RSI < -0.97101 (deeply oversold)
In Plain English:
"BB bandwidth is big enough, price broke below previous lower band, and Fisher RSI is deeply oversold — if this isn't a buy, what is?"
🎯 Mode 2: Cluc Variant
Core Logic:
- Price < EMA48
- Price < BB lower band × 0.98585 (1.415% lower)
- Volume < average volume × 18
- Fisher RSI < -0.97101
In Plain English:
"Price is below EMA48, broke 1.415% below BB lower band, volume is normal, Fisher RSI is oversold — if this isn't a buy, what is?"
Roast: This strategy is really "a rabbit has two burrows" — one of the two modes will always trigger! 🤣
4. Protection: Order Timeout + Trailing Stop
This strategy's protection is much more luxurious than previous strategies:
| Protection Type | Function | Plain English |
|---|---|---|
| Trailing Stop | Auto-follows price after profit | "Activates after 3.67%, runs if pulls back 1.06%" |
| Order Timeout | Cancels order if price is wrong | "Cancel if order price deviates over 1%" |
| Hard Stoploss | Cut at 34.299% loss | "Really wrong, admit defeat, 34% is the line" |
Roast: This strategy's protection is really luxurious, wrote three functions just for order timeout checks! 🤣
5. Exit Logic: Even More Complex Than Entry
5.1 Technical Exit: Must Meet 4 Conditions Simultaneously
Trigger:
(Price × 0.95153 > BB Middle Band) # Price near middle band
AND (EMA6 > Price) # Short-term trend weakening
AND (Fisher RSI > 0.60924) # Fisher RSI overbought
AND (Volume > 0)
In Plain English:
"Price is near BB middle band, EMA6 is above price (trend weakening), Fisher RSI is overbought — if you don't run now, what are you waiting for?"
Roast: Exit conditions require 4 conditions simultaneously — this strategy is really cautious! 🤣
5.2 ROI Exit: 7-Level Take-Profit
Profit Hold Time Trigger Exit
─────────────────────────────────────
4.35% Anytime Run when reached (big profit)
3.73% After 5 min Run when reached (medium profit)
2.57% After 8 min Run when reached (small profit)
1.9% After 10 min Run when reached (tiny profit)
1.28% After 76 min Run when reached (small red)
0.7% After 235 min Run when reached (mosquito leg)
0% After 415 min Run at breakeven (nearly 7 hours)
In Plain English:
- Make 4.35% right after buying? → Pie from heaven, run!
- Hold 5 minutes and make 3.73%? → Not bad, run!
- Hold nearly 7 hours and make 0%? → Run at breakeven, not playing anymore!
6. This Strategy's "Personality Traits"
✅ Advantages (Praise Session)
- Dual Bollinger Bands: 40-period + 20-period, covers different time dimensions
- Fisher RSI: Normalized RSI is more sensitive
- Order book check: Uses real-time order book to optimize execution
- Order timeout: Prevents orders from not filling due to price movement
- Hyperparameter optimization: Key parameters are optimized, not guessed
⚠️ Disadvantages (Roast Session)
- High complexity: Dual BB + multiple indicators, debugging is painful
- Order book dependency: Requires exchange to support orderbook API
- Parameter sensitivity: Optimized parameters may overfit
- Stoploss too loose: -34.299% stoploss, extreme markets may hurt
- High computation: Dual BB increases computational burden
7. Applicable Scenarios: When to Use It?
| Market Environment | Recommended Action | Reason |
|---|---|---|
| Ranging market | Highly recommended | Dual BB best for ranging |
| Uptrend | Recommended | Trailing stop locks profits |
| Downtrend | Pause or light position | No trend filter, easy to lose consecutively |
| High volatility | Adjust parameters | May need to adjust stoploss threshold |
| Low volatility | Adjust ROI | Lower ROI threshold for small moves |
| BTC crash | Pause | Big brother crashed, watch first |
8. Summary: How's This Strategy?
One-Sentence Review
"A cautious trader using two sets of Bollinger Bands, checks order book, cancels orders"
Who Should Use It?
- ✅ People who like multi-indicator combinations
- ✅ People who can accept some complexity
- ✅ People with quantitative foundation
- ✅ Friends with VPS RAM 2GB or more
Who Should NOT Use It?
- ❌ People who like simple strategies (this strategy has many conditions)
- ❌ People wanting to bottom-fish in downtrends (no trend filter)
- ❌ People whose exchange doesn't support order book
- ❌ Pure quantitative newbies (need to understand dual BB)
My Recommendations
- Simulate first: Run 2-4 weeks to see signal frequency
- Add filter: Can add EMA200 trend filter yourself
- Tune parameters: Order timeout threshold can be adjusted per market
- Watch BTC: Manually pause strategy when Bitcoin crashes
9. What Markets Make Money with This Strategy?
9.1 Core Logic: Faith in Double Confirmation
ClucFiatROI is a cautioustype, code is about 150 lines — what concept? About the length of a long Weibo post 📱
Its money-making philosophy:
"One BB might lie, but two BBs watching together won't both lie, right!"
- Dual BB faith: 40-period for long-term, 20-period for short-term
- Fisher RSI faith: Normalized RSI more sensitive than regular RSI
- Order book faith: Real-time price more accurate than candles
9.2 Performance in Different Markets (Plain English Version)
| Market Type | Performance Rating | Plain English Explanation |
|---|---|---|
| 📈 Slow bull/ranging up | ⭐⭐⭐⭐☆ | Dual BB + trailing stop, performs well |
| 🔄 Wide ranging | ⭐⭐⭐⭐☆ | Born for ranging markets, harvests both sides |
| 📉 Single-sided crash | ⭐⭐☆☆☆ | No trend filter, easy to lose consecutively |
| ⚡️ Extreme sideways | ⭐⭐⭐☆☆ | Too little volatility, signals reduce but risk also low |
One-sentence summary: Makes money in ranging markets, also good in uptrends, be careful in crash markets
10. Want to Run This Strategy? Check These Configs First
10.1 Pair Configuration
| Configuration | Recommended Value | Roast |
|---|---|---|
| Number of pairs | 20-40 | Moderate signal frequency |
| Quote currency | USDT | Don't use BTC/ETH as quote |
| Max positions | 3-6 orders | Control risk |
| Position mode | Fixed position | Recommended fixed, control risk |
| Timeframe | 5m | Mandatory, can't change |
10.2 Hardware Requirements (Moderate Level)
This strategy uses dual BB, moderate computation:
| Number of Pairs | Minimum RAM | Recommended RAM | Experience |
|---|---|---|---|
| 20-40 pairs | 1GB | 2GB | Can run |
| 40-80 pairs | 2GB | 4GB | Comfortable |
Warning: Don't try with 512MB RAM VPS, this strategy eats some resources 😅
10.3 Order Book Dependency
Strategy uses self.dp.orderbook() to get real-time order book:
- Requires exchange to support orderbook API
- Order book data may have latency in live trading
- Order book data may be inaccurate in backtesting
Roast: This strategy has "order book dependency" — can't play without orderbook API exchange! 🤣
10.4 Backtest vs Live Trading
Strategy logic is complex, differences between backtest and live mainly from:
- Order book data latency
- Order timeout check behavior differences
Recommended process:
- Backtest first to see historical performance
- Dry-Run for 2-4 weeks
- Observe if order timeout check works as expected
- Small capital live test for 1 month
Don't go all-in immediately, even the best strategy needsgetting-used-to-each-other period!
11. Easter Egg: Strategy Author's "Little Thoughts"
Look carefully at the code, you'll find some interesting things:
-
Strategy name is ClucFiatROI: Cluc + Fiat (fiat currency) + ROI
"Maybe Cluc series fiat optimization version, who knows!"
-
ROI has 7 levels: More than common strategies
"This is real·time for space, 7-level take-profit!"
-
Stoploss -34.299%: Much looser than common strategies
"This stoploss is really wide, probably to avoid being shaken out!"
12. Last But Not Least
One-Sentence Review
"Dual Bollinger Bands + order book optimization, few signals but high quality cautious player"
Who Should Use It?
- ✅ People who like multi-indicator combinations
- ✅ People who can accept some complexity
- ✅ People with quantitative foundation
- ✅ Friends with VPS RAM 2GB or more
Who Should NOT Use It?
- ❌ People who like simple strategies
- ❌ People wanting to bottom-fish in downtrends
- ❌ People whose exchange doesn't support order book
- ❌ Pure quantitative newbies
Manual Trader Recommendations
Manual traders can reference this strategy's dual BB approach:
- Observe both 40-period and 20-period Bollinger Bands
- Use Fisher RSI to confirm overbought/oversold
- Set order timeout cancellation mechanism
13. ⚠️ Risk Reminder Again (Must Read This Section)
Backtest Is Beautiful, Live Trading Needs Caution
ClucFiatROI's historical backtest performance may be very excellent — but there's a trap:
Multi-indicator + hyperparameter optimized strategies are easier to "fit" beautiful backtest curves, because there are many parameter combinations, may have just "memorized" how that historical period went.
Simply put: Backtest data looks good, maybe because it just "remembered" how that period went.
Hidden Risks of Complex Strategies
In live trading, complex logic may cause:
- Too few signals: Dual BB + multi-condition confirmation, may go long without signals
- Order book latency: Real-time order book data may have latency
- Overfitting risk: Hyperopt results may overfit
My Recommendations (Real Talk)
1. Test with minimum capital first (e.g., 100U)
2. Run live at least 2-4 weeks, observe signal frequency
3. Confirm order timeout check works normally
4. Consider adding trend filter yourself (e.g., EMA200)
Remember: The more complex the strategy, the more alert to overfitting risk. Staying alive is most important!
Final reminder: No matter how good the strategy, the market won't greet you when teaching you a lesson. Light position test, staying alive is most important! 🙏