Architecture reference
How a Native MT5 Risk Panel Works Without DLLs
A verifiable explanation of local MT5 execution, standard MQL5 APIs, terminal state, and the boundary between core risk controls and optional connected services.
Direct answer
The EA PRO risk engine is compiled as an MT5 Expert Advisor and runs in the terminal process. It uses standard MQL5 trading, chart, event, and terminal-storage facilities. Core risk and trade-management functions do not load an external DLL and do not call a remote server to calculate or execute a trade.
Local control path
User input enters the panel, is validated locally, updates panel state, and is converted into order parameters through the terminal trading interface. Ticket-specific settings remain associated with the relevant order or position.
- Panel event handling
- Local risk and lot calculation
- Chart-based entry, stop, and target levels
- Terminal trade request
- Per-ticket state persistence
No external DLL boundary
The compiled product relies on standard MQL5 interfaces for its core behavior. This removes a separate native library installation step and avoids coupling core operation to a third-party binary bridge.
No mandatory server boundary
Position sizing, order controls, partial exits, and local protections are designed to operate in the terminal. Website availability is not a calculation or execution prerequisite for these core functions.
Reproducible verification
Install the official version 3.4 market build in a clean MT5 terminal, inspect the Expert Advisor dependency declaration, run with web access disabled, and test sizing plus a non-live order workflow in the Strategy Tester or a demo account. Full Telegram delivery is excluded because it is planned for version 4.
- Use a clean MT5 installation
- Confirm no DLL permission is requested for core use
- Disable network access
- Verify local sizing and panel controls
- Test only on a demo account
- Record product version and terminal build
Limit of this claim
This architecture statement does not claim that every planned service is offline. Version 4 Telegram relay, website accounts, licensing, and web dashboards require their respective network services.
Evidence standard
Claims on these pages describe the current product architecture. Performance or superiority claims are not made without reproducible measurements.