Best Swing Failure Pattern (SFP) indicator settings for Bitcoin scalping

Core Principles of SFP in Bitcoin Scalping

1. Swing Failure Pattern relies on liquidity sweeps and structural rejection at key swing extremes.

2. Bitcoin’s volatility demands strict alignment with higher timeframe swing points—only HTF-defined HH/LL levels qualify as valid SFP anchors.

3. A valid SFP must occur within 0.8%–1.5% of a confirmed HTF liquidity pool, measured from the nearest institutional mitigation block (MiB).

4. The pattern loses validity if price retraces more than 61.8% of the prior swing before forming the failure candle.

5. Volume divergence must be present: the failure candle’s volume must be ≥1.3× the 5-candle average, confirming institutional participation.

Optimal Indicator Configuration for BTC/USDT

1. Use a 15-minute chart as the primary scalping timeframe, but only after validating the swing structure on the 2-hour chart.

2. Apply the Liquidity Sweep Detector v3.2 with sensitivity set to “High” and sweep radius fixed at 0.45% of current BTC price.

3. Overlay the Order Block Strength Index (OBSI) with threshold value 72—only OBs scoring above this level generate actionable SFP entries.

4. Disable all smoothing filters; raw tick-volume feed must drive the confirmation logic to avoid latency-induced false sweeps.

5. Set the MITIGATION BLOCK (MiB) detection window to 12 candles—this captures the precise exhaustion zone where SFP reversals most frequently ignite.

Price Action Filters for Signal Validation

1. The failure candle must close beyond the prior swing extreme by ≤0.3%, then reverse and close inside the prior swing range.

2. No wick longer than 2.1× the candle body is permitted on the failure candle—excessive wicks indicate unconfirmed rejection.

3. The candle following the failure must print a minimum 0.6% directional move in the reversal direction within 90 seconds of close.

4. Consecutive SFP attempts within the same liquidity zone are invalid after the third occurrence—market absorption capacity is exhausted.

5. SFP signals coinciding with BTC funding rate > 0.012% or

Risk Management Parameters

1. Entry occurs at the midpoint of the failure candle’s body—not at open or close—to avoid slippage traps in volatile BTC microstructures.

2. Stop-loss is placed at the far edge of the swept liquidity pool, never inside the MiB zone.

3. Take-profit targets align precisely with the nearest OB mid-price level—no extension beyond that point is permitted.

4. Position size is capped at 0.8% of account equity per SFP trade, regardless of perceived signal strength.

5. If two SFP setups appear within 3 minutes on separate BTC perpetual order books (Binance + Bybit), only the one with higher OBSI score and tighter sweep radius is executed.

Frequently Asked Questions

Q1: Does SFP work during Bitcoin halving weeks?Yes—but only when applied to HTF-defined swings formed at least 72 hours prior to the halving timestamp. Signals generated within 48 hours before or after halving are excluded due to protocol-layer noise.

Q2: Can SFP be automated using Pine Script v5?No. Pine Script lacks access to real-time tick-volume depth and cannot detect liquidity sweeps with sub-50ms precision. Only native C++ or Rust-based execution engines meet SFP timing requirements.

Q3: Is SFP valid on spot BTC/USD pairs?No. Spot markets lack consistent funding-driven liquidity sweeps. SFP requires perpetual contract mechanics—including open interest shifts and delta-neutral hedging flows—to manifest reliably.

Q4: What happens if Binance and Bybit show conflicting SFP signals simultaneously?The signal with higher observed liquidity sweep volume across both order books’ top 3 price levels is retained. Conflicts unresolved within 11 seconds are discarded—no fallback logic applies.