Layer 4 · Method

Indicators & Scanners

Every tool in this layer exists to do one specific thing the human eye gets wrong or slow — find a level that's pixel-precise, scan 60 charts at once, or stop you mistaking a sweep for a hold. None of them tell you what to do; they delete the work that wastes your eyes.

The actual tools: Hold Levels, Break/Origin Detector, Native Candles & HTF Closes, the Bias Scanner, Origin Bot in Discord, and the Fib-Lab Dashboard. Settings explained, with the trade-offs that aren't in the docs.

FibLab indicator stack on a single chart — hold lines, break/origin lines, native candles, bias scanner strip, origin bot. EVERYTHING ON · THE FULL INDICATOR STACK 1-4H 6-12H 1D+ Hold Levels Break / Origin Native Candles Bias Scanner Origin Bot /close-origins SOL Dashboard filter-by-price HTF Closes ⏱ 22m to 4H one chart, every layer · what each line means lives in the chapters below
The full indicator stack on one chart — what each line means is in the chapters below.

The whole layer in 8 lines

Hold LevelsMin move 0.4%. Refinements ON for planning, OFF for alerts. Break/Origin DetectorShow pure + non-pure. Range hit origins ON. ATR proximity tuned for your TF. Native CandlesPeriod Length on daily = N-day virtual candle. 604, 134, 347 are common. HTF ClosesFractal countdowns essential for scalping. Native exchange closes > TV closes. Bias Scanner1-4H low % = lots of resistance being built → expect rejection. Origin Bot/close-origins TOKEN, /big-close-origins, /TV close-origins TOTALS. Green = untouched. DashboardFilter-by-price = instant multi-TF confluence check. Singularity filterSymbol → Native → Break/Origin → Widgets. OFF non-pure, ON singularity.

The 6-tool suite at a glance

ToolWhat it doesWhat it does NOT doSetting that mattersFailure modePairs with
Hold LevelsMarks every body engulfment near priceTell you which one to tradeMin-move %, refinements toggleRefinements ON during alerts → noiseHTF Closes for context
Break/Origin DetectorPixel-marks origins + tags pure/non-pureDecide if proximity is acceptableATR proximity bandATR too tight = no alerts; too wide = constant noiseBias Scanner
Native Candles + HTF ClosesPaints pending HTF close on your TFPredict where the close landsTF mapping, custom periodsCustom-period TF mismatch silently breaks readsTime & Levels rule
Bias ScannerOne number per TF bracket across the marketTell you which token to tradeToken universe, TF bracketsReading the number as a signal, not as biasOrigin Bot for entries
Origin Bot v2Discord pings when an origin actually printsConfirm the trade is takeable/origin command flagsActing on the alert without your own thesisDetector for confirmation
Fib-Lab DashboardMulti-token table + heatmap + chart viewerReplace the chart in TradingViewFilter cohort, refresh cadenceTreating the dashboard as the chartEverything above
Chapter 4.1
Hold Levels Indicator
▶

Eye-balling every body engulfment across six timeframes is the single slowest part of FibLab. Hold Levels does the scan; you spend the saved time deciding which level to trade.

What it does

Highlights all hold levels (body engulfments) and optionally wick engulfments on every relevant TF near price. Source of truth for the ladder rungs.

Key settings

The ones you actually tune
  • Minimum move: default 0.4%. Skips holds too small to overcome fees. Anything under ~0.4% is noise for most traders.
  • Refinement search: Nearest pending below / Nearest pending above. Returns sub-TF levels inside a parent hold for greedy entries.
  • Engulfment type: body-only, wick-only, or both. Default body. Use wick-only for pure range trading with the range fibs.
  • Fib levels (range fibs): wick 0, wick 1, wick 1.618, wick 2.618, wick 4.618. See Layer 3.4.
  • Status filters: pending / active / completed / revisited / hard-closed-and-polarized. Toggle by what you're hunting.
  • Range filter (proximity): default 2. Increase to see more levels farther from price; decrease for cleaner view.
  • Cosmetics: label size, padding, line color, position.

The alerting rule that matters

Refinements ON for trade planning, OFF for alerts
Keep refinement search OFF when setting alerts. Every level on every sub-TF triggers separately — your phone will buzz constantly. Turn refinements ON only when you're actively planning the entry on a specific level.

The TradingView reality check

"TradingView just can't keep up. On lower TFs the indicator can crash. Just toggle it off and on."
— Syndotc · Video 01

Indicator stays data-rich, not dumbed-down. Accept occasional crashes — refresh and continue.

Hold Levels is the eye-replacement layer — what your eye does in 60 minutes, the indicator does in 60 milliseconds.

Chapter 4.2
Break / Origin Detector
▶

An origin is the precise pixel where a break reversed — get the candle wrong and your stop is in the wrong place. The detector marks the exact wick, so the highest-confidence trade in FibLab isn't a guess.

What it does

Shows all break levels and origin levels with proximity alerts and ATR-based notifications. Flags pure vs non-pure. Tags BUT levels and range hit origins.

Key settings

