BTCUSD: sequential monthly update March 2019
Updated
After monthly expectation was disturbed, as my followers remember, I was waiting for the RED 1 to tell me where our next channel are going to settle it's bottom red line
This month, for the first 20 days, we saw a fight for this RED 1 to stay, and now most likely are going higher, probably will succeed to close above previous GREEN 4 in the end, but we'll wait and see
If RED 1; then our next expectations are:
- to test support line(RED)
- to test median line(GRAY)
Let's say next two weeks we succeed to close RED 1, immediately after price going to try and close below it or will fail to do this and strike higher somewhere around:
- the median line(5715.78),
- previous strong as hell unmet expectation line(6266.24),
- previous channel's median(6916.78) resistance(7761.56) lines
The bad part are going to happen only
IF WE FAIL TO CLOSE RED 1; THEN
_!_EMERGENCY DIVE_!_
Thanks and let the profit come to you!
This month, for the first 20 days, we saw a fight for this RED 1 to stay, and now most likely are going higher, probably will succeed to close above previous GREEN 4 in the end, but we'll wait and see
If RED 1; then our next expectations are:
- to test support line(RED)
- to test median line(GRAY)
Let's say next two weeks we succeed to close RED 1, immediately after price going to try and close below it or will fail to do this and strike higher somewhere around:
- the median line(5715.78),
- previous strong as hell unmet expectation line(6266.24),
- previous channel's median(6916.78) resistance(7761.56) lines
The bad part are going to happen only
IF WE FAIL TO CLOSE RED 1; THEN
_!_EMERGENCY DIVE_!_
Thanks and let the profit come to you!
Trade closed: target reached
Reached the unmet expectation from Dec 2018 and most likely going higher
Related publications
Disclaimer
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.