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)
Is the Dead CEO Story Fake? Evidence Is Mounting That QuadrigaCX Pulled Off Massive Exit Scam
QuadrigaCX, one of Canada’s most popular cryptocurrency exchanges, appears to be in a serious predicament — its customers can’t get access to $190 mln worth of crypto after its CEO, Gerald Cotton, unexpectedly died from Crohn's disease in India. Cotton was the only person who had access to the virtual keys to the exchange’s cold wallets, and many people suspect that the whole thing could be a huge exit scam.
Is he really dead?
The unfortunate death of the Canadian crypto CEO might not have even happened at all. Multiple scam allegations are picking up steam after the news spread like wildfire across numerous news outlets.
The thing is, their story about how he died is a bit fishy. He was only 30, and they're saying he died from complications due to crohn's disease while opening an orphanage in India. A lot of people are finding this hard to believe.
— Adam (@ChalicothereX) February 4, 2019
However, Freddie Heartline, one of QuadrigaCX’s very first customers, who also happens to be Cotton’s longtime friend, believes that these accusations do not have any substance. He claims that Cotton was ‘a really nice guy’ who wouldn’t be able to pull off an exit scam.
The CEO’s widowed wife Jennifer Robertson revealed that she received multiple death threats from disgruntled customers. Cotton’s will was yet another log on the fire given that it was signed two weeks prior to his ‘unexpected’ demise with (you guessed it) Robertson being the sole executor. The alleged death certificate didn’t cool down the exchange’s users, who think that it is bogus. Notably, the certificate was issued in Nova Scotia, not India.
It is also worth mentioning that several outgoing transactions have been detected after Cotton’s death, which took place on Dec. 9, 2018. Obviously, that doesn’t fit the narrative.
Fascinating article on forensic #blockchain analysis in the #QuadrigaCX case.
— Chetan Phull (@SmartblockLaw) February 4, 2019
Reportedly, "[s]everal outgoing transactions" from QuadrigaCX addresses "have been made since the alleged date of Gerald Cotten’s passing (December 9th, 2018)".#crypto #lawhttps://t.co/D5wxJmXBmB
Regulatory uncertainty is to blame
As of now, deposit insurance doesn’t apply to cryptocurrencies in Canada, which signifies the importance of proper regulations. In case of any black swan situation, customers will have to deal with the consequences.
On Oct. 29, U.Today also reported about another Canadian exchange, MapleChange, facing the wrath of its users after an unexpected hacking attack gave ground to suspicions about a potential exit scam.
Darryn PollockQuadrigaCX is currently seeking creditor protection to prevent any lawsuits from disgruntled customers. The court hearing will take place on Feb. 5.
Related articles
Vladislav Sopov
Dan Burgin