Bradleyrb

AIONBTC 30% PP

Long
Bradleyrb Updated   
BINANCE:AIONBTC   None
AIONBTC took a nose dive just after the death-cross of the 22 and 200 EMA on the 4hr Chart. It seems to have bottomed out around 310SATS. Currently AIONBTC is sitting in an accumulation phase and looks ready to break out. There is a bullish crossover of the 4hr stochastics which shows momentum is starting to grow in the right direction. Please see targets below:

BUY:
Between 325 - 333

TARGETS:

372 25%
409 25%
449 50%

I will only post my own ideas and what i am trading myself. This is not financial advice, so please use your own discretion when choosing trades. All comments are welcome.
Good Luck with your trading!
Trade active:
Looking like AIONBTC is forming a double-bottom. Stoch-RSI was on 17 for 1st bottom and now 12 for the second. No such thing as over-bought or oversold and the trade can always turn and keep going down. However, AIONBTC is still on its base-level and we are waiting for the turnaround.
Trade active:
As expected, the turnaround has happened and i am now a little bit above my buy-in area. Still much room to grow. I will be aiming, ideally, for a cross-over of the 22 and 200 ema. This would essentially form a 4hr golden cross and the price should spike to hopefully hit targets. Goodluck!
Trade active:
The BTC drop was unexpected and this trade has dragged on longer than I wanted. Currently 6.15% up and pushing for first target.
Comment:
FIRST TARGET HIT:
372
25% SOLD at 14.4%
Trade active:
AION/BTC on the move again, next Target is 409 SATS
Trade active
Trade active:
MIssed my second target by 4SATS...killer
Trade closed: target reached:
Please excuse me for not having updated this trade:
SECOND TARGET HIT (30th MARCH):
409 25% SOLD at 25.85% PROFIT

FINAL TARGET HIT (3rd April):
449 50% SOLD at 38.15% PROFIT
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.