GBPUSD H4 AnalysisSupport 1.30000
Resistance 1 1.31804
Resistance 2 1.34165
Entry Point 1.30665
if gbpusd retrace from 1.31804 then it will sell till 1.30000 , from support when it goes up and cross the R1 1.31804 and when its fall down and retrace from 1.31800 then it will going to another Resisrance point 1.34165
Buying Zone 1.30000 - 1.31804
Techinal
BTCUSDT/ By Delovski / what I'm doing exactly Hello all ,
As you can see in the figure, at points 1, 2 and 3, my indicator (not shown here) gives me short position three times. As I said before, in the ascending trend, you should not take a short position here and it only gives me the opportunity to take a long position in points A, B and C where my indicator shows .
I added 30, 20, and 10 percent to the long position at points A, B, and C , respectively, and placed the Stop lost on point A . Good luck .
Is BTC Crashing Again? Okkkkk so my first prediction shut a few people up LOL. Let's take a look at the monthly timeframe for the time being. What we clearly see is a Hammer formed, followed by a possible engulfing of that candle, but closer to the close of that candle, we should see if it is or not.I would possibly look for a sell position around 47k where i have clearly marked at the wick of the hammer my entry. People will gain fate again in the coin, but will it retrace to 20k, no doubt. Scanning over the daily timeframe, its quiet interesting to see that 47k is clearly showing confluence with the Fibonacci extension at the 50% zone, which is also known as a golden zone for entries. One last thing that completes my analysis is we have liquidity zones(Imbalances) below that need to be filled with the Ema (40) just below them.
KEEP AN EYE ON WPRHI GUYS HOPE EVERYONE IS DOING GREAT, TODAY I AM POSTING AN IDEA ABOUT WPR.
WHY SHOULD YOU BUY WPR:
1) WE HAVE STRONG SUPPORT AT 85 SATS
2) WE CAN SEE BULLISH DIVERGENCE ON MACD 4H TIMEFRAME
3) STOCH RSI IS NOT EITHER OVERBOUGHT NEITHER OVERSOLD SO ITS OPTIMUM CONDITION TO POSSIBLE MOVE ON BOTH SIDES.
TRADE SAFE GUYS AND DONT FORGET TO USE TIGHT S/L.
:)