Strategies
On-Chain Venue Flow Migration Fade: Short a Hyperliquid Alt Perp, BTC-Beta-Hedged, for a Fixed 5 Days After an Up-Day on Which Hyperliquid's Share of Its Perp Volume (HL vs Binance USD-M) Spikes >=2.5 Sigma (25 HL alts + BTC hedge, Binance volume signal-only, 1-DAY, market-neutral event panel, flat most of the time)
Outcome: Backtesting
HlVenueFlowMigrationFadeBtcHedged
On-Chain Venue Flow Migration Fade: Short a Hyperliquid Alt Perp, BTC-Beta-Hedged, for a Fixed 5 Days After an Up-Day on Which Hyperliquid's Share of Its Perp Volume (HL vs Binance USD-M) Spikes >=2.5 Sigma (25 HL alts…
Hypothesis
Fills under-represented buckets: Hyperliquid (13.3% vs >=20% target), cross-venue (10% vs >=15%; Binance volume is a signal-only leg), long-short/market-neutral (24% vs long-only 76%). Avoids BTC as the traded series (BTC is only the hedge). New mechanism (venue flow migration), not a candle pattern, carry, or a re-run of NR7/absorption. Event-triggered and flat most of the time, per L231/L224. The short arm is pre-registered on these exact names per L230; the event count inside the full-overlap span is pre-registered per L237.
Implementation
Verification Results
Optionally add a check so that the summed BTC target notional (`_btc_target() * btc_close`) stays at or below 1.0 x equity, and skip an event that would push it over. This is a sizing guard, not a rule change.
Risk-control pre-screen (L239). Branch (a): the stop is a 20% alt stop on a leg worth 20% of equity, so the loss at the stop is about 4% of equity, above the 2% limit. A gap through the stop could lose more. Branch (b): the exits are signal/time based, but the netted BTC hedge is the sum of beta x alt notional over the live events. The only bound on it is the gross cap `if gross + add > cap` (cap = 0.9 x equity x leverage = 180% of equity). Example: three events with beta near 2 give 60% alt notional plus 120% BTC, which passes the gross cap and leaves one BTC position at about 120% of equity, above the 100% single-position limit. pair_notional_pct, leverage, max_concurrent and the beta clip are all fixed by the research contract, so implementing them is faithful and not a defect here. Risk review may still reject the strategy.
Acceptable as written. A reduce-only BTC trim could be submitted from on_order_filled when the reduce-only BUY stop fills, if tighter hedging is wanted.
When the 20% intrabar alt stop fires, that event's BTC hedge stays open until the next daily close. Step 1 then drops the event and _sync_hedge reduces the hedge. For up to one day the book holds net long BTC. The strategy description discloses this, and it only happens after a +20% alt move.
No change needed.
The hypothesis title says 25 alts, but research_contract.instruments lists 20 HL alts. The code uses exactly those 20 (COINS), with BTC as the hedge and Binance USD-M bars for the signal only. The contract is the specification, so this is not a mismatch. It is noted for the analyst because the pre-study event counts may have come from the larger universe.
The pre-study's -2.6% hedged 5-day figure is gross and entered at the signal close. About 0.6-0.8% of it is the unconditional underperformance of alts against BTC over 2023-26, which is a beta/regime drift and not this signal, so the incremental effect is about -1.9%. Per-name results are mixed: DOGE, ARB and DOT are slightly positive. The pre-study chose the z>=2.5 / 5-day shape on the same history the optimizer will search (z 2.0-3.0, hold 3-7, lookback 30-120). The analyst should compare the result with an up-day-only control at the frozen rule, and check that the profit is not concentrated in 2024 (-4.9% that year against -0.9% in 2025).
Iteration History
Risk-control pre-screen. Branch (a): the stop is a 20% alt stop on a leg worth 20% of equity, so the loss at the stop is about 4% of equity, above the 2% limit. A gap through the stop could lose more. Branch (b): the exits are signal/time based, but the netted BTC hedge is the sum of beta x alt notional over the live events. The only bound on it is the gross cap `if gross + add > cap` (cap = 0.9 x equity x leverage = 180% of equity). Example: three events with beta near 2 give 60% alt notional plus 120% BTC, which passes the gross cap and leaves one BTC position at about 120% of equity, above the 100% single-position limit. pair_notional_pct, leverage, max_concurrent and the beta clip are all fixed by the research contract, so implementing them is faithful and not a defect here. Risk review may still reject the strategy.
Backtest and paper results are hypothetical. Trading involves risk of loss.