#FamilyOfficeCrypto #TrendingTopic #BTC走势分析 #Square e
Most losses come from buying the first green candle through resistance or shorting the first red under support. The 3‑Candle Test forces patience and confirms whether a break has real backing before committing risk.
Why this works
Real breaks sustain above/below the level for multiple closes and accept pullbacks.
Liquidity hunts print long wicks and snap back within 1–2 candles—this filter keeps capital off those traps.
How to run the 3‑Candle Test
Step 1 — Mark the line in the sand
Use last week’s high/low (WLH/WLL) or a well‑defined daily range edge. Draw it precisely.
Step 2 — Demand three closes
Candle 1: Break and close beyond the level.
Candle 2: Stay beyond the level with similar or rising volume.
Candle 3: Either continue or print a controlled pullback that closes beyond the level.
If any candle closes back inside the prior range, the test fails—no trade.
Step 3 — Take only the retest entry
After the third close, wait for a “Close → Retest → Hold” of the broken level on the execution timeframe (1h/4h intraday, daily for swing).
Enter on the hold close. Stop goes below the retest low (long) or above retest high (short).
Targets and management
TP1: Measured move equal to the height of the prior range.
TP2: Next weekly level or prior supply/demand.
One add allowed only after a new higher‑low/lower‑high forms above/below the level.
If price re‑enters the broken level and closes inside, exit to core—trend failed.
Where it shines
Range markets with frequent fakeouts.
Listing/TGE weeks and headline sessions where wicks are common.
Alt rotations: confirms leaders and filters noisy laggards.
Risk rules
≤1% portfolio risk/day; 0.25% per position if running four names.
Skip if funding spikes hard against the direction before the retest—crowded trade risk.
No widening stops; size down if the structure stop is wide.
Fast checklist (copy/paste)
Level: WLH/WLL/Range Edge: __
Three consecutive closes beyond level? Y/N
Retest and hold confirmed? Y/N
Entry __ | Stop __ | TP1 __ | TP2 __
Add trigger __ | Invalidation (back inside) __