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 (EOS) 2.0 Released by Block.One: What's New
Block.one, the development team behind EOS.IO (EOS) blockchain, released the second version of its software. It is focused on the operational speed and smooth development experience.
New Virtual Machine
It has been announced today that EOS.IO (EOS) 2.0 is released. It is a software required for the operations in EOS.IO and similar blockchains.
A stable version of #EOSIO 2 is now available making it faster, simpler, and even more secure. Start building. https://t.co/R6PGAUsJ30
— block.one (@block_one_) January 10, 2020
It replaces an ordinary WebAssembly (WASM)-based engine by a new, purpose-built EOS VM. According to Block.one, it will process smart contracts up to 4x-16x faster than the previous version of EOS.IO software. EOS VM and its components are also highly customizable, so developers can implement its various facets suitable for different use-cases.
Vera YurinaEOS.IO also has upgraded the block processing performance by isolating some components of transaction handling.
Developers Paradise
A new development environment, EOSIO Quickstart Web IDE has also been released. It is run in the cloud, so, a new smart contract testnet can be created even by a newbie developer in a couple of minutes.
Moreover, with EOS.IO (EOS) 2.0, developers can begin with demo applications, seamlessly make changes, and see updates in real-time, as well as commit code to Git repositories directly from their browsers.
Finally, cutting-edge WebAuthn cryptographic standard is implemented to guarantee the unmatched level of security and to prevent high-profile data breaches where passwords are stolen.
Well, it looks like EOS.IO has fully recovered from recent congestion. Do you agree? Answer in Comments!
Related articles
Alex Dovbnya
Dan Burgin