|
6+ yıl
deneyim
|
4
ürünler
|
2
demo sürümleri
|
|
0
işler
|
2
sinyaller
|
0
aboneler
|
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
ürün yayınladı
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
ürün yayınladı
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 kodunu yayınladı
Farklı işlevlere sahip üç pozisyon büyüklüğü koruma mekanizması; bunların birbiriyle karıştırılması, pek çok hesabın tamamen silinmesine neden olmaktadır:
- merdiven: bakiyenin her X birimi başına bir kontrat; manuel lot belirleme durumunda bile her zaman bir üst sınır (CAP) olarak uygulanır;
- floor: minimum sermayenin altına düştüğünde işlem yapmaz; yeni bir para yatırımı gerekir;
- breaker: hesap büyüklüğü ne olursa olsun, zirvenin X% altına düştüğünde durur ve kendi kendine yeniden etkinleşmez.
Bu kütüphanenin çözdüğü ve neredeyse hiçbirinin çözemediği sorun: para yatırımı kâr değildir ve para çekme işlemi de zarar değildir. Breaker, düşüşü bakiye zirvesine göre ölçer. Bu durum dikkate alınmazsa, bir düşüş SIRASINDA yapılan para yatırma işlemi hem bakiyeyi hem de zirveyi yükseltir ve koruma, tam da yardımcı olacağı anda düşüşü algılamayı durdurur. Burada para yatırma ve çekme işlemleri, zirveyi aynı miktarda kaydırır.
Zirve değeri bir dosyaya kaydedilir: terminal yeniden başlatıldığında zirve değerini unutan bir kırıcı, gerçek bir kırıcı değildir.
Demo, düşüşün en dip noktasında yapılan bir para yatırma işlemini simüle eder. Para yatırma seçeneğini açık ve kapalı olarak çalıştırın ve "düşüş" sütununu karşılaştırın.
3
86
Joao Prata Silva Yglesias
Safe Logger: why your log lines vanish while FileOpen keeps returning success kodunu yayınladı
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 kodunu yayınladı
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 kodunu yayınladı
Kapanan her işlem için, hesap özetinde yer almayan rakamları içeren bir CSV satırı dışa aktarır: işlemin gösterdiği en yüksek gerçekleşmemiş kâr (MFE), atlattığı en kötü gerçekleşmemiş zarar (MAE), MFE’nin ne kadarının fiilen elde edildiği, kaç çubuk boyunca sürdüğü ve ne kadar süreyle açık kaldığı. Trade Excursion göstergesiyle aynı ölçümler, grafikte gösterilmek yerine bir dosyaya yazılır; çünkü bu verilerle ilgili sorulması gereken sorular, bir grafiğin cevaplayamayacağı sorulardır: yakalama oranı giriş saatine bağlı mıdır? Erken kapattığım işlemler, en uzun süre tuttuklarım mı? Pazartesi günleri gerçekleşen zararlı işlemlerin MAE değeri, Cuma günlerinkinden farklı mı? CSV dosyası hazır olduğunda, bu soruların yanıtlarını bir pivot tablo ile kolayca elde edebilirsiniz. Çıktı, MQL5\Files dizininde başlık satırı ile birlikte noktalı virgülle ayrılmış haldedir; herhangi bir elektronik tabloda açılabilir. Ölçüm sınırı: sapmalar, seçilen zaman dilimindeki çubukların en yüksek ve en düşük değerlerinden elde edilir; çubuk içindeki yol bilinmemektedir. Çubuklar sütunu, her işlemin elde ettiği çözünürlüğü bildirir ve özet, tek çubuklu işlemleri ortalamak yerine ayrı ayrı sayar.
10
141
Joao Prata Silva Yglesias
Trade Excursion: how much of each winner you actually kept (MFE/MAE from your own history) kodunu yayınladı
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 kodunu yayınladı
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 kodunu yayınladı
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 kodunu yayınladı
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) kodunu yayınladı
Í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 sinyali yayınladı
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
ürün yayınladı
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
ürün yayınladı
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
Joao Prata Silva Yglesias
MetaTrader 5 sinyali yayınladı
"SurfBot Bidirectional Grid" kullanılabilir değil