Main navigation

Error message

Warning: Undefined array key 0 in amp_entity_view_alter() (line 156 of modules/contrib/amp/amp.module).
amp_entity_view_alter(Array, Object, Object) (Line: 545)
Drupal\Core\Extension\ModuleHandler->alter('node_view', Array, Object, Object) (Line: 304)
Drupal\Core\Entity\EntityViewBuilder->buildMultiple(Array) (Line: 238)
Drupal\Core\Entity\EntityViewBuilder->build(Array)
call_user_func_array(Array, Array) (Line: 111)
Drupal\Core\Render\Renderer->doTrustedCallback(Array, Array, 'Render #pre_render callbacks must be methods of a class that implements \Drupal\Core\Security\TrustedCallbackInterface or be an anonymous function. The callback was %s. See https://www.drupal.org/node/2966725', 'exception', 'Drupal\Core\Render\Element\RenderCallbackInterface') (Line: 788)
Drupal\Core\Render\Renderer->doCallback('#pre_render', Array, Array) (Line: 377)
Drupal\Core\Render\Renderer->doRender(Array, ) (Line: 204)
Drupal\Core\Render\Renderer->render(Array, ) (Line: 238)
Drupal\Core\Render\MainContent\HtmlRenderer->Drupal\Core\Render\MainContent\{closure}() (Line: 583)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 239)
Drupal\Core\Render\MainContent\HtmlRenderer->prepare(Array, Object, Object) (Line: 128)
Drupal\Core\Render\MainContent\HtmlRenderer->renderResponse(Array, Object, Object) (Line: 90)
Drupal\Core\EventSubscriber\MainContentViewSubscriber->onViewRenderArray(Object, 'kernel.view', Object)
call_user_func(Array, Object, 'kernel.view', Object) (Line: 111)
Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch(Object, 'kernel.view') (Line: 187)
Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 76)
Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 58)
Drupal\Core\StackMiddleware\Session->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object, 1, 1) (Line: 191)
Drupal\page_cache\StackMiddleware\PageCache->fetch(Object, 1, 1) (Line: 128)
Drupal\page_cache\StackMiddleware\PageCache->lookup(Object, 1, 1) (Line: 82)
Drupal\page_cache\StackMiddleware\PageCache->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle(Object, 1, 1) (Line: 704)
Drupal\Core\DrupalKernel->handle(Object) (Line: 18)

US Securities and Exchange Commission Still Hesitant About Crypto ETFs

Advertisement
Wed, 28/11/2018 - 15:53
US Securities and Exchange Commission Still Hesitant About Crypto ETFs
Cover image via U.Today
Read U.TODAY on
Google News

SEC Chairman Jay Clayton made public today during his speech at the Consensus: Invest conference that he is not yet comfortable with Bitcoin and other cryptocurrency ETFs. The main reasons behind his unease are the risk of manipulation and lack of solid market surveillance. The chairman stated:

“What investors expect is that trading in the commodity that underlies that ETF makes sense and is free from the risk of manipulation […] It’s an issue that needs to be addressed before I would be comfortable.”

In the meantime, Bitcoin just had its best day in weeks, posting an 8.50% gain and climbing above the key $4,000 mark.

Advertisement

Chart Analysis – BTC/USD

Chart Analysis – BTC/USD

Currently trading at $4,011 on Coinbase and higher on crypto-to-crypto exchanges, Bitcoin is still down more than 11% for the last 7 days, but it is showing increased bullish pressure and potential for more upside.

After the double bottom formed around 3500 support, the pair climbed, but it is now at a crossroad: if it can break the current resistance at 4000, it will most likely move above 4200 during the days to come, but otherwise it will probably drop for another test of 3500. Although we are in a clear downtrend, the chart shows bullish signs, so we favour the buy side, at least for the short term.

Support zone: 3500

Resistance zone: 4000 followed by 4200

Most likely scenario: move to 4200 if 4000 is broken decisively

Alternative scenario: rejection at current levels and move into 3500

Related articles

Advertisement
TopCryptoNewsinYourMailbox
TopCryptoNewsinYourMailbox
Advertisement
Advertisement

Recommended articles

Latest Press Releases

Our social media
There's a lot to see there, too

Popular articles

Advertisement
AD