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.IO Creator Block.one Breaks Silence After Network Collapse
Block.one, the fintech team behind the EOS.IO blockchain, has issued their first public statement since the recent collapse of the EOS network. From the statement, few could have expected this kind of reaction.
Block.one: It's Time to Step In
With Block.one holding of 9.5% of the total EOS tokens in circulation, many individuals began to publicly participate in discussing ideas and proposals about upgrading the network. More importantly is the fact that Block.one will begin participating in block producer voting:
We now feel ready to begin playing our proportional role, with the focus of continuing to support healthy upgrades of the EOS network, the official statement says.
It's ironic and obvious that this forced decision by Block.one is characterized as an exciting milestone "marked by joining the EOS community in more actively furthering the iterative advancement of public blockchain development". Apart from the BP-voting participation, the only action that is clearly disclosed is the launch of the #EOSGOV hashtag on social media, allowing the public to share their suggestions on how to improve the EOS blockchain.
EOS (De)Centralization: New Page in History
We can say with certainty that the decision made by the EOS.IO leaders will be widely criticized as one more step to EOS network centralization. This story started a year ago when severe whale-dominated nature of EOS.IO blockchain was disclosed. 69 % of native tokens were controlled by 100 accounts in November, 2018.
Alex DovbnyaAccording to the Whiteblock Report, EOS acts not as blockchain, but as a cloud database, in which transactions may not be verified by cryptographical means. EOSians then reported the transactions, which were reversed by arbitrators.
The decision of Block.one to intervene in the block producer voting process is because of the EOS network cohesion, when the CPU capacity of users were overloaded by an airdrop.
Does it not look like someone tried to put on a good front? Let's discuss it in our Twitter!
Arman Shirinyan
Dan Burgin
Alex Dovbnya