The required_neutral_streak parameter determines how many consecutive neutral or reversal readings are needed before a held DCA order is released. Optimizing this setting is key to balancing safety and responsiveness in your Volatility Gate.

---

🔹 1️⃣ Purpose of required_neutral_streak

• Prevents premature DCA execution during brief pauses in ongoing crashes or pumps.
• Ensures that the market has truly stabilized or reversed before committing capital.
• Works together with explosive_threshold_pct and max_observation_minutes to control DCA timing and risk exposure.

---

🔹 2️⃣ How to Optimize

1. Consider Market Volatility:

   • High-Volatility Altcoins:

     • Price can fluctuate wildly within minutes.
     • Use 2–3 consecutive neutral/reversal readings to avoid releasing orders too soon.

   • Stable Assets (BTC/ETH):

     • Momentum changes are usually gradual.
     • 1–2 readings are sufficient to confirm stabilization.

2. Balance Safety vs. Timeliness:

   • Higher streak value (3–4):

     • Safer → ensures sustained trend exhaustion.
     • Slower DCA execution → may miss minor dips.

   • Lower streak value (1–2):

     • Faster DCA execution → more responsive to normal dips.
     • Slightly higher risk of catching short-lived spikes or noise.

3. Test in Demo Mode:

   • Observe logs:

     • 👁️ DCA Observer: still volatile → streaks reset if volatility persists
     • ✅ DCA Observer: RELEASING → confirms order release after required streak
   • Adjust streak until orders consistently release after true stabilization rather than temporary pauses.

---

🔹 3️⃣ Practical Example

Asset Type	Recommended Streak	Reason
BTC	1 – 2	Stable, trend reversal usually clear within 1–2 polls
Low-Cap Altcoins	2 – 3	Rapid swings; longer confirmation prevents premature DCA

Scenario:

• Low-cap coin drops 8% in 10 minutes.
• required_neutral_streak = 3 → DCA order is only released after 3 consecutive 60-second polls confirm momentum has cooled.
• Result: Order fires after market has truly stabilized, avoiding chasing the crash.

---

🔹 4️⃣ Key Considerations

• Works in conjunction with polling interval (60s) — each streak reading represents one poll cycle.
• Too high: DCA may be delayed unnecessarily, missing good entry opportunities.
• Too low: Orders may release during short-lived pauses in explosive moves, reducing safety.
• Use alongside explosive_threshold_pct and max_observation_minutes for full Volatility Gate optimization.

---

🔹 5️⃣ Summary

• required_neutral_streak ensures DCA orders are only executed after momentum truly stabilizes or reverses.

• Adjust based on asset volatility and risk tolerance:

  • Stable coins: 1–2
  • High-volatility altcoins: 2–3
• Always validate in demo mode to achieve the optimal balance between safety and timely execution.

Think of it as the “confirmation count” before your DCA order is allowed to execute — more confirmations = safer, fewer = faster entry.

---

I can also update the DCA observation lifecycle diagram to show how required_neutral_streak affects the timing of DCA execution, making it visually clear.

Do you want me to do that?

📎 Related Topics

• Should I test DCA strategies in demo mode first?
• What are recommended DCA settings for beginners?
• How can I tell if my DCA configuration is too aggressive?
• What are common DCA mistakes to avoid?
• What are recommended Volatility Gate settings for BTC?