DestinationMoonCrypto

Bitcoin Today: SEC delays, but market growth

BITFINEX:BTCUSD   Bitcoin
Price
Yesterday, despite the new statement from SEC about delaying the SolidX Van Eck Bitcoin ETF decision again, after short fluctuations at the 6400 level bitcoin found a support and went upwards accompanied by a rise in volumes. At the end of the yesterday, BTCUSD reached 6600 level, and today already broke above Bearish Trend Line. On the way up the price will meet an important resistance level 7000, which coincides with the 100-days EAM at this point. A breakthrough above 7000 will be a major turnaround signal, until then an entering the long positions stays a risky business. For now, the most important for the bullish trend is to hold above 6600 level. High volatility and buying volumes in this area will be a sign of readiness to test 7000. Comeback below 6600 would be a bullish sign.

Today forecast
Trading in the 6600 - 7000 zone.

Latest news
  • SEC delaying ETF decision from until February of 2019
    The SEC has published an official statement saying that it is postponing its decision on the approval of the CBOE’s application to be able to trade shares of the SolidX Van Eck Bitcoin ETF (Exchange Traded Fund.) Following initial delays, a decision was expected by September 30th; now, a decision isn’t expected until February of 2019.
    “Institution of such proceedings is appropriate at this time in view of the legal and policy issues raised by the proposed rule change,” an official statement by the Commission reads. “Institution of proceedings does not indicate that the Commission has reached any conclusions with respect to any of the issues involved.”
    The SEC also said that it is seeking public opinions and information from the public in order to inform its decision and that it had received more than 1400 letters about the matter so far.
    In general, people's reaction can be characterized as follows: Delays are some sort of a sign that the SEC is slowly warming up to the idea of a Bitcoin ETF. For now, delays are more promising that outright denials, of which there have been many.
    “Being delayed was a best-case scenario. It was never going to be approved,” – Reddit user anti09

  • A critical vulnerability in Bitcoin Core, that threatened the bitcoin network for two years, is eliminated
    On Tuesday, September 18, an unscheduled release of the Bitcoin Core client under version 0.16.3 took place, the release eliminated a critical vulnerability that threatened the DOS attack on the network. The exploitation of the bug was, however, not an easy task, and fortunately, no one took advantage of them.
    As stated in the accompanying comments of Bitcoin Core developers, the vulnerability was exploited by the user who wished to remain anonymous. The exploitation of the bug, which was called CVE-2018-1744, allowed an attacker to disrupt almost 90% of the nodes, and only 12.5 BTC would be required to carry out the attack - the size of the reward currently received by the miners for the block. Built-in Bitcoin Core Fast Internet Bitcoin Relay Engine (FIBRE) engine would also contribute to the attack.
    The Optech mailing list explains that the bug CVE-2018-17144 appeared in the Bitcoin Core 0.14.0 release, which was released in November 2016, and affected all subsequent versions up to 0.16.2. Its exploitation allowed to disrupt the network when trying to validate a block containing a transaction that tries to double-spend the input. Such block would be invalid and could only be created by miners willing to give up the loss of a reward of 12.5 BTC (about $ 80,000 at the current rate).
    It is worth noting that this vulnerability was the result of the so-called human factor, and responsibility is on those developers who approved the corresponding code change. Among them were, for example, Gregory Maxwell, Vladimir van der Laan, and Matt Corallo.
    For now, there were no statements from the Bitcoin Core developers, as to whether any analysis of the incident will be conducted and whether a public report on the causes of the incident will be made and how to avoid the recurrence of such cases in the future.


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.