EA FX HUB Documentation

EA FX HUB is structured as a holding ecosystem with six interconnected products. Each product is independently deployable but shares a common signal and identity layer.

At the core of every product is the SignalOS routing engine. Signals from any source — technical indicators, AI models, external webhooks — pass through a consensus gate before execution or distribution to copy trading subscribers.

Get EA FX HUB V5.0 running on your MT4 or MT5 terminal in under 10 minutes.

SignalOS is the signal orchestration and copy trading platform at the centre of the EA FX HUB ecosystem. It combines four independent signal channels with a consensus routing engine, per-account preset overrides, and an embedded copy trading layer — all executing in a single EA with no external dependencies beyond the MQL5 Calendar API for news filtering.

The ENUM_SIGNAL_MODE enum controls how channel votes are combined before a trade is executed.

The copy trading layer is built directly into SignalOS — not bolted on. Every signal that passes the consensus gate and drawdown guard is simultaneously written to the master signal file and distributed to all connected slave terminals.

The architecture uses Windows directory junctions for inter-terminal file sharing on the same VPS, enabling sub-100ms signal propagation without any third-party bridge software.

Every per-account override flows through the PresetParams struct (P. prefix at runtime). This enables a single EA file to power accounts with completely different risk profiles, lot sizes, and drawdown rules simultaneously.

The news filter module reads directly from the MQL5 Economic Calendar API — no third-party data feed required. It evaluates upcoming events against the symbols being traded and blocks order entry during the configurable pre/post event window.

PropEdge is the prop trader operating system — a browser-based dashboard for managing multiple funded accounts simultaneously. It aggregates real-time equity, drawdown state, open positions, and news risk across all connected accounts in a single view.

Connect any MT4 or MT5 account via the PropEdge bridge. Each account displays live equity, floating P/L, daily DD consumed, static DD remaining, and active channel status.

PropEdge maintains a persistent drawdown ledger for each account. The rule engine evaluates the following hierarchy in real time:

TradeScribe AI is a coding co-pilot purpose-built for MQL5 and MQL4 developers. It translates plain-language strategy descriptions into production-grade EA code, explains backtest results, and performs logic audits to catch edge-case bugs before they cost a funded account.

AlgoVault is managed cloud infrastructure for retail algo traders. It provisions MT4/MT5-optimised VPS instances, handles terminal orchestration, configures directory junctions for copy trading, and enforces a security hardening baseline — removing the need for traders to manage server infrastructure themselves.

FlowDesk is a no-code workflow automation builder for trading teams and fintech companies. It is designed to replace manual processes around compliance reporting, client onboarding, lead follow-up, and content distribution — without requiring any engineering resource.

Phase 1 launches as a service delivering pre-built automation systems for trading brands, coaches, and fintech startups. Phase 2 converts those systems into a self-serve SaaS product.

TraderMark Studio is an AI brand and media studio built exclusively for fintech and trading companies. Unlike general brand agencies, TraderMark can validate the trading logic behind a brand's claims — which means copy, visuals, and campaign strategies that are credible to a sophisticated trading audience.

EA FX HUB ships with 21+ validated .set files covering three prop firm account tiers, five currency pairs, and three risk levels. Load any preset via the EA Inputs → Load button — no manual parameter entry required.

When UseLotDistribution = true, each channel is allocated a weighted percentage of the total calculated lot size. This prevents any single channel from over-trading and ensures capital is distributed proportionally to each strategy's historical edge.

EA FX HUB operates active Introducing Broker and Cost-Per-Acquisition relationships with the following brokers. Each relationship provides dedicated support, custom IB links, and in some cases co-branded materials for partner-facing deployment.

The SignalOS REST API enables external systems to push signals into the routing engine, query account state, and manage copy trading subscribers programmatically. Authentication uses API key passed in the request header.

New in V5.0: Per-session Channel D fire flags (g_chD_tokyoFired, g_chD_overlapFired) replacing the single daily flag — enables independent trading of both the Tokyo-to-London and London-to-New York sessions. Comprehensive [SIG:<Channel>]-tagged signal tracing throughout all four channels. LogSig refactored from #define macro to a proper void function to fix compiler context issues. Midnight-crossing session date bug in ChD_CalculateAsianRange() resolved.

Merged standalone Asian Range Breakout EA as Channel D into the 4-channel architecture. Introduced distributed lot sizing system (Ch-A 44%, Ch-D 28%, Ch-C 17%, Ch-B 11%) activated via UseLotDistribution=true with SIG_ANY_CHANNEL mode.

Merged RSI×RSI-MA crossover strategy as Channel C. Signal independence enforced via dedicated indicator handles. GTS dark dashboard theme migrated — deep navy, teal title bar, coloured section headers using #define colour constants.

CopyMaster/CopySlave infrastructure built using Windows directory junctions for inter-terminal file sharing with atomic writes. PU Prime news filter module v2 — MQL5 Calendar auto-read with symbol-aware kill logic and dynamic leverage event window handling. PresetParams struct architecture established as the foundation for multi-instrument, multi-broker deployment.

V5.0 is designed for prop firm use. It uses single-position-per-channel logic, fixed SL/TP, no martingale, no grid. It is compatible with FTMO, Monaxa, PU Prime, and most challenge-based firms. Always verify your specific firm's EA policy — some firms restrict any automated trading. Check the broker compatibility table for specific notes.

Yes. Each account runs in its own MT4/MT5 terminal instance. Use separate .set files with per-account MaxDailyDD_Pct and MaxStaticDD_Pct values. The copy trading layer can link all accounts to a single master signal source while each account enforces its own risk rules independently.

Check three things: (1) AsianRangeMinPips — if the Asian session range was smaller than this threshold, Ch-D skips the session. (2) The session fire flags — if g_chD_tokyoFired is already true, Ch-D won't fire again until the flag resets at the next session boundary. (3) Midnight-crossing dates — if your server UTC offset causes the session date to roll mid-Asian-range, the range calculation resets. Set ServerUTC to your broker's exact UTC offset.

Primary support is via the Telegram channel. For technical issues, include your EA version, broker, account tier, and a screenshot of the dashboard showing the active channel states. Enterprise and prop firm support is available via contact@eafxhub.com.

EA FX HUB is applying for $100,000 in AWS Activate credits to fund the cloud infrastructure for SignalOS and AlgoVault — specifically the MT4/MT5 container fleet, SageMaker market regime ML model, and real-time Kinesis signal streaming. This infrastructure is what transitions EA FX HUB from a VPS-based EA into a fully hosted SaaS platform. See the AWS section on the landing page for the full breakdown.