Dinex Blocks is a MetaTrader 5 EA library of reusable MQL5 building blocks for entries, exits, filters, risk limits and position sizing, each with a test status in a registry.
The problem
An EA combines many small rules. Rewriting them for each EA means retesting every copy.
Journey
- 27 Oct 2026: library v0.3 brought into git (Core, 39 blocks, 9 rebuilt EAs); Core v0.4 adds safety blocks.
- 30 Oct 2026: Core v0.6.2 checks margin before every new order.
- 7 Nov 2026: 20 signal and filter blocks pass all five technical evidence checks.
- 9 Nov 2026: whole-library regression runner and block catalogue.
My role
Nguyễn Hải Minh designed the block library and its registry together with AI, building with Claude and Codex and coordinating several AI agents.
Time spent
About 29 hours, estimated from commit history, not a timesheet, across 13 working sessions. Work before git (27 Oct 2026) and tester runs without commits are not counted, so the real figure is higher.
Tools and stack
- MQL5
- Python for checks and regression tests
- JSON registry
- MetaTrader 5 Strategy Tester
Checked
- Registry export of 9 Nov 2026: 108 blocks, of which 80
verified, 25unit_testedand 3rejected. - A sample of 20
verifiedblocks: every row shows PASS in the registry. - Daily-range entry filter: 4 Strategy Tester parameter sets with zero wrong allows or refusals, and 35 unit checks without a failure.
Not checked
- Profitability. The test status checks behaviour only.
- Detailed test evidence on this page covers one block only.
What can be observed
Screenshots of the registry and of the test evidence for one block, dated 10 Nov 2026.
FAQ
What is Dinex Blocks?
Dinex Blocks is a library of reusable MQL5 building blocks for MetaTrader 5 EAs, with a test status per block.
What does "verified" mean in Dinex Blocks?
It marks a passed technical check of the block's behaviour, not evidence of profit.
What is Dinex Blocks built with?
MQL5, Python for checks, a JSON registry and the MT5 Strategy Tester.
How long has Dinex Blocks taken?
About 29 hours across 13 sessions from 27 Oct to 9 Nov 2026, estimated from commit history, not a timesheet.