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)

EOS Mainnet Network Freeze Points to Bigger Problems on the Horizon

Advertisement
Mon, 18/06/2018 - 14:14
EOS Mainnet Network Freeze Points to Bigger Problems on the Horizon
Cover image via U.Today
Read U.TODAY on
Google News

EOS has garnered a pretty big reputation since its $4 bln ICO which was the largest in history, however, with its growth and move to the new mainnet, a major glitch occured showing a few big cracks in the facade that is EOS’s entire so-called decentralized system.

The mainnet suffered a glitch which saw it freeze over the weekend, which paused the Blockchain and stopped all transactions.

This has seen many either slate, question or mock EOS for such a calamitous fault, but it has also led to many issues that need addressing about a company which is meant to be a success story of ICOs.

card

The big freeze

The freeze of the EOS network was announced by the development team who were alerted to a bug on the network. A few hours later, the development posted an update that the problem had been identified. Block.one, the creator of EOS, was able to develop a software patch for the bug.

The problem was a bug in the code that controlled how deferred transactions were handled. The disruption has not really affected the price, upon the news of the freeze, EOS token prices fell about five percent.

This move to the mainnet and the lead up to this switch has been greatly anticipated as EOS price has seen some big spikes in the past few weeks around such news.

Additional issues

This latest freeze is another compounding issue as the mainnet continues to stumble around its launch.  Voting has been other issues affecting the company. It was necessary for 15 percent of the EOS community to vote Block producers, but the voting was slow with it only reaching just past three percent last week.

card

Questions of decentralization

There have been questions put forward on the level of decentralization of EOS as research shows that 50 percent of the tokens belong to the top 10 wallets. This makes things complicated, especially with the need for voting to advance the mainnet.

Basically, the necessary voting could all be done by big wallets within minutes, and their owners could choose the Block Producers they want. However, it is not happening.

Among the  Block Producers candidates there is one that remains anonymous and some most active members of the community are warning against voting for this candidate until it identifies itself.

Shitcoin

The crypto community has not reacted well to the way in which EOS has gone about its business with the mainnet move. The freeze, and the supposed-decentralized nature of the project, has led many to question if EOS is even a viable cryptocurrency.

 

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