Skip to main content

Stavix2: Japanese "Zhuge Liang's Scheme" — There Are Clouds Inside!

Nickname: Japanese Zhuge Liang's Apprentice, Cloud Hunter
Profession: Read clouds to predict weather (not that kind of cloud reading!)
Timeframe: 1 minute (Short-term player, but cloud chart is long-term thinking)


1. What's This Thing?

Simply put, Stavix2 is:

  • A technical strategy that decides buying/selling by cloud chart
  • A simple logic of buy when price breaks cloud, sell when breaks below
  • An impatient player doing trend following on 1-minute K-line
  • A two-way player with both entry and exit

This strategy uses famous Japanese "Ichimoku Kinko Hyo" (Ichimoku Cloud). This name sounds impressive — "Ichimoku" means "one glance", "Kinko" means "balance", "Hyo" means chart. Meaning is "super chart that lets you know market trend at one glance"!

"My strategy is like Zhuge Liang — without leaving home, just looking at clouds in sky, know what to do next!"


2. Core Config: Basically "Charge When Breaking Through Cloud Layer"

Profit-Taking Rules (ROI Table)

Hold → Run at 15% profit 🤑

Translation: 15% take-profit target! On 1-minute K-line, this is very aggressive target. Means you need to wait for a relatively big trend to trigger take-profit.

Stoploss Rules

Loss 10% → Admit defeat and leave 🏳️
Profit retracement 1% → Lock profits immediately 🪤 (but must first make 3%)

Translation:

  • 10% fixed stoploss, hurts when cut
  • Trailing stop: Must first make 3%, then profit retraces to only 2% (3%-1%) triggers

3. 1 Entry Condition: Japanese "Cloud Three-Insurance"

This strategy has 1 entry condition, but this condition has triple confirmation:

🎯 Core Logic: Three-Insurance Entry

Code Logic:

# Condition 1: Close price > Cloud upper edge (Senkou Span A)
# Condition 2: Close price > Cloud lower edge (Senkou Span B)
# Condition 3: Base line (golden cross) crosses above conversion line
→ BUY!

Plain English:

"Report boss! Price broke through cloud layer, and short-term MA shot up from below and crossed long-term MA — this is about to rise! BUY!"

This is equivalent to:

  1. 🌤️ Price breaks through cloud: Burst out from inside cloud, visible now
  2. 🌥️ Price above cloud: Not just head poking out, entire thing above cloud
  3. 📈 MA golden cross: Short-term trend starting to accelerate

Three insurances, none can be missing!

What's the Cloud?

Japanese "Ichimoku Kinko Hyo" consists of 5 lines, looks like a cloud, so called "cloud chart":

LineNameFunction
Conversion LineTenkan-senShort-term "weather trend"
Base LineKijun-senMedium-term "seasonal change"
Cloud ASenkou Span AUpper layer of cloud
Cloud BSenkou Span BLower layer of cloud
Lagging SpanChikou SpanLagging "confirmation"

Stavix2's Parameters:

  • Conversion line period: 200
  • Base line period: 350
  • Lagging: 75

These parameters... too long! 200+350, normal people can't remember!


4. Exit Logic: Symmetrical "Three-Insurance"

Exit Conditions

Code Logic:

# Condition 1: Close price < Cloud upper edge
# Condition 2: Close price < Cloud lower edge
# Condition 3: Conversion line (death cross) crosses below base line
→ SELL!

Plain English:

"Price dropped into cloud, and short-term MA also fell from above — this is about to drop! SELL!"

Symmetry: Entry and exit logic completely symmetrical, just opposite direction. This strategy really fair — longs and shorts both can play!


5. Protection: 0 Layers "Running Naked"

This strategy has no explicit protection mechanisms, because triple conditions themselves are protection:

  • Price must be above cloud (strong)
  • MA must golden cross (momentum confirmation)

But no:

  • ❌ RSI filtering
  • ❌ Volume validation
  • ❌ BTC protection
  • ❌ Time filtering

6. This Strategy's "Personality Traits"

✅ Pros (Praise Section)

  1. Classic Theory: Japanese "Ichimoku Cloud", decades of historical verification
  2. Multi-Dimensional Confirmation: Triple conditions, reduces false signal probability
  3. Long-Short Symmetry: Entry/exit logic symmetrical, strategy complete
  4. Simple Code: Around 100 lines, beginners can understand
  5. Adjustable Parameters: Cloud parameters can optimize for different coins

⚠️ Cons (Roast Section)

  1. 1-Minute Too Short: Too many false signals, overtrading
  2. Late Entry: Must wait for price to break through cloud
  3. Complex Computation: Ichimoku computation heavy
  4. Parameters Too Long: 200+350 parameters, normal users don't understand
  5. No Protection Mechanisms: No additional filtering conditions

7. Applicable Scenarios: When to Use It?

Market EnvironmentRecommended ActionReason
Strong uptrend✅ UsablePrice breaks cloud + MA golden cross = effective
Strong downtrend✅ UsableSymmetrical exit logic
Ranging market❌ Don't useFrequent cloud crossing
Sideways consolidation❌ Don't useCloud intertwined

8. Summary: How's This Strategy Really?

One-Sentence Review

"Automated implementation of Japanese classic technical analysis — cloud three-insurance, simple but effective. 1-minute K-line is a flaw, suggest changing to longer timeframe."

