Video summary
I ALWAYS WAIT FOR THIS SIGNAL BEFORE ENTERING TRADES
Main summary
Key takeaways
Finance-Focused Summary (Markets, Strategy, Risk, Performance)
- The presenter’s core critique: a common trader mistake is trading “signals” (e.g., candlestick patterns, fair value gaps, order blocks, market structure shifts) without higher-timeframe context.
- Core principle: wait for lower-timeframe confirmation to match the higher-timeframe trend—for example, when the higher timeframe is bearish, expect behavior consistent with lower lows/lower highs (and the opposite for bullish conditions).
- Higher timeframe framing: the higher timeframe is described as the domain where “smart money” / institutions act, meaning it controls (or dominates) what happens on lower timeframes.
Market Microstructure Logic
The approach repeatedly emphasizes that price is “engineered” to grab liquidity:
- Bearish scenario: sellers target lows
- Bullish scenario: buyers target highs
Decision Framework (Avoid Contradictory Trades)
- If the higher timeframe is bearish:
- avoid buying lower-timeframe setups showing bullish momentum.
- If the higher timeframe is bullish:
- avoid selling lower-timeframe setups that contradict price action until alignment occurs.
Risk Management Philosophy
- Prefer multiple smaller risks aligned with the dominant higher timeframe instead of taking big risk against it.
- The presenter highlights that trading can’t produce “certainty,” so the goal is controlled outcomes rather than perfect prediction.
- Stop-loss placement is discussed in the live example, with an emphasis on keeping losses controlled (optionally allowing more patience).
Live Trade Execution Example (Timing / Metrics)
- The presenter discusses entering a sell after watching candlestick behavior/confirmation.
- Stop-loss placement: described as “around this high” (no exact numeric level provided).
- Targets / realized movement referenced:
- about 50 pips initially mentioned
- later about 80 pips referenced as expected/desired
- Performance/consistency claim:
- “not a losing day… in like 3 weeks”
- referenced roughly as ~2–3 weeks since a holiday (as phrased)
Instruments / Asset Classes Mentioned
- Gold
- Explicit statement: “I trade on the 1 minute time frame… because gold is very liquid”
- No specific ticker was provided (e.g., no GLD / XAUUSD mentioned).
Methodology / Step-by-Step Framework
- Start with the higher timeframe (daily)
- Determine directional bias (e.g., sellers dominating; look for lower lows/lower highs).
- Map key levels on the intermediate timeframe (4H)
- Identify crucial areas where price could turn or continue.
- Use execution timeframe (hourly / 1-minute) only after alignment
- Look for lower-timeframe price action to match the higher-timeframe “story.”
- Confirm using “first move” logic
- The market should make the first move.
- Avoid entering just because price touched a “premium” level (e.g., selling at fair value gaps immediately, described as “sniper entry” behavior).
- Execute with defined risk controls
- Place stop-loss near a relevant swing/level (described as around a recent high in the sell example).
- Let the trade run when price confirms, aiming for larger downside movement (e.g., 50–80 pips cited).
- Avoid setups that contradict the higher timeframe
- Even if the pattern looks “perfect,” skip trades that reduce odds by fighting the higher-timeframe bias.
Key Numbers / Explicit Recommendations
Numbers (Live Example)
- Pip targets/moves:
- ~50 pips
- ~80 pips
- Consistency claim:
- “not a losing day” for approximately 3 weeks
- with a ~2-week holiday reference (as phrased)
Explicit Recommendations
“Stop trying to predict. Stop trying to be first. Start waiting for confirmation.”
- Don’t trade against the higher timeframe.
- Wait for alignment between higher and lower timeframes to improve probability.
Disclaimers / Disclosures
- No formal “not financial advice” disclaimer was present in the provided subtitles.
Presenters / Sources
- The subtitles reference one main presenter throughout.
- No presenter name or external source/ticker provider was mentioned.