<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>EA Operations on FX Backtest Diary</title><link>https://etherpoc.com/en/tags/ea-operations/</link><description>Recent content in EA Operations on FX Backtest Diary</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 21 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://etherpoc.com/en/tags/ea-operations/index.xml" rel="self" type="application/rss+xml"/><item><title>Audit findings get measured before they get fixed</title><link>https://etherpoc.com/en/posts/audit-verify/</link><pubDate>Tue, 21 Jul 2026 00:00:00 +0000</pubDate><guid>https://etherpoc.com/en/posts/audit-verify/</guid><description>&lt;p&gt;At one point I put the roughly 2,500 lines of my live EA&amp;rsquo;s source through a full bug audit. It produced 20 findings, ranging from genuinely dangerous holes (a halt latch that evaporated on restart) to a subtler species: places where the EA&amp;rsquo;s behavior quietly differs from the verified research code.&lt;/p&gt;</description></item><item><title>Running My EA on a Real Prop-Firm Account (Live Forward Log)</title><link>https://etherpoc.com/en/posts/forward/</link><pubDate>Thu, 09 Jul 2026 00:00:00 +0000</pubDate><guid>https://etherpoc.com/en/posts/forward/</guid><description>&lt;p&gt;Most articles on this site are backtests. This page is different: it is the &lt;strong&gt;live forward record&lt;/strong&gt; — what is happening right now to the EA running on a real account.&lt;/p&gt;
&lt;p&gt;Ground rules for this log:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Only measured numbers from the actual account.&lt;/strong&gt; If I ever quote an estimate or a simulation, I will label it as such.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Bad results get reported exactly like good ones.&lt;/strong&gt; If the account fails the evaluation, this page will say so.&lt;/li&gt;
&lt;li&gt;Updates are irregular (when something happens, plus milestones).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="what-is-running-under-what-conditions"&gt;What is running, under what conditions&lt;/h2&gt;
&lt;table&gt;
	&lt;thead&gt;
			&lt;tr&gt;
					&lt;th&gt;Item&lt;/th&gt;
					&lt;th&gt;Details&lt;/th&gt;
			&lt;/tr&gt;
	&lt;/thead&gt;
	&lt;tbody&gt;
			&lt;tr&gt;
					&lt;td&gt;Account&lt;/td&gt;
					&lt;td&gt;Fintokei ProTrader Challenge &lt;strong&gt;STEP 1&lt;/strong&gt; (a real evaluation account)&lt;/td&gt;
			&lt;/tr&gt;
			&lt;tr&gt;
					&lt;td&gt;Account size&lt;/td&gt;
					&lt;td&gt;¥10,000,000&lt;/td&gt;
			&lt;/tr&gt;
			&lt;tr&gt;
					&lt;td&gt;Start date&lt;/td&gt;
					&lt;td&gt;&lt;strong&gt;2026-07-04&lt;/strong&gt;&lt;/td&gt;
			&lt;/tr&gt;
			&lt;tr&gt;
					&lt;td&gt;Pass conditions&lt;/td&gt;
					&lt;td&gt;+8% (then +6% in STEP 2). One breach of daily -5%, max -10%, or total open risk -3% means failure&lt;/td&gt;
			&lt;/tr&gt;
			&lt;tr&gt;
					&lt;td&gt;EA&lt;/td&gt;
					&lt;td&gt;CoreSystemV14 — the MT5 implementation of the &lt;a href="https://etherpoc.com/en/posts/core-system-v1.5.0/"&gt;finalized system&lt;/a&gt; validated on this site (all 7 sleeves)&lt;/td&gt;
			&lt;/tr&gt;
			&lt;tr&gt;
					&lt;td&gt;Risk settings&lt;/td&gt;
					&lt;td&gt;Challenge preset (base leverage 2.5 / cap 2.5 — stage 1 of the &lt;a href="https://etherpoc.com/en/posts/research-195/"&gt;three-stage plan&lt;/a&gt;)&lt;/td&gt;
			&lt;/tr&gt;
			&lt;tr&gt;
					&lt;td&gt;Safety guards&lt;/td&gt;
					&lt;td&gt;Flatten everything at daily -4%; halt new entries + flatten at account DD -7% (designed to step off well before the disqualification lines)&lt;/td&gt;
			&lt;/tr&gt;
	&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;For transparency, the backtest-derived expectations (past data, 2015–2026, 11 years): &lt;strong&gt;+0.82%/month, PF 1.66&lt;/strong&gt;, max DD -7.7% for the base system. Monte Carlo on the challenge settings says there is roughly a 30% chance of touching a -5% account drawdown at some point before passing, and about a 1% failure probability on the unstressed distribution. In other words: seeing a few percent of drawdown along the way is part of the plan.&lt;/p&gt;</description></item><item><title>I stopped hand-carrying EA updates to my VPS — a git-based auto-deploy for MT5</title><link>https://etherpoc.com/en/posts/ea-auto-deploy/</link><pubDate>Wed, 08 Jul 2026 00:00:00 +0000</pubDate><guid>https://etherpoc.com/en/posts/ea-auto-deploy/</guid><description>&lt;p&gt;The expert advisors on this site run 24/5 on MT5 inside a Windows VPS, while all development happens on my local machine. Every EA change used to require this ritual:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Compile and test locally, push to git&lt;/li&gt;
&lt;li&gt;Log into the VPS over Remote Desktop (RDP)&lt;/li&gt;
&lt;li&gt;&lt;code&gt;git pull&lt;/code&gt; on the VPS&lt;/li&gt;
&lt;li&gt;Recompile in MetaEditor&lt;/li&gt;
&lt;li&gt;Manually restart the EA on its chart&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;A few minutes each time, but with real money attached, every step demands attention. And in my setup, most EA code changes are made by an AI agent (Claude Code) — which meant the human&amp;rsquo;s only remaining job was being a courier who carries the AI&amp;rsquo;s work to the VPS. Time to automate the courier away.&lt;/p&gt;</description></item></channel></rss>