|
6+ 年
经验
|
4
产品
|
2
演示版
|
|
0
工作
|
2
信号
|
0
订阅者
|
Trader and algorithmic developer focused on risk-managed automation for the Forex market. I build Expert Advisors that prioritize capital protection and survivability over hype — real strategies, transparent results, and live monitoring.
My flagship is SurfBot, a bidirectional mean-reversion grid with portfolio-level exposure control and an optional trend hedge. Everything I publish runs on real accounts with public signals, so you can verify performance before you buy.
I value clear documentation and responsive support. Questions are always welcome — reach out anytime.
My flagship is SurfBot, a bidirectional mean-reversion grid with portfolio-level exposure control and an optional trend hedge. Everything I publish runs on real accounts with public signals, so you can verify performance before you buy.
I value clear documentation and responsive support. Questions are always welcome — reach out anytime.
Joao Prata Silva Yglesias
已发布产品
Grid Survival Ruler answers one question that decides whether a grid survives: how far can price move against you before the last layer is filled, and how often has THIS pair actually moved that far? Enter your spacing (% of price) and your maximum layers. The indicator draws the ladder on the chart, marks the last layer in red (book full), and shows the total adverse move in % and in price, plus how many average daily ATRs it represents. Then it tests that distance against the pair's own D1
Joao Prata Silva Yglesias
已发布产品
Spacing Audit measures the grid spacing your EA REALLY uses, from its own closed trades, not from its inputs and not from the gaps between open layers. Why: I spent a week believing my grid used ATR-based spacing because UseATR was true. It did not. Every pair sat on the minimum-spacing floor, 2.8x to 5.1x tighter than intended, and the book kept clogging. The inputs said one thing; 1,120 closed trades said another. The method: in a grid where each layer carries a take-profit one spacing away
Joao Prata Silva Yglesias
已发布代码Contract Sizer: ladder, floor and a breaker that survives a deposit
三种起作用不同的仓位规模保护机制；正是因为混淆了它们，才导致如此多的账户被清零：
- 阶梯式：每X的余额对应一份合约，始终作为上限（CAP）应用，即使手动设定手数也是如此；
- 底限（floor）：余额低于最低资本要求时停止交易；需进行新的入金；
- 断路器（breaker）：无论账户规模大小，当余额跌破峰值X%时触发止损，且不会自动重置。
本库解决了一个几乎所有其他库都未解决的问题：入金不等于盈利，提现不等于亏损。 断路器是根据账户余额峰值来衡量跌幅的。如果不加以处理，在回撤期间进行的入金会同时推高余额和峰值，导致保护机制恰恰在最需要发挥作用的时候无法识别跌幅。在此情况下，入金和出金会以相同幅度改变峰值。
峰值会被保存到文件中：如果一个止损机制在终端重启后会忘记峰值，那它就称不上是止损机制。
该演示程序模拟了在回撤谷底进行入金的情况。请分别开启和关闭入金功能运行程序，并比较“跌幅”列的数据。
16
86
Joao Prata Silva Yglesias
已发布代码Safe Logger: why your log lines vanish while FileOpen keeps returning success
Four EAs writing to the same file, all with FILE_SHARE_READ|FILE_SHARE_WRITE, FileSeek(SEEK_END), FileWrite, FileClose. Looks correct. Every FileOpen returns success. No error in the log. And the lines vanish.
Reason: FILE_SHARE_WRITE lets all four open at the same time. All four call FileSeek(SEEK_END) and get THE SAME offset, because none has written yet. All four write at the same position. Whoever closes last wins. Three lines vanish silently. In my case: 12 events expected, 8 in the file.
The fix is to open EXCLUSIVELY (no FILE_SHARE_WRITE) and retry while another EA holds the file. And to shout in the log when the retries run out: a log that fails silently is worse than no log at all, because you trust it.
The demo script reproduces both modes. To see the loss, drag it onto four charts at the same time with safe mode off and count the lines in the CSV. On a single chart the defect does not show up - which is why it passes in testing and breaks in production.
80
Joao Prata Silva Yglesias
已发布代码Clock Diagnostic: TimeCurrent() freezes and steps backwards
TimeCurrent() is not a clock. It is the stamp of the LAST TICK. Two consequences break robots in production:
1. It freezes. With no tick it does not move: illiquid instrument, end of session, unstable connection - and any rule based on it stops with it.
2. It steps backwards: on a symbol switch, a reconnection or a tick from another instrument, the value can go back.
The case that cost me a whole protection: I compared the date of a daily decision with TimeCurrent() to reject an expired one. The server clock stepped back to the previous day, the comparison matched, and four EAs accepted YESTERDAY's decision as valid. The gate that should have failed closed failed open - without a single error in the log.
Rule: TimeLocal() for timestamps, dates, day changes, expiry - all that must always move forward; TimeCurrent() for session hours and market data.
The script measures the divergence in your environment and reports both symptoms live. Run it with the market closed.
103
Joao Prata Silva Yglesias
已发布代码Trade Excursion Report: MFE and MAE of every closed trade, to CSV
针对每笔已平仓交易导出一行CSV数据，其中包含对账单上未显示的数值：该交易曾达到的最高未实现盈利（MFE）、曾承受过的最大未实现亏损（MAE）、实际保留的MFE金额、交易跨过的K线数量以及持仓时长。 该指标的计算方式与“交易波动”指标相同，但将结果写入文件而非绘制在图表上，因为针对这些数据值得探讨的问题，是图表无法解答的：获利率是否取决于入场时间？ 我提前平仓的交易是否恰恰是持仓时间最长的？周一的亏损交易达到的MAE是否与周五不同？只要生成CSV文件，这些问题只需通过一个数据透视表即可解答。 输出格式为分号分隔且带标题行，位于 MQL5\Files 目录下；可在任何电子表格软件中打开。测量限制：波动值取自所选时间周期的K线高低点；单根K线内的价格路径无法确定。“K线”列报告了每笔交易的分辨率，汇总统计时将单根K线交易单独计数，而非将其平均计算在内。
124
141
Joao Prata Silva Yglesias
已发布代码Trade Excursion: how much of each winner you actually kept (MFE/MAE from your own history)
Your statement tells you what you KEPT. It does not tell you what you HAD. This indicator reads your own closed trades from the account history and draws, for each one, the full range it travelled: the best unrealised profit it ever showed (MFE) and the worst unrealised loss it survived (MAE). The gap between what a trade showed and what it paid is where two common problems hide, and neither is visible in a balance curve: winners closing far below their best point (the exit leaves money behind), and losers whose worst excursion barely passed the stop (the stop sits inside the noise). The number to look at is the CAPTURE RATIO: of the profit a winner showed at its best, how much did you take home? 90% says the exits are well placed; 30% says the market kept offering and the exit kept refusing. Limit, stated up front: excursions come from the bars each trade spanned, on the chart timeframe; the path inside a bar is unknown. Predicts nothing; measures trades that already happened.
134
Joao Prata Silva Yglesias
已发布代码Decision Watchdog: refuse yesterday's decision, fail closed, log once
A daily process writes "today's decision" (which strategy runs, or FLAT) to a file the EAs read at the open. One day the writer did not run. The EAs read yesterday's file, compared its date with TimeCurrent() - the server clock, which had stepped back to the previous day overnight - saw a match, and traded all morning on a 24-hour-old decision. No error anywhere. Two rules, both in this class: 1) staleness is judged against TimeLocal(), which always moves forward; TimeCurrent() is the last tick's stamp - it freezes without ticks and can step back on reconnect. 2) When in doubt the answer is FLAT: missing file, bad date, wrong day, empty line - every failure path returns "do nothing", and each is logged ONCE per state change, not on every tick and not never. File format: line 1 = ISO date, line 2 = decision string. The demo writes a fresh, a stale, a malformed, an empty and a missing file, and shows that only the first is allowed to trade.
86
Joao Prata Silva Yglesias
已发布代码Exposure Cap: one position limit per symbol across all your EAs
Four EAs on the same symbol, each one honest on its own: each checks "do I have a position?" with its own magic number, sees none, and enters. On a demo account this reached 22 contracts on a symbol meant to carry 1, and a watchdog had to close 16 positions in one morning. The cap belongs at the door, not after the fact. ExposureCap::Allowed(symbol, lots, cap) sums the volume of every open position on the symbol - all magic numbers, manual trades included - and refuses the order BEFORE it is sent when it would breach the cap. One log line with the three numbers (held, requested, cap) says why. Deliberately simple: gross exposure, no netting of longs against shorts, no per-EA quota. It is a check, not a lock: two EAs deciding on the same tick can both pass; in practice EAs on different charts decide on different ticks. The demo script prints held / cap / room for the current symbol and shows the refusal line. Nothing is traded.
84
Joao Prata Silva Yglesias
已发布代码Server Time Offset: the three clocks in MQL5 and how timestamps shift on export
A datetime in MQL5 is seconds since 1970 - but server time (TimeCurrent, bar times, deal times) is the broker's wall clock stored AS IF it were UTC. Export it to CSV, read it in Python or a spreadsheet with a "seconds since 1970 UTC" parser, and every timestamp shifts by the server's UTC offset. On a UTC-3 broker that is three hours: the daily bar dated 00:00 reads as 21:00 of the previous day, and "yesterday's session" silently becomes "today's, half formed". That happened to a morning report of mine before this script existed. The script prints TimeTradeServer, TimeCurrent, TimeGMT and TimeLocal, the three offsets between them, the tick lag, and this chart's last bar time in server time and in real UTC - then states the rule: export server timestamps as wall-clock text, or export the epoch together with the offset, and never let the consumer apply its own timezone.
100
Joao Prata Silva Yglesias
已发布代码Elder Force Index (faithful to the book definition)
Índice de Força, conforme definido por Alexander Elder: Volume x (Fechamento de hoje - Fechamento de ontem), e a série resultante é então suavizada. Dois comprimentos, 2 e 13, ambos de seus livros.
25
Joao Prata Silva Yglesias
发布MetaTrader 5信号
SurfBot 2.06 — one-direction Forex grid with hard capital caps, running on a real FXGlobe account. This is the live record of the exact engine sold on the MQL5 Market as SurfBot (product 179990, magic number 880001): https://www.mql5.com/en/market/product/179990 WHAT IT DOES: one grid per pair, on ONE side only (long or short), chosen by the better swap. Each layer has its own take-profit one spacing away. There is NO stop-loss per trade, by design. WHAT KEEPS IT ALIVE: max 12 layers per pair
Joao Prata Silva Yglesias
已发布产品
SurfBot Radar is a free breakout and trend indicator for MetaTrader 5. It plots a Donchian channel (the highest high and lowest low of the last N bars), marks the first bar that breaks the channel, and confirms each breakout with flow — the net of directional volume over a recent window. Breakout + matching flow shows a clear BUY or SELL signal; a breakout without flow is flagged as "no confirmation". A graphical on-chart panel (placeable in any corner) shows the current state, the flow, the
Joao Prata Silva Yglesias
已发布产品
SurfBot — one-direction Forex grid with hard capital caps. No stop-loss per trade, by design. 🔴 Live performance (verified, real account, this exact engine): https://www.mql5.com/en/signals/2383326 WHAT IT DOES Runs one grid per pair, on ONE side only (long or short). The side is chosen by the better swap (GridSide=AUTO) or forced by you. Each layer has its own take-profit one spacing away; there is no stop-loss per trade. Spacing comes from a built-in table per pair (percent of price), widened