FIL_Grid_Engine — Performance
Window 3.2 years (2023-07-15 → 2026-09-14, 111,044 bars of 15m) · Markets ADA, BTC, DOGE, ETH, LINK, SOL, XRP Costs 0.10% taker fee + 2 bps slippage on every fill Timeframe declares 15m — tested at its own timeframe Capital 1,000 quote Sizing unknown
How this was measured
Every decision is taken on a bar that has closed, and the resulting market order fills at the next bar's open plus slippage. Resting stop and target orders fill intrabar, and when one bar's range covers both the stop and the target the stop is taken first — the pessimistic reading wherever candle data cannot resolve the order of events inside a bar.
The engine is validated separately by 53 known-answer tests covering accounting, fee arithmetic, determinism and the no-look-ahead boundary. Nothing below means anything unless those pass, so the pipeline aborts if they do not.
Result by market
| Market | Orders | Round trips | Return | Buy & hold | Edge | Max DD | Sharpe | Win rate | Profit factor | Time in market |
|---|---|---|---|---|---|---|---|---|---|---|
ADA |
58 | 22 | -2.4% | -31.1% | 28.7% | 2.4% | -0.82 | 0% | 0.00 | 0.2% |
BTC |
52 | 27 | -0.2% | 161.0% | -161.2% | 0.2% | -1.67 | 11% | 0.00 | 0.2% |
DOGE |
31 | 16 | -0.2% | 9.9% | -10.1% | 0.3% | -0.41 | 19% | 0.04 | 0.4% |
ETH |
89 | 40 | -2.8% | 34.3% | -37.1% | 2.8% | -0.61 | 5% | 0.00 | 0.1% |
LINK |
115 | 54 | -3.8% | 49.6% | -53.4% | 3.8% | -0.60 | 39% | 0.03 | 0.1% |
SOL |
85 | 33 | -4.3% | 307.6% | -311.9% | 4.3% | -0.59 | 48% | 0.01 | 0.0% |
XRP |
73 | 33 | -4.2% | 113.2% | -117.3% | 4.2% | -0.57 | 45% | 0.01 | 0.1% |
Median across markets: -2.8% return, 2.8% max drawdown, Sharpe -0.60.
The median is the honest number, not the best market. Ranking a strategy on its best pair measures which pair was picked, not what the strategy does.
Reading these numbers
- Profitable on 0 of 7 markets, beat buy-and-hold on 1. Those differ because buy-and-hold itself returned a median 49.6% here, so "beat buy-and-hold" can mean nothing more than having held less.
- Best-to-worst spread is 4.1% (BTC -0.2% vs SOL -4.3%). That is reasonably tight across very different assets.
- Time in market is 0.1%. The equity curve is mostly flat cash, so the result rests on a small fraction of the bars however long the window. The 2.8% drawdown is incurred inside that 0.1%, not spread across the window — being out of the market most of the time does not make the committed time any safer.
- Fees cost 0.22% of starting capital at the median, across 225 round trips.
Variant B — no stop loss, never sells below the position average
The same strategy on the same data, with one rule added: no exit may be priced below the position's average cost. That also removes every stop-loss, since a stop sits below the entry by definition. It is the "never realise a loss" version.
| A — as shipped | B — no-loss exits | |
|---|---|---|
| Median return | -2.8% | 26.9% |
| Median max drawdown | 2.8% | 66.8% |
| Profitable markets | 0 / 7 | 6 / 7 |
| Ends still holding | — | 7 / 7 |
| Exits refused by the rule | 0 | 7,364 |
| Market | A return | B return | A max DD | B max DD | B ends holding |
|---|---|---|---|---|---|
ADA |
-2.4% | -14.4% | 2.4% | 71.7% | yes |
BTC |
-0.2% | 26.9% | 0.2% | 24.9% | yes |
DOGE |
-0.2% | 4.5% | 0.3% | 69.0% | yes |
ETH |
-2.8% | 14.4% | 2.8% | 45.5% | yes |
LINK |
-3.8% | 31.1% | 3.8% | 66.8% | yes |
SOL |
-4.3% | 178.0% | 4.3% | 74.6% | yes |
XRP |
-4.2% | 41.8% | 4.2% | 56.0% | yes |
How to read this. Variant B reports the higher return — 26.9% against -2.8% — and that is mostly not an improvement. A loss that is never closed does not disappear, it sits in inventory. That is why max drawdown rises from 2.8% to 66.8%, and why the strategy ends still holding on 7 of 7 markets: B's reported return leaves out the positions it never resolved. The rule refused 7,364 exits over the window.
Read the two together rather than picking one. A is what the strategy does; B is what it looks like with its losses deferred instead of taken, and the gap between them measures how much of A's result comes from cutting.
Why it exited
Every exit the engine executed, attributed to the message the strategy emitted on that bar. One bar is one decision, so an event announced on both the console and the side panel is counted once.
| Exit | Count | Share | Mean gain | Worst |
|---|---|---|---|---|
FILLED |
4,818 | 55.9% | — | — |
| (unexplained) | 3,796 | 44.1% | — | — |
3,796 of 8,614 exits (44.1%) carry no explanation. The position changed and the strategy said nothing about why. That is usually a resting order — a
customSellTargetorcustomStopTargetthe exchange fills without calling back into the strategy — in which case the strategy's own P&L, trade count and win rate never saw those trades either. See the fixes report.
Cost sensitivity
The strategy places the same number of orders at 0% fees as at 0.10%. That is a correctness property rather than a performance one: it proves no balance gate becomes unsatisfiable once costs leave the wallet. A strategy that fails this check stops trading silently the moment it meets a real fee schedule.
| Market | Orders at 0.10% fee | Orders at 0% fee | Ratio |
|---|---|---|---|
ADA |
36 | 36 | 1.00 |
BTC |
25 | 25 | 1.00 |
DOGE |
15 | 15 | 1.00 |
ETH |
49 | 49 | 1.00 |
LINK |
61 | 61 | 1.00 |
SOL |
52 | 53 | 0.98 |
XRP |
40 | 40 | 1.00 |
Correctness invariants
| Invariant | Result |
|---|---|
| runs clean on every market | PASS |
| no phantom chart marks | PASS |
| no negative balances | PASS |
| cost independent (fees change P&L, not the ability to act) | PASS |
| places orders somewhere | PASS |
Outstanding notes
- holds a position only 0.2% of the time — it commits properly (peak 23.7%) but the result rests on very few bars, so treat it as a small sample
What this window cannot tell you
A single year is a small sample, and this one was a broad downtrend.
The engine models spot, long-only, one price per bar. It carries no order book, so it cannot see spread, queue position or depth, and a strategy whose edge is the spread cannot be measured here at all.
Every number on this page is read from the run record that produced it — the audit pipeline writes the page and the record together, so the two cannot drift apart.