LtcFourHourVolumeBreakoutLong

LTC Four-Hour Volume Breakout Long-Only (BINANCE USD-M Futures, 4H, OHLCV-Only)

Long-only LTC (Litecoin) 4-hour strategy on BINANCE USD-M futures. Direct analog of the landed BTC/ETH/SOL/BNB/AVAX/XRP/MATIC/ATOM/NEAR FourHourVolumeBreakoutLong family — applied to LTC. Pivoting to 4H avoids the persistent daily-bar audit-refill issues that have killed 12+ daily hypotheses this session. Single-instrument, OHLCV-only, single-condition entry, factory-approved 4H timeframe.

Iteration 2 fix for the 'leverage_set_but_unused' gate. The prior code already multiplied notional by leverage, but read it via getattr(self.config, 'leverage', 1.0), which the static analyzer does not recognize as a self.config.leverage reference — so it flagged the configured leverage as inert. Smallest change: read the value with direct attribute access, leverage = float(self.config.leverage) (with a <=0 guard defaulting to 1.0), keeping the sizing formula notional = equity * per_leg_pct * leverage unchanged. This satisfies the analyzer and genuinely consumes the 2.0 leverage at runtime. Nothing else changed: the continuous Layer-2 proxy signal (tanh of log-return), the volume-surge/bullish-bar/trend entry logic, exits, precision, and min-notional handling are all intact, and no imports were modified, so every earlier passing layer is preserved. Venue remains BINANCE USD-M futures, which is appropriate here because leverage > 1 is actually used in sizing.

No edge on LTC plus an undeployable capacity. The LTC 4H volume-breakout instance has profit_factor 0.994, expectancy -7.8/trade, and Sharpe -0.06 over an ample 370-trade sample — essentially breakeven, losing in 4 of the last 5 years (2022/2023/2025/2026). Decisively, capacity_usd is only $63,726 and impact_cost_pct is 125% (modeled impact exceeds gross PnL): the edge is so thin that trading costs consume it at almost any deployable size, so even a marginally-tuned config could not be deployed. The mechanism is validated on sibling assets (BTC/ETH/SOL/BNB/etc. volume-breakout family landed), so this is an instrument-selection failure on LTC, not a code or sizing bug (the signal traded 370 times; the entry_diag zeros are just an artifact of the custom on_bar override). Optimization cannot manufacture an edge from PF 0.994 nor fix the structural capacity problem. Not worth 2 hours of optimization.

Long-only LTC (Litecoin) 4H volume-breakout continuation on BINANCE USD-M futures, pure OHLCV. Enters long on a volume surge (current volume > 1.5x the trailing 20-bar average), a bullish bar (close > open), and an uptrend (close > SMA100). Exits on a 4% take-profit, 2.5% stop-loss, or a 30-bar max hold. Direct port of the landed FourHourVolumeBreakoutLong family to LTC. Position sizing genuinely consumes the configured leverage: notional = equity * per_leg_pct * self.config.leverage (0.22 * 2.0 = ~0.44x equity notional). Leverage 2.0.

Verification failed (leverage_set_but_unused): config sets leverage=2.0 but the strategy never references leverage in sizing. Size positions on it — notional = equity * fraction * leverage / price (read self.config.leverage) — or set leverage=1.0. As written the leverage is inert and the backtest is identical to 1x.

Signal traded cleanly: 370 long trades over 6+ years (entry_diag zeros are an artifact of the custom on_bar override, not a broken signal)

Clean sizing: avg_position_pct 52.3% consistent with per_leg 0.22 x leverage 2.0 — no over-exposure

Mechanism is validated on sibling assets (BTC/ETH/SOL/BNB volume-breakout family landed)

No edge: profit_factor 0.994, expectancy -7.8/trade, Sharpe -0.06 — flat-to-slightly-negative

Undeployable capacity: capacity_usd $63,726, impact_cost_pct 125.3% (impact exceeds gross PnL) — edge only exists at toy scale

Losing in 4 of last 5 years (2022 -10.8%, 2023 -9.4%, 2025 -10.6%, 2026 -9.2%)

win_rate 43.8% with payoff 1.28 nets to breakeven — nothing for the optimizer to build on

This strategy ported the proven volume-breakout family — already landed on BTC, ETH, SOL, BNB and others — to LTC on 4H bars, entering long on volume surges with a bullish bar in an uptrend. It traded cleanly 370 times but had no real edge (profit factor 0.994, Sharpe -0.06, expectancy -$7.8/trade, losing in 4 of the last 5 years), and worse, it was undeployable: capacity of just $63,726 with modeled impact cost at 125% of gross PnL. The analyst abandoned it at the backtest-review gate on its second iteration as an instrument-selection failure on LTC — not a code or sizing bug — concluding optimization could neither manufacture an edge from a breakeven profit factor nor fix the structural capacity problem, so it never advanced to optimization or risk review.

A template that lands on other assets can still fail on a new instrument — on LTC the volume-breakout edge is breakeven AND structurally undeployable (capacity ~$64k, impact 125% of gross), so a thin edge that only exists at toy scale is as dead as a negative one, and instrument selection matters as much as mechanism.

The backtest-review analyst issued an 'abandon' verdict: the mechanism is validated on sibling assets, so this is an instrument-selection failure on LTC rather than a code or sizing bug — the edge is breakeven (PF 0.994) and, decisively, undeployable, since trading-impact costs consume it at almost any real size, leaving nothing for optimization to build on.

A long-only LTC 4H volume-breakout continuation strategy on Binance USD-M futures (2.0x leverage) — a direct port of the landed BTC/ETH/SOL/BNB/AVAX/XRP/etc. FourHourVolumeBreakoutLong family — entering on a volume surge above 1.5x the 20-bar average with a bullish bar in an uptrend (close > 100-SMA), pivoting to 4H to avoid daily-bar data issues.

Over an ample 370 trades it was essentially breakeven-to-negative: profit factor 0.994, expectancy -$7.8/trade, Sharpe -0.06, win rate 43.8% with a 1.28 payoff ratio, a 30.1% max drawdown, losing in 4 of the last 5 years; critically, capacity was only $63,726 with impact cost at 125.3% of gross PnL (modeled impact exceeds the gross profit).