Personal logic is in, shared speed is out
A personal EA that manages your own orders fits the written rule. A risk manager that attaches stops and partials fits it too. HFT, latency arbitrage, and group copy-trading do not. The copy ban matters if the EA is really a signal shared across unrelated accounts. The firm does not need to call it a copy service for the pattern to look like one.
The platforms are MT5, cTrader, and DXtrade. There is no MT4 on this list. A bridge built only for MT4 is pointed at the wrong desk. The 5% daily loss, $5,000 on $100,000, and the static 10% maximum still apply while the bot runs. Automation does not rent a wider floor.
Where 2,000 messages actually go
A stop, a breakeven move, and four partial closes are a handful of messages on one ticket. A trail that modifies the stop on every tick through gold or NAS100 can spend the 2,000 cap before lunch, with the 5% line still untouched. The breach is then a message breach, not a drawdown breach. Both end the account.
You can create a Venasri login and connect the BrightFunded platform you actually trade. Step the stop when structure pays you, not when the last tick printed. The cap is per day, and a $200,000 account does not receive a second 2,000.
Trade2Earn lots and the message log
Trade2Earn mints tokens on every closed lot, winning or losing, and those tokens can be redeemed for free challenges. That reward sits next to a 5% day anchored to the higher of balance or equity at 00:00 CE(S)T. Extra round trips to farm tokens spend both the message budget and the daily cash. A losing farm ticket counts fully against $5,000 on $100,000.
Keep the cash risk on Equity Guard, with the daily lock at 4.25%, $4,250 on $100,000. If the bot's only reason for the next order is a token, the order does not belong. Five minimum trading days are not an invitation to fill the message cap on each of them.
Stops in milliseconds, entries only if the rule allows
Manual Trade Guard can attach a stop, move it to breakeven, and scale out at TP1 through TP4 in milliseconds. That is a risk manager, which the rule permits. It is not a license for a latency bot. Funded accounts still restrict five minutes before and after red-folder events. Phase 1 and Phase 2 do not. A bot that traded CPI in the evaluation must go quiet in that window once funded.
Bot Control should pause funded entries in the five-minute news window and should count modifications so the day ends far under 2,000. The split, 80% scaling to 100% at the third milestone, is paid on a book that still has its message log and its 5% day intact.
