XRP has just confirmed a golden cross on the hourly chart, indicating a bullish momentum in the short term. Meanwhile, the simple XRP XRP exceeded 50 days (SMA 50) on the daily chart-the decisive technical level that traders watch closely.
The golden cross is formed when a short -term average (such as SMA for 50 hours) crosses over the long -term steel (such as SMA 200 hours). On the hourly chart, it is often seen as an early signal to reflect the direction or short -term price strength.
After the last unification, XRP Daily 50 SMA violated at $ 2.20, which served as support and resistance in the current session. This step indicates that the bulls gain momentum and target higher price levels.
What comes after that?
At the time of writing this report, XRP increased by 7.73 % in the last 24 hours to $ 2.26. In the next sessions, XRP behavior will be seen near Daily SMA 50 if the price is sustainable over it. According to Ali, an encryption analyst, XRP seems to be a reverse and shoulder pattern, which is likely to put the way for the bullish penetration of about $ 2.70.
Related
The next goal will be $ 3, but if this level is crossed, XRP may move towards a sign of $ 3.4. The sellers are expected to maintain the resistance line because the gathering over it will start a new phase of the XRP price.
The level of $ 2 is decisive support on the negative side. Less dollar rest and closure may indicate that the bears remain in driving. XRP can decrease to $ 1.72 and $ 1.61.
Security vulnerability is fixed XRPL library
Yesterday, a security vulnerability was discovered at XRPL.js, which is the Javascript Library to interact with LEDGER XRP.
Related
The problem only affects Node Package Manager (NPM) versions, a site where developers participate in a usable symbol of projects; The XRP code base or the same GitHub warehouse is not affected, as well as important XRP services such as XAMAN and XRPSCAN wallet.
As a result, XRP Ledger Foundation has released updated versions of the tool to address weakness, and urge projects to switch to the latest version immediately. The affected versions (V4.2.1-4.2.4 and V2.14.2) were neglected.
