The push from 60k to 64k was more than expected. But sat tight. Slept like a baby, up every hour crying. Only joking.
Ok so if we go back to the post "Rocket" - See inside this post for full details.
We had the A and B moves. But this wasn't actually the 3 end as expected. So in Wyckoff terms, this was the BC and not the UTAD move.
Here's why I want to say I am wrong - Our indicator for the top of the mean reversion called a $64,966 March 21st. ATH was 64,896 - what's 70 bucks amongst friends?
However, before this, we had a March 19th move inside the regression which also has a tag of the outer upper channel lined up for 65k.
The 26th of March the weekly 3 was projected for 67k - however, this is where I was wrong. 3 had yet to complete, meaning daily 5 was still being built. See inside this one for exact levels.
So I was feeling a little scared these levels had all shifted a bit.
The call was built around 8hours of Liquidity levels (also unchartered territory for BTC) Although it was a fake-out and drop.
So I wanted to share the shift. This is what I had pushed out in the rocket post.
Whereas actually, 3 is now from the ATH.
Last nights call was an internal joke on Cubbish pressure - catching a lovely timed drop (see inside for call)
Hope next week brings some more fun.
Disclaimer This idea does not constitute as financial advice. It is for educational purposes only, our principle trader has over 20 years’ experience in stocks, ETF’s, and Forex. Hence each trade setup might have different hold times, entry or exit conditions, and will vary from the post/idea shared here. You can use the information from this post to make your own trading plan for the instrument discussed. Trading carries a risk; a high percentage of retail traders lose money. Please keep this in mind when entering any trade. Stay safe.
Le informazioni ed i contenuti pubblicati non costituiscono in alcun modo una sollecitazione ad investire o ad operare nei mercati finanziari. Non sono inoltre fornite o supportate da TradingView. Maggiori dettagli nelle Condizioni d'uso.