PineForge’s book
- Trades
- 11,800
- Net P&L
- +262.81 USDT
- Largest drawdown, closed trades
- −2,631.44 USDT
- Win rate
- 50.3 %
- Profit factor
- 1.01
VCP: FVG active zones ETHUSDT 15m
All 11,800 trades identical in both books
Same side, entry and exit times, prices and quantity on every trade.
01,0002,000
Apr 2025Jul 2025Oct 2025Jan 2026Apr 2026
USDTTap or drag the chart to read any point.
Source: tv_trades.csv and engine_trades.csv in pineforge-corpus at d75b4fa.
The chart as a table
| Time (UTC) | TradingView, USDT | PineForge, USDT |
|---|---|---|
| 2025-03-31 18:00 | 21.94 | 21.94 |
| 2025-05-17 00:15 | 1,049.07 | 1,049.07 |
| 2025-07-06 04:00 | 709.11 | 709.11 |
| 2025-09-01 05:45 | 2,032.32 | 2,032.32 |
| 2025-10-22 05:00 | 1,798.18 | 1,798.18 |
| 2025-12-12 06:00 | 1,472.64 | 1,472.64 |
| 2026-01-26 18:30 | 863.87 | 863.87 |
| 2026-03-16 03:15 | 357.83 | 357.83 |
| 2026-05-01 00:00 | 262.81 | 262.81 |
The chart as a table
Computed from the same series as the P&L view: how far each book’s cumulative P&L sits under its own running peak.
| Time (UTC) | TradingView, USDT | PineForge, USDT |
|---|---|---|
| 2025-03-31 18:00 | 0.00 | 0.00 |
| 2025-05-17 00:15 | −6.52 | −6.52 |
| 2025-07-06 04:00 | −346.48 | −346.48 |
| 2025-09-01 05:45 | −638.79 | −638.79 |
| 2025-10-22 05:00 | −872.93 | −872.93 |
| 2025-12-12 06:00 | −1,198.47 | −1,198.47 |
| 2026-01-26 18:30 | −1,807.24 | −1,807.24 |
| 2026-03-16 03:15 | −2,313.28 | −2,313.28 |
| 2026-05-01 00:00 | −2,408.30 | −2,408.30 |
The chart as a table
Each square is one trade, counted by class. The squares are counts, not positions in time.
| Class | Trades |
|---|---|
| Identical | 11,800 |
| Differing | 0 |
| TradingView only | 0 |
| PineForge only | 0 |
| Total | 11,800 |
- TradingView, final P&L 262.81 USDT
- PineForge, final P&L 262.81 USDT
How this is measured
All 11,800 trades are identical in both books.
Source: TradingView’s export, tv_trades.csv, and PineForge’s trade list, engine_trades.csv, as committed in pineforge-corpus at d75b4fa; PineForge’s was written by engine v1.0.1.
Graded excellent by the engine’s open-corpus check, which allows entry and exit prices within 0.01 % of TradingView’s and P&L within 1 % at the 90th percentile, over the window both lists cover. For excellent, where TradingView shows two or more distinct entry Signals at one exact time, price and direction, the engine shows as many distinct entries there (distinct-entry identity). Identical means both files print the same side, entry and exit time and entry and exit price, and the same quantity to the decimals TradingView exports. How the grades work
This page shows the files committed in pineforge-corpus at commit d75b4fa: the Pine source, the C++ that codegen 1.0.1 generated from it and both trade lists, PineForge’s written by engine v1.0.1 from that C++. The grade comes from the engine’s corpus check at 35db01c8, which re-runs every strategy and which engine v1.6.2 includes. The pineforge-release 1.6.0 image carries engine and codegen 1.6.0 and runs them on the OHLCV data you give it; the published pair is v1.6.2.
Save the strategy’s strategy.pine from that corpus commit next to your OHLCV file, then run:
docker run --rm --network=none \
-v "$PWD/strategy.pine:/in/strategy.pine:ro" \
-v "$PWD/ohlcv.csv:/in/ohlcv.csv:ro" \
ghcr.io/pineforge-4pass/pineforge-release:1.6.0 > report.jsonAbout this strategy
Gap boundaries persist in parallel arrays alongside their bullish or bearish classification. After an ATR size filter admits a gap, array.push appends its fields and array.shift removes the oldest records when the retained length exceeds the script's cap. The var declarations preserve the arrays across bars. Each bar resets the overlap flags before scanning the arrays, allowing bullish and bearish overlaps to be detected independently. A bullish overlap can submit a long while flat; a bearish overlap can close an existing long. Touched zones are not removed during the scan.