Disclaimer: Built from the current Obsidian Flow codebase and organized by shared logic, not redundant tool-by-tool repetition. Use this as your clean starting framework, then fine-tune to your instrument, session, and preferred aggression threshold.
These settings are not meant to be followed blindly.
They serve as a structured baseline — a foundation built from typical liquidity behavior across instruments.
True edge comes from your ability to observe, adapt, and refine.
The tools reveal the behavior.
You decide how to act on it.
Many of your tools share the same underlying logic families: hidden liquidity, iceberg detection, pulling and stacking, decay, and order-book persistence. Instead of repeating nearly identical settings under every product, this page groups them into practical operating buckets so users can tune faster and understand what actually matters.
Use these as starting points. The numbers below are intentionally conservative and practical. They are designed to get a trader close enough to start reading behavior immediately, then tighten or loosen sensitivity based on instrument liquidity and session volatility.
Bid / Ask Dominance in the current code exposes Smoothing Period, EMA usage, and Bid/Ask data usage — not an ATR-length input. Hidden Liquidity Bias and Iceberg Detector share the closest overlap on hidden-size logic, while Liquidity Behavior Engine and Pulling / Stacking Net Meter share the pulling / stacking family.
These profiles define how aggressively you should start. ES stays closest to defaults because it is the deepest benchmark contract in this stack. NQ usually needs more filtering. 6J often benefits from lower thresholding. BTC needs enough filtering to avoid overreacting to bursty movement.
Use this as the baseline profile. Most code defaults land here naturally. Ideal for the “standard” sensitivity pack across the suite.
More violent and less forgiving than ES. Raise event thresholds and keep filters tighter so the tools only fire when intent is clearer.
Usually cleaner but thinner. Lower hidden-liquidity and DOM event thresholds so legitimate activity is not ignored.
Use stronger filtering than 6J but not as restrictive as NQ. Let the tools breathe enough to catch true bursts without overfiring.
This cluster governs Iceberg Detector Lite, Iceberg Detector Pro+, and the hidden-size side of Hidden Liquidity Bias. The goal is simple: catch real hidden interest without letting every random refresh or small DOM twitch masquerade as absorption.
| Setting | ES | NQ | 6J | BTC |
|---|---|---|---|---|
| Lite — Min Traded Volume To Detect | 100 | 140 | 40 | 70 |
| Lite — Iceberg Ratio Threshold | 3.0 | 3.5 | 2.0 | 2.5 |
| Lite — Break Ticks | 1 | 1 | 1 | 2 |
| Pro+ — Min Traded Volume To Detect | 50 | 70 | 20 | 35 |
| Pro+ — Iceberg Ratio Threshold | 1.0 | 1.2 | 1.0 | 1.3 |
| Pro+ — Min Block Order DOM Size | 200 | 300 | 80 | 120 |
| Pro+ — Min Block Order Traded Volume | 50 | 80 | 25 | 40 |
| Pro+ — Block Break Ticks | 2 | 2 | 2 | 3 |
| Pro+ — Block Collapse Threshold | 5 | 8 | 3 | 5 |
| HLB — Block Threshold | 50 | 70 | 20 | 25 |
| HLB — Iceberg Time Window (ms) | 800 | 700 | 1000 | 900 |
| HLB — Iceberg Max Clip Size | 20 | 25 | 10 | 12 |
| HLB — Iceberg Min Clips | 3 | 3 | 3 | 3 |
| HLB — Iceberg Min Total | 40 | 60 | 20 | 25 |
Stay close to defaults. ES is deep enough that false positives usually come from too much relaxation, not from thresholds being too strict.
Push thresholds up first, especially block and iceberg size. NQ will tempt you into reading noise as intent if you tune it too loose.
Thinner markets often require lower minimum size but a touch more patience around persistence and follow-through. Lower size does not mean lower standards.
This cluster controls how aggressively your DOM-based tools react to pulling, stacking, spoof behavior, and vacuum conditions. Use this section to decide whether you want a faster tape read or a calmer structural read.
| Setting | ES | NQ | 6J | BTC |
|---|---|---|---|---|
| LBE — Aggressive Bid / Ask Stack Threshold | 50 / 50 | 70 / 70 | 25 / 25 | 40 / 40 |
| LBE — Spoof Stack / Pull Threshold | 80 / 60 | 120 / 90 | 35 / 25 | 55 / 40 |
| LBE — Spoof Time Window (ms) | 1500 | 1200 | 1800 | 1400 |
| LBE — Vacuum Pull Threshold | 80 | 110 | 30 | 45 |
| LBE — Vacuum Max Age (ms) | 3000 | 2200 | 3500 | 2800 |
| LBE — Min Abs Delta To Draw | 10 | 15 | 5 | 8 |
| LBE — Reset Tolerance | 2500 | 2200 | 3000 | 2500 |
| Net Meter — Levels To Aggregate | 5 | 4 | 6 | 5 |
| Net Meter — Weighting Mode | Near-Weighted | Near-Weighted | Equal or Near | Near-Weighted |
| Net Meter — Decay Time (ms) | 2000 | 1500 | 2500 | 1800 |
| Net Meter — Refresh Interval (ms) | 33 | 33 | 50 | 33 |
| Net Meter — Impulse Multiplier | 1.0 | 0.9 | 1.15 | 1.0 |
| Pressure — Decay Half-Life (sec) | 60 | 45 | 75 | 50 |
Practical rule: if your DOM tools feel jumpy, raise thresholds before you lengthen everything. If they feel dead, lower event thresholds first, then consider slightly longer persistence only after that.
These are your chart-based readout tools. Their job is not to spam entries. Their job is to make aggression and hidden intent legible enough that the right zones become easier to trust.
| Setting | ES | NQ | 6J | BTC |
|---|---|---|---|---|
| Bid / Ask Dominance — Smoothing Period | 14 | 18 | 10 | 16 |
| Bid / Ask Dominance — Use EMA Smoothing | On | On | On | On |
| Bid / Ask Dominance — Use Bid/Ask When Available | On | On | On | On |
| HLB — Response Weight | 0.30 | 0.35 | 0.25 | 0.30 |
| HLB — Location Bias Strength | 1.00 | 1.15 | 0.90 | 1.00 |
| HLB — Warn / High Threshold | 0.50 / 0.70 | 0.55 / 0.75 | 0.45 / 0.65 | 0.50 / 0.70 |
| HLB — ATR Period | 14 | 14 | 14 | 14 |
| HLB — ATR Multiplier | 0.70 | 0.85 | 0.60 | 0.75 |
| HLB — Range Lookback Bars | 20 | 18 | 24 | 20 |
| HLB — Max Range Ticks | 24 | 32 | 16 | 30 |
| HLB — Breakout Confirm Ticks / Bars | 2 / 2 | 3 / 2 | 1 / 2 | 3 / 2 |
Initial Balance is less about “sensitivity” and more about consistent structure. The current code defaults to a 09:30–10:30 IB window, shows the core levels and extensions, and keeps the styling simple. For ES and NQ, that default is your clean starting point.
| Setting | ES | NQ | 6J | BTC |
|---|---|---|---|---|
| IB Window | 09:30–10:30 | 09:30–10:30 | 09:30–10:30 to start | Use a chosen NY anchor window |
| Show IB High / Low / Mid | On | On | On | On |
| Show Extensions | On | On | On | On |
| Show Half Delta Levels | On | On | Optional | Optional |
| Keep Previous IB Levels | On | On | On | Only if using a fixed session framework |
| Show Extensions Only After Touch | On | On | On | On |
Best use: keep Initial Balance as your structural anchor. Let your DOM tools and chart oscillators refine the interaction at or around those levels instead of treating IB as a standalone trigger.
ES = baseline. Start there mentally even if you primarily trade something else. It helps you understand what “normal” sensitivity feels like.
NQ needs stricter event filtering. 6J needs more forgiveness on size. BTC needs balance: not too loose, not too sterile.
Do not optimize every setting at once. Lock one profile, trade it, then adjust only the family that is obviously too loud or too quiet.