The dials
  • Show pure / non-pure: keep BOTH on. Non-pure gets flagged for higher-TF investigation.
  • Status filters: touched, untouched, broken-retested. Keep all on.
  • Range hit origins: toggle on. Useful for catching "very fast pumps" before they happen.
  • Alerts: pure, non-pure, proximity, broken/retested, created.
  • ATR proximity: sets alert distance band. Tune carefully (see warning below).
  • Range filter: Dynamic Unbroken Count (default 8), or Manual Price Range, or Distance from Previous Close. Defaults are good.
  • Cosmetics: label size, padding, transparency, anchors.

Proximity alert workflow

Pick 5-10 tokens. Set proximity alerts on 4H/8H/12H/Daily. Get notified whenever a level is created, broken, touched, or in proximity. Eliminates manual chart scanning.

ATR proximity caveat
Set too low → tight band, you won't get warning before fast moves.
Set too high → noise, alerts fire when nothing actionable is happening.
Test in your timezone with your assets.

The non-pure trap

Single-candle hard close on a non-pure level ≠ break. True level lives on a higher TF — cross-reference with the dashboard's price filter or OTA Scanner.

The detector marks the pixel; you pick the trade. Don't trust the alert without your own thesis behind it.

Chapter 4.3
Native Candles & HTF Closes
▶

Reacting to a 4H close is too late; front-running it is too early. These two indicators paint the higher-TF close on the timeframe you're already watching, so you decide before the candle prints, not after.

Two indicators that pair

  • HTF Closes: table of upcoming TradingView native and exchange-native time-frame closes. Yesterday/tomorrow, fractal countdowns, market sessions, exchange-native daily anchors.
  • Native Candles: virtual high-time-frame candle painted on your chart at any custom period (604 days, 7 days, 134 days, etc.).

HTF Closes settings

What to enable
  • Fractal countdowns — when the next 1m / 3m / 5m / 72m / 134m / etc. close happens.
  • Market sessions — NY, London, Asia open/close.
  • Native exchange closes — often differ from TradingView's daily anchor. Critical.
  • Max rows in the table.
  • Position (top-right, bottom-left, etc.) and background opacity.

Why fractal countdowns matter for scalping

Trading the 1H, but a 4H candle closes in 22 minutes — that close shifts every level in the 1-4H bracket. Knowing exactly when lets you wait for it. (Fractal mechanic: see Layer 2.3.)

Native Candles settings

The unique controls
  • Period length: any number. 604 on a daily chart = a virtual 604-day candle. On weekly = 604 weeks. On monthly = 604 months.
  • Auto trends: built-in auto-trend detection.
  • Anchor mode: "start of bar" vs "center of bar". Matters for time-arrayed trends — try both, pick what's cleaner on your TF.
  • Wicks on/off: wicks visible let you snap trend lines exactly to high/low. Turn bodies off if the chart feels too noisy.

The 604-day candle revelation

SOL · Video 03 — long-term structure invisible on TV
Set Period Length: 604 on daily chart
Reveals: one giant 604-day candle
Top of the 604-day candle: exact rejection point
Price tapped it → dumped. Spotted in seconds. Invisible on standard TV daily.

A 1H view that paints the pending 4H close lets you trade before the candle prints, not after.

Chapter 4.4
Bias Scanner / Origin Stats
▶

Reading 60 charts to answer "is the market red or green right now" costs an hour and several wrong calls. The Bias Scanner reduces that question to one number per TF bracket — the macro frame every individual trade lives inside.

The market-wide brain

Real-time scanner across ~540 tokens by TF bracket. Shows where the whole market is positioned before the next major close.

The four metrics

What each tells you
  • Origin Potential Bias: resistance vs support being created RIGHT NOW. Low number on 1-4H = lots of resistance building → high probability of rejection if price pushes up.
  • Broken Level Bias: balance of already-broken levels waiting to be retested. >50% downside = more magnets below. Tells you where liquidity sits.
  • Upside Break Bias: predicted candle-close direction — bias to break support down or break resistance up.
  • % Bullish Origins: when very low → market is building far more bearish than bullish structure.

The three time-frame buckets

  • 1-4 hour — short-term tactical. Most actionable for day traders.
  • 6-12 hour — bridge between intraday and swing.
  • 1-day plus — strategic / swing.

The most powerful read — bucket disagreement

Lower TFs breaking down while higher TFs build support → short-term breakdown into HTF support, then bounce.

Real prediction example · Video 05
Heading into daily close:
1-4H upside bias: 17% (massive resistance being built)
6-12H: ~50%+ bullish
Daily+: ~50%+ bullish

Read: short-term retrace into support, then bounce, then rejection again
"You go down, you go up, you go down, you go up." Played out exactly.

When to check

Before 4H and Daily closes — every level in the bracket flips at close. Clearest signal heading into them.

One number per TF bracket. The macro answer to "what is the market doing right now" without 60 charts of work.

Chapter 4.5
Origin Bot & Alert Scanner v2
▶

You can't watch every TF on every coin in a 540-token universe. The Bot watches them for you and pings only when an origin actually prints — turning a 24/7 vigil into a notification.

