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

I’m posting this to warn anyone operating DCA bots on Binance by way of 3Commas API. I’ve been stress-testing the execution logic during high-volatility events (flash dumps) and located a critical architectural flaw that places our accounts at risk. The Problem: Restrict Orders vs. Binance Volatility 3Commas at present forces Limit 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 moves quicker than the order e-book can fill. The Failure: As a result of 3Commas doesn't permit Market Order execution for Security Orders, the Limit Order will get skipped/gapped. The Outcome: The bot fails to average down. You're left holding a heavy bag with no improved entry worth, whereas the market tanks -20%. Why this matters: I argued this with their Engineering Staff. They admitted internally that their logic is "Fallacious" and that superior customers want Market execution and "Last Entry" calculation (true Martingale logic), but they are delaying the repair. In case you are trusting your liquidation worth based mostly on the idea that safety orders will hit, it is advisable to be careful. The present logic just isn't crash-proof. I’ve documented the complete technical breakdown and their admission right here (proof): GitHub Technical Report & Dev Response Examine your bot settings. Should you can't select "Market" for safety orders, your technique has a single point of failure.

P.S. To make matters worse: Their Admin just 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 are actively making an attempt to suppress this execution danger somewhat than fixing it. That's the reason I am bringing this to the group.

Commerce protected.