← Back to NitroPosted 16 Oct 2025 · Commenced 1 Oct 2026
Nitro Trades · video
My Trading Strategy Is Boring, But It Makes Me $1-2K A Day (Full Guide)
Code base used · SMT All-in-One + Roman Essentials v0.1
Target stack for Nitro CRT. Versions per /workspace/smt-python/VERSION_LOG.md.
- Code base
- SMT_AllinOne + Roman v0.1: Python power-test surface pinned 2026-09-25;
smt_strategy/allinone/, CLIsmt_strategy/run_smt_allinone_roman.py. - Order manager
- Roman Essentials Host v0.1 (pinned 2026-09-24). Param bag
essentials_params_full.json, version 2026-09-25: 294 params across 11 categories and 37 groups. - Entry plugin
- Nitro CRT plugin v1 (
nitro_crt_v1, 2026-09-24) is entry-only: it sends entry signals, and Roman Essentials/ZZ manages the trades (size, stops, TP ladder, session, max trades, trailing). - Ninja (reference)
- Full SMT Strategy V3 (
AllinOneStrategy) on PC2.
Honesty line: today's Nitro CRT backtest (run_nitro_crt_a_rebreak_bt.py, 10 stocks, clean data: −$86,953, PF 0.90, 370 trades) used a simplified Roman-style order-management stand-in (one stop, one target, 0.5% risk, max 2/day), not the full stack. It has not yet been run through the full All-in-One + Roman order manager. Source: smt-python/results/nitro_crt_weekly_clean_2026-10-01/compare_summary.json (STOCKS_COMBINED).
My Trading Strategy Is Boring, But It Makes Me $1-2K A Day (Full Guide)
Key frames 5 flagged
Source: WATCH_ALONG.md Curated timeline.
00:40 · TradeZella stats
on screen TradeZella stats
what's said '10.19 profit factor is not normal'
rule it illustrates stats
03:32 · schematic HOD/LOD
on screen schematic HOD/LOD
what's said 'I want to see the break, I want to see price hold'
rule it illustrates break holds
04:26 · NVDA example
on screen NVDA example
what's said 'break of the low of day... instant reversal back up means nothing to me'
rule it illustrates failed break
10:40 · AMD FVG reaction
on screen AMD FVG reaction
what's said 'flips completely to green'
rule it illustrates confirmation
13:20 · TSLA short
on screen TSLA short
what's said 'Stop loss goes at the high of the middle candle of the fair value gap'
rule it illustrates stop
Worked examples (2 A+ / 2 total)
| id | kind | t | instrument | date on screen | CRT TF | dir | entry mode | entry | stop | target | RR | outcome | frame |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ph3v-A1 | a_plus | 08:17–12:24 | AMD calls (1m) | not shown | not shown | long | HOD break → first FVG → red→green flip → next open | not shown | trailing ratchet | highs | not shown | +~60% (ran ~400% after) | 074_09m25s_10s_fvg.png |
| ph3v-A2 | a_plus | 12:24–13:39 | TSLA puts | not shown | not shown | short | LOD break → FVG → green→red flip → next open | not shown | high of FVG middle candle | not shown | not shown | win (amount not stated) | 094_12m45s_10s.png |
ph3v-A1 · frames
ph3v-A2 · frames
Summary bullets 7
(en-orig deep-card captions; timestamps are video mm:ss; “not stated” is retained where the card gives no rule.)
Main logic
- Mark HOD/LOD after open; holding break, post-break FVG, first FVG tested and reaction candle; clear trend/high volume/relative strength.
Entry
- Reaction candle closes/respects FVG; enter next candle open; first FVG tested ~95%.
Stop
- FVG middle candle high/low (short example); otherwise ratchet stop when no 1H level.
Target
- Next 1H level if present; otherwise ratchet stop, not a fixed target.
Risk filters
- 09:30–11:00, wait about 10m; skip chop and FVGs before highs established; high-volume only.
Timeframe
- 1–5m, highest TF with FVG; 09:30–11:00 ET.
Exceptions
- No CRT or fixed RR; one perfect trade/day; exit behavior is ratchet.
Pipeline outcome
My Trading Strategy Is Boring, But It Makes Me $1-2K A Day (Full Guide)
Video ph3vv5mRwW4 · updated 2026-10-01
1Strategy write-up
- Main logic
- Mark HOD/LOD after open; holding break, post-break FVG, first FVG tested and reaction candle; clear trend/high volume/relative strength.
- Entry
- Reaction candle closes/respects FVG; enter next candle open; first FVG tested ~95%.
- Stop
- FVG middle candle high/low (short example); otherwise ratchet stop when no 1H level.
- Target
- Next 1H level if present; otherwise ratchet stop, not a fixed target.
- Risk filters
- 09:30–11:00, wait about 10m; skip chop and FVGs before highs established; high-volume only.
- Timeframe
- 1–5m, highest TF with FVG; 09:30–11:00 ET.
- Exceptions
- No CRT or fixed RR; one perfect trade/day; exit behavior is ratchet.
2Already in All-in-One
- allinone_v4/levels.py::detect_levels (FVG/OB/swing levels)
- smt_strategy/ict/fvg.py and fvg_entries.py (FVG primitives)
- playbooks/runner.py::_collect_signals + combined.py::match_combined_entries (preset FVG candidates)
- allinone_v4/engine.py::_resolve_levels and ::_exit_scan (exits)
3New features
| Feature | Notes | Status |
|---|---|---|
| break_then_gap | Holding HOD/LOD break before FVG. | not yet coded |
| fvg_retest_confirmation | Reaction candle. | not yet coded |
| fvg_middle_candle_stop | Middle-candle stop. | not yet coded |
| fvg_target_1h_or_fixed_rr | Next 1H level or ratchet. | not yet coded |
| fvg_timeframe_select | Highest TF with FVG. | not yet coded |
| relative_strength_filter | High-volume/relative-strength context. | not yet coded |
Playbook summary what this video teaches
- Setup (BOS-FVG): mark HOD/LOD after the open; a holding break, post-break FVG, first FVG tested, reaction candle; clear trend, high volume, relative strength.
- Entry: reaction candle closes/respects the FVG; enter at the next candle open (first FVG tested ~95% of the time).
- Stop: FVG middle-candle high/low (short example).
- Target: next 1H level if present; otherwise a ratchet stop instead of a fixed target.
- Window: 09:30-11:00 ET, wait about 10 minutes; 1-5m, highest TF with an FVG.
- Filters: skip chop and FVGs formed before the highs are established; high-volume names only; one perfect trade per day.
Source: /workspace/nitro-setups/nitro_last15_2026-10-01/ph3vv5mRwW4/outcome.json (+ BULLETS.md / DEEP_CARD.md in the same pack)
Code model notes how the ideas map to code
(a) Parameters and suggested defaults
| Parameter | Suggested default | Source |
|---|---|---|
levels | HOD/LOD after open | video |
open_delay_min | ~10 | video |
tf | highest of 1-5m with FVG | video |
stop | FVG middle-candle high/low | video |
target | next 1H level, else ratchet stop | video |
window | 09:30-11:00 ET | video |
max_trades_per_day | 1 | video |
ratchet_rule | not specified in video, needs testing | not quantified |
(b) Detection and entry logic
- Wait ~10 min for HOD/LOD; detect a holding break, then the first post-break FVG.
- Enter at the next open after the reaction candle; stop at the middle-candle extreme.
- Exit at the next 1H level or by ratcheting the stop.
(c) Already coded in our Nitro CRT implementation
- The Nitro CRT runner and plugin contain no BOS / FVG / opening-range logic.
- Reusable primitives exist elsewhere but are NOT wired to Nitro: smt_strategy/ict/fvg.py::detect_fvgs, ict/fvg_entries.py::generate_fvg_entry_signals, ict/bos.py::detect_bos, allinone_v4/levels.py::detect_levels.
- Plugin nitro_crt_v1: python/signal_contract.py::build_signal only formats an entry signal (trigger_price, stop_hint, target_hint); ninja/NitroCRT_Entry_v1.cs is a stub (EmitOnly=true, session + RequireHtfBias knobs, no C1/C2 detector). Roman Essentials/ZZ is the order manager.
(d) Still to build (from outcome.json)
| Feature | Note | vs current code | Status |
|---|---|---|---|
break_then_gap | Holding HOD/LOD break before FVG. | not in Nitro code (FVG/BOS primitives in smt_strategy/ict/ are not wired) | not yet coded |
fvg_retest_confirmation | Reaction candle. | not in Nitro code (FVG/BOS primitives in smt_strategy/ict/ are not wired) | not yet coded |
fvg_middle_candle_stop | Middle-candle stop. | not in Nitro code (FVG/BOS primitives in smt_strategy/ict/ are not wired) | not yet coded |
fvg_target_1h_or_fixed_rr | Next 1H level or ratchet. | not in Nitro code (FVG/BOS primitives in smt_strategy/ict/ are not wired) | not yet coded |
fvg_timeframe_select | Highest TF with FVG. | not in Nitro code (FVG/BOS primitives in smt_strategy/ict/ are not wired) | not yet coded |
relative_strength_filter | High-volume/relative-strength context. | not in Nitro code (FVG/BOS primitives in smt_strategy/ict/ are not wired) | not yet coded |
Code checked: /workspace/nitro-setups/backtests/run_nitro_crt_a_rebreak_bt.py, /workspace/smt-python/entry_plugins/nitro_crt_v1/ (read only), backtests/sweep_2026-09-29/sweep_core.py. Statuses unchanged from outcome.json.
DSG /dev · Top Traders · training / second-gate only