Discussing the article: "How to Replace a WebSocket EA with TradeMux REST in MetaTrader 5"

New comment

Check out the new article: How to Replace a WebSocket EA with TradeMux REST in MetaTrader 5.

The article continues the series on AI Hedge Fund and addresses three limitations of v4: analysts' reputation scores are now stored persistently in SQLite, the EA has been removed from the critical execution path, and signals from the council of fifteen are distributed to multiple brokers via the TradeMux REST API. The logic behind the council and risk management has remained the same: Python retrieves data via the MetaTrader 5 SDK and executes orders directly. The result is resilience to restarts and scalability across multiple terminals.

If you have read the previous article about AI Hedge Fund v4, you know where we left off. A 15-member council: 10 analysts, 4 risk managers, and a Chairman; eight currency pairs; a Sharpe ratio of 6.31 and a Profit Factor of 2.09 based on an eight-week backtest. The system ran on a single MetaTrader 5 terminal via a WebSocket Expert Advisor (EA).

After that article was published, most of the questions boiled down to one thing: Why go to the trouble of setting up a 15-member council when you can just use a ready-made trading signal service? The answer became clearer during those eight weeks of operation. It is not about the number of council members, but about the fact that a system with a reputation engine learns from its own mistakes as it trades. Victor's rise from a reputation score of 50 on Monday to 68 by Friday is more than just a number in memory — it represents accumulated information about whom to trust more and on which trading instrument. It was precisely this information that turned out to be a vulnerability in the v4 architecture.


Author: Yevgeniy Koshtenko

New comment