⚠️ Critical Flaw for 3Commas users trading via Binance API (Safety Orders Failure)

I’m posting this to warn anybody operating DCA bots on Binance by way of 3Commas API. I’ve been stress-testing the execution logic throughout high-volatility events (flash dumps) and located a critical architectural flaw that puts our accounts at risk. The Situation: Restrict Orders vs. Binance Volatility 3Commas presently forces Restrict Orders for all Security Steps and calculates them based mostly on fastened steps. The State of affairs: When Binance experiences a flash crash (wick down), the worth strikes quicker than the order e-book can fill. The Failure: Because 3Commas doesn't permit Market Order execution for Safety Orders, the Restrict Order gets skipped/gapped. The End result: The bot fails to average down. You're left holding a heavy bag with no improved entry worth, while the market tanks -20%. Why this issues: I argued this with their Engineering Workforce. They admitted internally that their logic is "Fallacious" and that superior customers need Market execution and "Last Entry" calculation (true Martingale logic), but they're delaying the fix. In case you are trusting your liquidation worth based mostly on the idea that safety orders will hit, you should watch out. The current logic shouldn't be crash-proof. I’ve documented the complete technical breakdown and their admission here (proof): GitHub Technical Report & Dev Response Examine your bot settings. In case you can't select "Market" for security orders, your technique has a single level of failure.

P.S. To make issues worse: Their Admin simply tried to bury this lively report by merging it right into a 2-year-old "Accomplished" thread on their Feedback Portal (which has nothing to do with this problem). They're actively making an attempt to suppress this execution danger moderately than fixing it. That is why I am bringing this to the group.

Trade protected.