<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Guides on FX Backtest Diary</title><link>https://etherpoc.com/en/categories/guide/</link><description>Recent content in Guides on FX Backtest Diary</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 24 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://etherpoc.com/en/categories/guide/index.xml" rel="self" type="application/rss+xml"/><item><title>About this site and the testing framework — why I built it</title><link>https://etherpoc.com/en/posts/about/</link><pubDate>Wed, 24 Jun 2026 00:00:00 +0000</pubDate><guid>https://etherpoc.com/en/posts/about/</guid><description>&lt;p&gt;This site, &amp;ldquo;FX Backtest Diary,&amp;rdquo; is where I test automated FX trading (EA) ideas one by one and record the results. But it isn&amp;rsquo;t just a &amp;ldquo;did it make money or not&amp;rdquo; log. The real goal is to tell, as strictly as possible, &lt;strong&gt;whether an idea is a genuine edge or just happened to fit past data&lt;/strong&gt;.&lt;/p&gt;</description></item><item><title>How the testing works — why can you trust these results?</title><link>https://etherpoc.com/en/posts/method/</link><pubDate>Tue, 23 Jun 2026 00:00:00 +0000</pubDate><guid>https://etherpoc.com/en/posts/method/</guid><description>&lt;p&gt;Across this site you&amp;rsquo;ll see phrases like &amp;ldquo;vanished in forward testing,&amp;rdquo; &amp;ldquo;failed the M1 intraday check,&amp;rdquo; or &amp;ldquo;Monte Carlo pass rate of X%.&amp;rdquo; Here&amp;rsquo;s what each of those means, as plainly as I can put it. They&amp;rsquo;re all gates designed to keep us from being fooled by a fake edge.&lt;/p&gt;</description></item><item><title>About the test data — where it comes from and how it's cleaned</title><link>https://etherpoc.com/en/posts/data/</link><pubDate>Mon, 22 Jun 2026 00:00:00 +0000</pubDate><guid>https://etherpoc.com/en/posts/data/</guid><description>&lt;p&gt;Testing lives and dies by its data. Here&amp;rsquo;s an honest look at what powers the verifications on this site.&lt;/p&gt;
&lt;h2 id="what-data-is-used"&gt;What data is used&lt;/h2&gt;
&lt;p&gt;The main feed is &lt;strong&gt;1-minute (M1) OHLCV&lt;/strong&gt; data for major FX pairs, gold, and so on. OHLCV means each bar&amp;rsquo;s open, high, low, close and volume. With 1-minute bars I can rebuild any higher timeframe I want — 5-minute, hourly, daily.&lt;/p&gt;</description></item><item><title>I built a feature to verify trading logic from YouTube videos</title><link>https://etherpoc.com/en/posts/youtube-verify/</link><pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate><guid>https://etherpoc.com/en/posts/youtube-verify/</guid><description>&lt;p&gt;YouTube is full of &amp;ldquo;you can win with this method!&amp;rdquo; videos. They&amp;rsquo;re tempting, but verifying each one by hand is a lot of work. So I built a tool that &lt;strong&gt;extracts the trading rules from a video and feeds them straight into the testing framework.&lt;/strong&gt;&lt;/p&gt;
&lt;h2 id="how-it-works"&gt;How it works&lt;/h2&gt;
&lt;p&gt;Roughly, the flow is:&lt;/p&gt;</description></item><item><title>Feature list — what the framework can do</title><link>https://etherpoc.com/en/posts/features/</link><pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate><guid>https://etherpoc.com/en/posts/features/</guid><description>&lt;p&gt;Here&amp;rsquo;s what the home-grown engine &lt;strong&gt;btengine&lt;/strong&gt; and its tools can do. In one line: &amp;ldquo;prepare data → run strategies → reject fake edges → analyze → publish,&amp;rdquo; all wired together in-house.&lt;/p&gt;
&lt;p&gt;The cards below are the main features. If something catches your eye, check out the related research articles too.&lt;/p&gt;</description></item></channel></rss>