Who Should Use It?

  • Technical analysis enthusiasts: People who like studying various indicators
  • Trend traders: Want to catch big trends
  • Program developers: Want to learn strategy structure
  • Do both long and short: Strategy supports two-way trading

Who Should NOT Use It?

  • Impatient people: 15% take-profit hard to trigger
  • Pursue stability: 1-minute too many false signals
  • Loss-averse: 10% stoploss still hurts

My Suggestions

  1. Change timeframe: 5-minute or 15-minute more stable than 1-minute
  2. Adjust take-profit: 15% too high, 5-10% more reasonable
  3. Add filtering: At least check volume
  4. Manual timing: Check big trend direction before trading

9. What Markets Can This Strategy Make Money In?

9.1 Core Logic: Buy When Breaking Through Cloud

Stavix2's core philosophy:

  • Cloud = Support/Resistance Band: Cloud chart represents an area, not single line
  • Price breaks through cloud = Trend change
  • MA golden cross = Momentum confirmation

Profit logic:

"I don't care what situation now, anyway price broke through cloud, and MA also confirmed — this is trend! I'm in!"

9.2 Performance in Different Markets (Plain English Version)

Market TypePerformance RatingPlain English Explanation
📈 Uptrend⭐⭐⭐⭐⭐Price continuously above cloud, MA golden cross effective
📉 Downtrend⭐⭐⭐⭐⭐Exit logic equally effective
🔄 Ranging market⭐⭐Price up and down, crosses cloud many times
⚡ High volatility⭐⭐⭐Large volatility has chance to reach 15% take-profit

One-Sentence Summary:

"This strategy is a 'cloud breakout' player — enters when price breaks through cloud, exits when breaks below. Simple and brutal, but indeed effective."


10. Want to Run This Strategy? Check These Configs First

10.1 Pair Configuration

Configuration ItemSuggested ValueRoast
Number of pairs5-10Too many can't handle
Only mainstream coinsMustAltcoin cloud chart inaccurate
Exclude BTCSuggestedBTC volatility too weird

10.2 Key Config File Settings

{
"timeframe": "1m",
"stoploss": -0.10,
"minimal_roi": {
"0": 0.15
},
"trailing_stop": true,
"trailing_stop_positive": 0.01,
"trailing_stop_positive_offset": 0.03
}

10.3 Hardware Requirements

Number of PairsMinimum MemoryRecommended Memory
1-101GB2GB
10-302GB4GB

10.4 Backtest vs Live Trading

Suggestions:

  1. Change timeframe: 5-minute or 15-minute better
  2. Lower take-profit: Change 15% to 5-10%
  3. Paper trading test: Run at least 2 weeks

11. Easter Egg: The Strategy Author's "Little Thoughts"

After reading code, I think author might be:

  1. A Japanese culture enthusiast

    "I first studied Japanese tea ceremony, then by the way studied Japanese technical analysis..."

  2. Thinks simple strategy not enough

    "1 condition too few, let me add to 3!"

  3. A parameter junkie

    "200-period conversion line, 350-period base line, this is professional!"

  4. Pursues symmetry beauty

    "Entry conditions have 3, exit conditions must also have 3!"


12. Final Final Thoughts

One-Sentence Review

"Automated attempt of Japanese classic technical analysis — cloud three-insurance, simple and effective. 1-minute K-line really too small, suggest changing to 5-minute or 15-minute."

Who Should Use It?

  • ✅ People who like technical analysis
  • ✅ Want to catch trends
  • ✅ Can accept long-period holding
  • ✅ Want to do both long and short

Who Should NOT Use It?

  • ❌ Impatient (15% take-profit too slow)
  • ❌ Newbie beginners
  • ❌ Low-spec device users
  • ❌ Pursue frequent trading

Manual Trader Suggestions

If you want to manually reference this strategy:

  • First learn cloud chart: Understand basic principles of Ichimoku Cloud
  • Look at big trend: Only go long when daily level trend upward
  • Wait for breakout: Enter only when price completely breaks through cloud
  • Set stoploss: 8-10% more reasonable

13. ⚠️ Risk Reminder (Must Read This Section)

Backtest Looks Great, Live Trading Needs Caution

Stavix2's backtest data looks "okay", but note:

  • 1-minute K-line too many false signals
  • 15% take-profit hard to trigger historically
  • Cloud calculation needs large amount of historical data

Simply put:

"Backtest looks beautiful, but in live trading, 1-minute false signals can annoy you to death."

Hidden Risks of Simple Strategies

In live trading, you'll discover:

  • Too many false signals: Price frequently crosses cloud
  • Entry too late: After breakout confirmation, price already rose a lot
  • Stoploss too far: 10% stoploss too big on 1-minute
  • Take-profit too hard: 15% basically can't trigger

My Suggestions (Real Talk)

1. Change timeframe: 5-minute or 15-minute better choice
2. Lower take-profit expectation: Change 15% to 5-10%
3. Add extra filtering: Volume validation, trend filtering etc.
4. Manual timing: Don't fully rely on auto signals
5. Prepare mentally: May have consecutive losses

Remember:

"Cloud chart is good theory, but 1-minute K-line not good carrier. Change to longer timeframe, effect will be much better."


Final Reminder: No matter how good the strategy, the market won't say hello when teaching you lessons. Light position test, staying alive is most important! 🙏

Friendly Tip: Strongly suggest changing timeframe to 5-minute or 15-minute, 1-minute really too small, too much noise, signal quality very poor.

Wish everyone successful trading, get rich! 🚀💰