After hitting targets for Wave 5, we are now in an ABC correction. Plotted are two possible pathways for the retrace already under way. Thus far the retrace looks to be of average "energy" of consolidation.
Plotted are the 3 "Impulses" which caused the 4 wave rally. Next we had an corrective Impulse in Red pushing downward. In ABC corrections, wave C may or may not have a new Impulse.
I think we are in wave C now, but still a bounce for higher B is possible. $ 8100-8124 would be the ideal zone from which to see a strong bounce. $ 8018-8041 is crucial support that is best not even tested, let alone breach.
Of course, I have had total FAILS on some ideas too, not going to pretend. But all of my plots show PRECISE entries, TIGHT stops, and EXACT targets. Precision is the way of the Fib. Almost every turn happens at a Fib Line.
Note
Ping perfect kiss of the top boundary of support zone
Note
Ping again. Only on the bottom boundary of first support zone I do NOT think this zone will hold, but pings on both boundaries makes it more likely the NEXT zone might bounce it.
.
Note
I guess we can rule out the 'alternative' ABC with a higher B. I have removed that path, and the remaining path still seems quite valid and quite possible
.
Note
turning into a decent BOUNCE thus far Still under the influence of the Red Fib pushing downward... I will be quite surprised but pleased if this zone actually holds and we get new highs from here ...
.
Note
Nice, support still holding and the bounce still growing
Zooming in Notice the exact bounce on the confluence of fibs (red 5.236, grey -0.236). And the overall action of walking up each fib line.
Note
wow, so that first support held, and has bounced it back to the original resistance that resistance "should" break this time. If not, bulls are nowhere near as strong as this bounce implies.....
The information and publications are not meant to be, and do not constitute, financial, investment, trading, or other types of advice or recommendations supplied or endorsed by TradingView. Read more in the Terms of Use.