SOL Weekend Volatility Regime Breakout

Exploit Solana's distinct weekend volatility regime on Binance USD-M Futures. During weekends, TradFi closure reduces institutional flow and market-maker activity, thinning liquidity and amplifying SOL price moves. The strategy detects the weekend regime shift (Friday ~20:00 UTC onwards) and trades volatility expansion breakouts when price breaches a range defined by late-Friday consolidation (high/low of 18:00-23:59 UTC Friday). Supplementary signals — funding rate divergence (>0.01%), declining open interest, and long/short ratio extremes — confirm reduced liquidity conditions ripe for exaggerated moves. Enter in breakout direction with ATR-based trailing stop, hard TP at 2-3x ATR, stop-loss at 1x ATR, and time stop at Monday 00:00 UTC. Weekend SOL moves of 3-5% are common; capturing 30-40% yields 1-2% per trade, well above the 0.15% fee threshold. Primary instrument: SOLUSDT Binance USD-M Futures (MARGIN account). Bar intervals: 1h primary, 4h regime confirmation. Risk factors: Sunday flash crashes, exchange maintenance windows, holiday anomalies, potential regime decay as weekend participation grows.

Iteration-2 minimal fix for the Layer-2 TypeError (_dt() takes 1 positional argument but 2 were given). Root cause: the UTC-conversion helper was a @staticmethod, but the Layer-2 _StrategyProxy rebinds class callables onto a stand-in instance, which discards the staticmethod descriptor and passes the proxy instance as an injected first positional argument, so a 1-param staticmethod is called with 2 args and raises on every scenario. The fix moves the helper to a module-level function `_ts_to_dt` (module functions are never bound to an instance, so no self can be injected) and renames it to avoid shadowing the `import datetime as _dt` alias; the two call sites in calculate_signal and should_exit now call `_ts_to_dt(...)`. Nothing else changed: imports stay clean (Layer 1 green), and the Friday-range/weekend-window/ATR-stop signal and entry/exit/sizing logic the harness exercised are byte-identical, so no earlier-layer regression. Venue remains BINANCE USD-M futures (long-short needs margin), leverage 1.0 (not used for amplification, so the leverage_set_but_unused gate does not trigger).

The SOL weekend volatility-breakout premise is empirically refuted: the strategy is a catastrophic, consistent loser with profit_factor 0.761, Sharpe -1.69 (CI entirely negative), total_return -79.8%, max_drawdown 84.4% (CI to 95%), expectancy -$81/trade, win_rate 32.5%, PSR 0.0041 — losing money in 6 of 7 years (2020 -19.3% through 2025 -19.5%, only 2026 positive) with rolling Sharpe -5 to -12 for long stretches. The code is correctly implemented and trades as specified (994 entries, 0 dropped), so this is a sign-wrong premise, not a bug: breakouts of the late-Friday consolidation range over the weekend whipsaw and revert (false breakouts in thin weekend liquidity) rather than continue, the opposite of the thesis, and the 1H frequency over-churns (994 trades, $21k commission + $18.9k impact, 8.27% of gross) compounding the loss. The hypothesis's funding/OI/long-short-ratio confirmation was never implemented (the code is pure OHLCV). Not optimize: no ATR/threshold tuning flips a Sharpe -1.69, PF 0.76, 84%-drawdown strategy that loses in 6 of 7 years into a winner. Not iterate: the code correctly implements the premise; the only 'fix' is to invert into a weekend-range-fade (mean-reversion), which is a different hypothesis. Not worth 2 hours. FAILURE PATTERN: weekend Friday-range volatility breakouts on a high-beta alt (SOL) at 1H produce a catastrophic, fee-bled loss (PF 0.76, Sharpe -1.69, -79.8% total, 84% DD, 6 of 7 years negative) because thin-liquidity weekend breakouts are false signals that whipsaw rather than continue, and the high trade frequency lets commissions/impact (8%+ of gross) dominate — calendar-gated breakout fading would be the inverse, but directional weekend breakouts have no fee-surviving edge on a volatile alt.

Verification failed (Layer 2 — synthetic scenarios): Parameters used: ['sl_atr', 'tp_atr', 'trail_atr', 'atr_period', 'min_notional', 'position_pct', 'consol_end_hour', 'consol_start_hour', 'breakout_buffer_pct'] Check that __init__ sets all attributes from self.parameters.get(). - steady_uptrend: TypeError: SolWeekendVolatilityRegimeBreakoutLS1H._dt() takes 1 positional argument but 2 were given (bar timestamp: 1735690500000) - steady_downtrend: TypeError: SolWeekendVolatilityRegimeBreakoutLS1H._dt() takes 1 positional argument but 2 were given (bar timestamp: 1735690500000) - flat_ranging: TypeError: SolWeekendVolatilityRegimeBreakoutLS1H._dt() takes 1 positional argument but 2 were given (bar timestamp: 1735690500000) - volatility_spike: TypeError: SolWeekendVolatilityRegimeBreakoutLS1H._dt() takes 1 positional argument but 2 were given (bar timestamp: 1735690500000) - zero_volume: TypeError: SolWeekendVolatilityRegimeBreakoutLS1H._dt() takes 1 positional argument but 2 were given (bar timestamp: 1735690500000) - price_gap: TypeError: SolWeekendVolatilityRegimeBreakoutLS1H._dt() takes 1 positional argument but 2 were given (bar timestamp: 1735690500000)