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)

Ripple Is Still Liable for Illegal XRP Sales, According to Lead Plaintiff in Class-Action Lawsuit

Advertisement
Tue, 5/11/2019 - 14:40
Ripple Is Still Liable for Illegal XRP Sales, According to Lead Plaintiff in Class-Action Lawsuit
Cover image via www.123rf.com
Read U.TODAY on
Google News

Bradley Sostack, the plaintiff in the class-action lawsuit against Blockchain company Ripple, claims that him delaying the suit "doesn't immunize" the Brad Gralinghouse-helmed crypto giant from following securities laws. 

Related

Sostack continues to insist that XRP, the native token of Ripple, is a security in a new legal filing. Hence, Ripple violated the law by selling its token to the general public without registering with the Securities and Exchange Commission (SEC). 

A group of investors, who lost big due to the depreciation of XRP tokens, filed a class-action lawsuit back in summer 2018 to prove XRP's securities status.           

Ripple tried to throw the damning lawsuit out of the court by filing a motion to dismiss it on the basis of a three-year statute of repose that expired as of 2016. However, according to Sostack, it doesn't bar Ripple from liability.      

“Defendants have failed to cite any case – and indeed, no court has found – that liability for multiple offerings have been barred by the statute of repose.”

Advertisement

In the aforementioned motion, the San Francisco-based company conveniently avoided the key question about whether their token is a security, but it did mention that XRP wasn't an investment in Ripple. 

“Purchasing XRP is not an ‘investment’ in Ripple; there is no common enterprise between Ripple and XRP purchasers; there was no promise that Ripple would help generate profits for XRP holders; and the XRP Ledger is decentralized.”  

Garglinghouse has explained multiple times why XRP cannot be considered to be a security, but it remains to be seen whether his arguments are convincing enough for the SEC.

On Sept. 30, Block.one, the parent company of EOS, settled with the SEC by paying a $24 mln fine, which was deemed as a slap on the wrist by industry analysts.    

Related

However, the SEC didn't go easy on Telegram's TON project whose launched was thwarted right on the verge of the Oct. 31 deadline by the watchdog's emergency restraining order. As reported by U.Today, Telegram will face off with the SEC during a high-stake Feabruary court hearing that will determine whether Gram tokens are securities.        

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