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)
Traders Require Compensation After OKEx Closed BCH Futures, Promising to No Longer Work with the Exchange
Hong Kong-based crypto exchange OKEx caught investors off guard when it settled futures contracts on Bitcoin Cash ahead of its hard fork, having hardly warned anybody.
Big investors losing big money
On Monday, Bloomberg wrote that this curious move by OKEx plunged investors into serious losses. For example, the founder of Consensus Technologies, Qiao Changhe, claimed that his investment firm had $700,000 go down the drain due to OKEx closing BCH futures at the mark on charts which did not reflect the market rates back then.
After this mishap, he shared that he is considering cutting the initial $5-mln investments into OKEx. Changhe believes the platform is losing customers’ trust and reliability.
Darryn PollockComplaining to regulators
Four other top traders, whose names Bloomberg prefers not to disclose, also stated that their cooperation with OKEx is going to be reduced or they will even change their investment partner completely after what had happened.
One of those bigwigs, as per Bloomberg, complained to the local SEC.
What actually happened
A day before the BCH hard fork occurred, the exchange published a note on its blog, saying that all Bitcoin Cash futures would stop trading at 9:05 in the morning and delivered at 10:00 in the morning. According to the blog post, the situation was caused by the approaching chain split of the Bitcoin Cash network.
As for the closing prices the exchange chose for closing the contracts, OKEx wrote that at that moment there were no trading crypto pairs with BCH that would have sufficient market depth and trading volume to create an index for delivery.
Alexander GoborovOKEx explained their decision to avoid announcing this earlier was out of desire to protect their users from possible market manipulation, calling this situation an extremely special case.
…it happens
OKEx has previously also caused awkward situations for its users. In late summer, the exchange froze the account of one of its users and forced a liquidation. The reason was that the user made a large long position of over 4 mln BTC futures and turned down the exchange’s request to make the position smaller.
Related articles
Gamza Khanzadaev
Godfrey Benjamin
Vladislav Sopov
Dan Burgin