About · ProEA Lab
Trading tools you can question.
We build MT5 and TradingView software and publish practical guides and research about testing it. The useful question is what the evidence shows, and what it leaves unknown.
ProEA Lab is the organization byline used for this publication. ProEA creates and sells products linked from these articles, including MTR, Pine tools and TradeLens. That is a commercial interest to consider when reading our product comparisons and research. A ProEA Lab byline does not imply an independent review, a named individual's credentials or third-party verification of trading results.
What we build
Product pages describe the included files, supported workflows and purchase terms. Access and use rights depend on the product and license; a source-code purchase does not promise a profitable trading system.
MetaTrader 5 · Expert Advisor
MTR FullSystemEA
MT5 Expert Advisor source: 16,923 lines across 21 files. Its approximately 29-month reference result is an MT5 generated-tick backtest. The product page separates that test from latency experiments and independent monthly tests, and discloses the substantial drawdown and modelling limits.
Inspect MTR →TradingView · Pine v6 · Built for AI
Advanced Smart-Money Engine
Pine v6 tools for examining order blocks, fair value gaps and market structure. Read the product documentation and research for the scoring rules and limitations. A zone's historical resolution is a descriptive statistic, not a forecast or an account return.
Inspect the SMC toolkit →The wider catalog includes Pine v6 tools, a multi-timeframe confluence matrix, prop-firm calculators and journaling software. Start with the documentation for the task you need to complete.
What the evidence can establish
MTR's published reference uses MT5 generated ticks. The separate Rust simulator is not the source of that approximately 29-month result. The independent monthly tests are not a real-tick walk-forward test, and the reported balance drawdown does not measure the worst floating-equity loss. Read the linked methodology before comparing any results. A published summary or source manifest is also different from access to raw test data; each study must state which inputs and calculations are available to the reader.
Editorial standards and corrections
ProEA is responsible for the material published under this organization byline. Our standard for technical work is to identify the source, explain the method, separate measurements from assumptions, and state what has not been independently verified. Product comparisons should disclose our commercial interest and distinguish published documentation from hands-on testing. AI assistance does not replace those checks.
Publication dates identify the original article. Material corrections should retain that date and show an update with an explanation of what changed. The September 2026 MTR evidence review corrected test-method labels and removed unsupported performance framing; it did not certify the system for live trading.
To report a factual error, email support@pulltrade.app with the article URL, the statement in question and the source or calculation that contradicts it. Avoid sending account credentials or private trading records. You can also inspect the research index and product changelog for published material.
Claims our editorial standard excludes
- ✕Promise you a return, a win rate, or a monthly percentage.
- ✕Quote an accuracy number we can't prove on your own chart.
- ✕Call anything a "holy grail" or a "set-and-forget money machine."
- ✕Hide costs, drawdowns, or the experiments that lost.
- ✕Describe source access as broader rights than the product license grants.
If our tools can't survive your suspicion, you shouldn't buy them — and we'd rather tell you that than sell you a screenshot.
What we believe
We're on your side of the screen.
We build for traders, not at them — the tools we ship are the ones we'd want to trade ourselves.
Inspect the implementation.
Check the file manifest, documentation and applicable license before buying. Source access is not a transfer of copyright or unrestricted redistribution rights.
A backtest is a hypothesis, not a promise.
It can disqualify bad ideas. It cannot predict your future.
Describe the mechanism.
Explain what a score measures, the information available when it is computed, and the conditions under which it can fail.
Include adverse results.
Costs, losing cases and drawdown definitions belong beside modelled returns. A favourable test is not a live track record.
We do the research in public
This blog is where we write down what we learn building and testing real systems — free, and technical. The point is simple: make traders harder to fool, including by us. The more you understand backtests, execution costs, and real risk, the sharper every decision you make becomes, whatever you end up trading.
Verify us — don't trust us
Start with the available evidence: the source manifest, the ~29-month modelled backtest, the public changelog, and the product itself at proea.app. For TradingView studies, check the scoring definition, historical inputs and Bar Replay behaviour. A chart statistic does not establish future trading performance.
Trading carries a risk of loss. Our tools are educational decision-support, not financial advice or a signal service. Past performance is not future results; a backtest is broker-specific and a zone-resolution percentage is a descriptive statistic, not a guarantee.