Origin Bot — Discord scanner

Discord bot returning S/R levels near price for any tracked token. ~540+ tokens, plus forex and stocks. CSV Data Members only. Updated in V62 (2026) — the v1 commands (/close-origins, /big-close-origins) were consolidated into a single origin command with flags.

Commands (v2 consolidated syntax)
  • /origin SOL — default: 6 above + 6 below S/R levels for SOL.
  • /origin SOL all — every time frame, top 6 each side.
  • /origin SOL big — 1-day-plus levels only (HTF trades).
  • /origin SOL pot — include "potential" origins (unconfirmed; level forming but not yet validated).
  • /origin TOTALS TV — total market cap version (the TV qualifier).
  • /origin S:TSLA — stocks (S: prefix).
  • /origin C:EURUSD — forex / commodities (C: prefix).

Rate limit: 1 request per 15 seconds. Source: V62 (qMf_DjM-rr0).

Output color coding

  • Green — untouched (highest probability).
  • White — touched but not broken.
  • Red — broken (retest target).

Origin Trading Alert Scanner v2

Watchdog scanner of all 540+ tokens. Posts in Discord by TF whenever a break converts to origin. Triggers every ~10 min, only on candle close.

What each post tells you

  • Token, bullish/bearish
  • Origin-touched / origin-untouched
  • Price
  • Golden cross / death cross dates
  • Relative volume status (rising / falling)
  • Highest TF the level exists on

Reading the alerts

Confluence stack
  • Bullish + golden cross + rising volume + first-touch = ideal long.
  • Bearish + death cross + first-touch = ideal short.
  • First-touch origin = highest-probability scalp.
  • Already-touched origin = still tradable but use other confluences.
"If you can compound your money by 1% a day, you won't need to worry about working anymore over a decent period of time, and this is the kind of thing that can do that for you."
— Syndotc · Video 27

The Bot is your overnight self — trades nothing, but pings when the trade you'd want to take has actually printed.

Chapter 4.6
Fib-Lab Dashboard
▶

Every other tool in Layer 4 answers one question. The Dashboard is the surface where their answers stack — the single screen that tells you "what is the market doing right now," in one glance.

The flagship

Web dashboard: multi-token break/origin/hold table, in-house liquidity heatmap, recent-updates feed, chart viewer. Center of the FibLab toolset.

Main views

What's on the dashboard
  • Liquidity heatmap — in-house built. Symbol selector, TF selector (1d/7d/14d/30d). Cascade triggers + liquidity magnets shown.
  • Tokens dropdown — BTC, ETH, SOL pre-loaded. Top-10 voted tokens added.
  • Holds & Breaks tab — tabular view of all levels.
  • Break / Origin tab — same data, filtered.
  • Native Time-Frames — non-standard periods (134-day, 347-day, 694-day, etc.).
  • Widgets / Table Filters — filter by price, status, singularity.
  • Recent Updates feed — live alerts on level activity.
  • Chart Viewer — one-click into TradingView for the chart.

Filter by price — the killer feature

Type 109.4 → lists every TF that level exists on. Multi-TF agreement = strong reaction zone.

Singularity filter — the rare violent levels

How to find singularities
  1. Symbol → Native → Break/Origin → Widgets → Table Filters.
  2. Turn OFF: everything except Origin Touched and Origin Untouched.
  3. Turn OFF: Non-Pure ranges.
  4. Turn ON: Singularity filter.
  5. Result: maybe a half-dozen levels per token. The most violent ones.

Daily routine

"Make this part of your sort of daily routine. Check it a couple times a day. So if you come in here, it just tells you what's changing."
— Syndotc · Video 12
  1. Open dashboard.
  2. Check Recent Updates for major level activity.
  3. Pick a level on a token. Filter by price → see all TFs it exists on.
  4. Click chart icon to verify on chart.

Every other tool answers one question. The Dashboard is where their answers stack into a single screen verdict.

Open questions

No reveal. No answer key. Carry them or open a chart.

  • Hold Levels uses body-engulfment as the trigger. Would wick-engulfment work as a parallel indicator, or is body-only structurally required?
  • Bias Scanner reports origin hit-rate. At what historical hit-rate does the indicator stop being information and start being a contrarian signal?

Edge-Case Files

Charts that look textbook-correct and failed. Diagnose first, reveal second.

Case 04

The Origin Bot ping that fired five seconds late

stress-tests: ATR proximity setting + indicator-as-truth fallacy
Diagnose You set Break/Origin Detector ATR proximity to 0.5× — you wanted "only the closest setups." For three days the bot was silent. On day four it pinged once, you took the trade, and the level was already 0.4 ATR past your fill before you got in. What broke?
Diagnosis

0.5× ATR is too tight for the alert layer — by the time price is within that band, you're chasing the move, not catching it. The indicator did exactly what you asked. The ask was wrong.

Rule restored: ATR proximity is a parameter, not a truth. Set it to the band where you'd actually want a notification — typically 1.5–2.5× ATR for entries, looser still for "watch list" alerts. Tight ATR = late ping = always chasing.