kjwlegend

Gold 0520 Trading Plan

Long
kjwlegend Updated   
TVC:GOLD   CFDs on Gold (US$ / OZ)
Instead of calling Gold analysis, I would use the term of trading plan or trading journal to record my trades.
So please note: This is a personal journal only, but NOT a trading suggestion. Please control your own risk if you want to follow, we may have different risk preference and position management strategy.

Date: 2020/05/20

No plan, No trading

Entry reason:

----- Previous analysis -------------
Gold has been doing a-b-c-d-e conslidating waves of wave (iv) for almost 3 weeks and now it's in the move of wave (v), which a new high is highly expected in next 5-10 days.
Bullish trend is confirmed so the trade is easy because the direction is clear.

Next few questions are:
1. Where to enter
2. Where to exit. (The target)

The entry:
I would not expect the gold to drops that hardly at this moment
Assume this is a bullish trend , : 1725 ~ 1730 is already a good point for me to re-entry.
I wouldn' expect price below 1710 (the grene trendline ) so much. If it did, it means the wave (v) is so weak and maybe finished. And the drop will be the correction wave A.

The exit:
wave(i) and wave ( iii ) are doing at least $170 in low-high difference. wave (v) may could be 100% or at least 50% ~ 61.8% fib of those.
To calculate the target:

1660 ~ 1690 + (range 100 to $180) = 1760 ~~~ 1840
---------------------------------------------
Updated analysis:

Today's plan is exactly same as 0519.
So not too much update.

So here's my plan:

Buy 1742, SL 1735. TP 1749 TP 1763
Confidence level: 65%

-----------------0519 result----------------------
Emotion level for the trade: Confident.
Result : Partially closed my 1730 long at 1749. and now re-entry at 1742 again.
Trade active:
1742 long is already in
Trade closed: stop reached
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.