UnknownUnicorn1540828

BTCUSDT : Price update and crucial data

UnknownUnicorn1540828 Mis à jour   
POLONIEX:BTCUSDT   Bitcoin / Tether USD
Hi guys,

So here my weekly post

  • Target (reviewed) : 2.8k-4k
  • Pattern : ABCDE correction with Zig zag 5,3,5 on shorter time frame. ABC correction on bigger time frame. Fibonacci full retracement at 3.5k.
  • Crucial data : Volatility calculation (calculated by Srezz) implies that if we close below 7775 the next zone is 2.8k but i will stay conservative with my fibo full retracement at 3.5k
  • Opinion : highly probable
  • Chart
    1) 60 min - Zig zag 5,3,5

    2) 1D - ABCDE (not showed) with ABC variant
    original post

    3) 1W - ABC correction

Transaction en cours:
if you didnt folow all the story. Heres my older post :
Transaction en cours:
If this count is valid as i project we may go verticaly down. Worked at hospital tonight and tired. i will give target later and it will give us time to see if the count is the one i project !
Transaction en cours:
As projected in the precendent chart we going down verticaly. 1-2 major with 1-2s sub and minor
Transaction en cours:
Anterio scenario still on the table :
Transaction en cours:
And this one still on the table :
Trade fermée: cible de profit atteinte:
I would wait to confirm it but it seems that we going for ths scenario :
Commentaire:
Weekly post maybe tonight. Stay tuned !
Commentaire:
Im starting to be curious about how the alts behave. I think a new weekly post with both bullish and bearish count tomorrow would be better than the bearish count.

My questions are :
Does alts market behave is a pro-factor of BTC behavior ?
By focusing on a bearish count does I have missed key elements ?

Why waiting for tomorrow ? -More data, better projection !
Clause de non-responsabilité

Les informations et les publications ne sont pas destinées à être, et ne constituent pas, des conseils ou des recommandations en matière de finance, d'investissement, de trading ou d'autres types de conseils fournis ou approuvés par TradingView. Pour en savoir plus, consultez les Conditions d'utilisation.